@fragment-dev/cli@2026.10.14-8
FRAGMENT CLI
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe inspected entry point and manifest show an ordinary user-invoked CLI without an install hook. The flagged execution and parser signals map to bundled helper and dependency code; the source reviewed does not establish malicious behavior.
Decision evidence
public snapshot- package.json exposes the Fragment CLI through bin/run.js and lists no install lifecycle hook.
- The CLI's analytics are gated by DISABLE_CLI_ANALYTICS and capture the command identifier plus basic platform details.
- The flagged parser chunks are bundled Esprima, GraphQL, and color-name dependencies.
- The flagged child process call belongs to the bundled open helper.
- Auth code sends configured client credentials to the OAuth URL from the saved Fragment auth configuration.
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-8.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.14-8 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.