@fragment-dev/cli@2026.10.16-10
FRAGMENT CLI
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe manifest has no install hook, and the executable starts the CLI. Inspected runtime behavior consists of command analytics, version warnings, and standard bundled dependencies; the scanner indicators do not establish an attack.
Decision evidence
public snapshot- The manifest exposes a CLI binary and has no install lifecycle hook.
- The binary starts the Oclif command runner.
- Command analytics is disabled by an environment setting and reports the CLI command and basic platform metadata to PostHog.
- Version checking compares Fragment releases and warns; package discovery uses fixed brew and npm list commands.
- Flagged bundles contain parser, GraphQL, and color-name dependencies; the browser-opening helper starts its resolved command.
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-10.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.16-10 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.