@fragment-dev/cli@2026.10.14-10
FRAGMENT CLI
AI Security Review
scanned 18d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or concrete attack behavior. The flagged process call is in bundled cross-spawn support code, while the observed network behavior is basic CLI analytics and package-aligned version checking.
Decision evidence
public snapshot- package.json exposes the fragment CLI through bin/run.js; the listed scripts show build and packaging tasks, with no install lifecycle hook.
- bin/run.js starts the oclif command runner.
- The main bundle imports JSON parsing and GraphQL libraries; the required chunks contain bundled parser, GraphQL, and color utility code.
- The CLI reads its own auth configuration and fetches a token using that configuration.
- Runtime analytics records the CLI command identifier and basic platform details; its bundled client uses PostHog's standard endpoint.
- The detected child-process call is in bundled cross-spawn support code.
- CLI analytics is enabled by default and records the command, architecture, platform, and shell; no credential collection or transfer was identified in the inspected caller.
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-10.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.14-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.