@fragment-dev/cli@2026.10.15-5
FRAGMENT CLI
AI Security Review
scanned 18d ago · by lpm-firewall-aiSource inspection found no malicious behavior: the manifest has no install hook, and flagged execution paths have ordinary CLI or authentication purposes. The default analytics event is limited to command and basic runtime properties and can be disabled through an environment setting.
Decision evidence
public snapshot- The manifest exposes a CLI entrypoint and shows no install lifecycle hook.
- Flagged process execution is a bundled cross-spawn helper used to check the CLI’s installation method.
- The browser-opening helper is called by the browser authentication flow to open its supplied URL.
- Startup analytics is gated by an environment setting and records the command ID and basic runtime properties at the PostHog endpoint.
- The other required flagged chunks contain a JavaScript parser, GraphQL library code, and color conversion code.
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.15-5.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.15-5 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.