@fragment-dev/cli@2026.10.14
FRAGMENT CLI
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe manifest and entry point show a conventional CLI with no install hook. The flagged subprocess and dynamic module patterns are attributable to CLI support code and bundled libraries; the inspected analytics event contains basic command and platform metadata, not credentials.
Decision evidence
public snapshot- package.json exposes a CLI entry point and defines no install lifecycle hook.
- bin/run.js delegates execution to oclif.
- The CLI sends command and basic platform metadata to its analytics client; it does not include credentials in the inspected event properties.
- The npm update subprocess is part of an explicit CLI update operation.
- The flagged chunks contain bundled library code: esprima, GraphQL, and color-name.
- The flagged open helper spawns a process to open the requested target.
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.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.14 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.