@fragment-dev/cli@2026.10.16-3
FRAGMENT CLI
AI Security Review
scanned 18d ago · by lpm-firewall-aiStatic source inspection found a standard oclif launcher, no install lifecycle hook, and package-aligned version checks. The default telemetry is limited to CLI command and platform metadata and has an environment-variable opt-out; no concrete attack behavior was found.
Decision evidence
public snapshot- The manifest points the CLI bin at bin/run.js and defines no install lifecycle hook.
- bin/run.js delegates execution to oclif.
- CLI telemetry sends the command name and platform metadata to PostHog and can be disabled with DISABLE_CLI_ANALYTICS=true.
- The version check targets the Fragment Homebrew tap or the npm registry entry for this package.
- The flagged bundled files contain standard dependencies, including esprima, GraphQL, color-name, and a macOS browser-setting lookup.
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.16-3.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.16-3 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.