@fragment-dev/cli@2026.10.15-8
FRAGMENT CLI
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the executable enters the CLI framework. The identified network behavior is limited to a Fragment version lookup and runtime analytics with a visible opt-out; inspected child-process matches belong to bundled helpers, with no concrete attack behavior found.
Decision evidence
public snapshot- package.json exposes a CLI executable and lists ordinary project scripts; it defines no install lifecycle hook.
- bin/run.js delegates execution to the oclif CLI framework.
- The CLI checks the Fragment release version and reports when an update is available.
- Analytics is sent during CLI initialization unless DISABLE_CLI_ANALYTICS is true; the event contains the command and basic runtime details and uses PostHog’s default host.
- The large flagged chunks are bundled dependencies, including Esprima, GraphQL, color-name, and a cross-platform process-opening helper.
- The scanner flagged child-process and dynamic-code primitives, but inspected matches are in bundled dependency helpers; no concrete attack behavior was established.
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-8.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.15-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.