@fragment-dev/cli@2026.10.13-15
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 and dynamic-code signals resolve to CLI support code and bundled libraries, while startup analytics is limited to command and basic platform context and has an opt-out.
Decision evidence
public snapshot- The manifest exposes a CLI executable at bin/run.js, which delegates command execution to oclif.
- Startup analytics runs during a user-invoked CLI command, can be disabled, and records the command plus basic platform context for the Fragment analytics project.
- Authentication sends client credentials to the configured OAuth endpoint as part of the client-credentials flow; browser setup requires a workspace and a supplied or configured MCP URL.
- Flagged bundle content includes parser dependencies, GraphQL support, and color-name data.
- The process helper spawns an operating-system opener with 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.13-15.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.13-15 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.