@fragment-dev/cli@2026.10.14-14
FRAGMENT CLI
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe package has no install lifecycle hook, and the flagged execution and dynamic-code signals resolve to bundled dependencies or normal CLI behavior. Telemetry is command-triggered and limited to command and platform metadata; authentication uses credentials and an OAuth URL supplied through the CLI configuration.
Decision evidence
public snapshot- The manifest exposes a CLI executable and lists no install lifecycle hook.
- Command-run telemetry sends the command name and basic platform metadata to PostHog, with an environment variable to disable it.
- OAuth credentials are prompted for and sent to the configured OAuth endpoint; the login command documents Fragment service endpoints.
- The flagged chunks contain bundled parser, GraphQL, and color-table dependencies; the process helper is the standard OS opener dependency.
Source & flagged code
7 flaggedPackage source references child process execution.
dist/open-SJMVVA3H.jsView on unpkg · L11This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/chunk-3IA6BI6A.jsView on unpkgFindings
Affected versions and remediation
This report applies to @fragment-dev/cli@2026.10.14-14.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.14-14 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.