@fragment-dev/cli@2026.10.13-12
FRAGMENT CLI
AI Security Review
scanned 18d ago · by lpm-firewall-aiSource inspection found no install hook or concrete attack behavior. The scanner’s process and dynamic-code signals resolve to bundled dependencies, while package-specific startup behavior is limited to CLI telemetry and release-version checking.
Decision evidence
public snapshot- package.json points the executable to bin/run.js; its scripts contain no install lifecycle hook.
- The launcher starts the oclif command framework. The flagged process spawning belongs to the bundled helper that opens a requested target with the system opener.
- CLI startup sends a command identifier and basic platform details to the bundled PostHog client; DISABLE_CLI_ANALYTICS disables this event.
- Saved Fragment authentication config is used to obtain a Cognito token; the inspected telemetry event does not include that token.
- The flagged chunks identify bundled color, JavaScript parser, and GraphQL dependencies.
- The version check fetches release metadata from Fragment’s Homebrew tap or the npm registry.
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.13-12.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.13-12 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.