@fragment-dev/cli@2026.10.23-3
⚠ Under reviewFRAGMENT CLI
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe inspected entrypoint and flagged bundle excerpts showed ordinary CLI and library behavior, with no confirmed attack. The enabled @oclif/plugin-not-found dependency is a selected runtime boundary whose source could not be inspected, so its behavior remains unresolved.
Decision evidence
public snapshot- The package entrypoint delegates command dispatch to Oclif, and inspected runtime telemetry records the command identifier and basic platform details with an environment-variable opt-out.
- Several flagged bundle excerpts resolve to ordinary CLI or library behavior, including local authentication-config loading, browser launching, API error constants, color data, JSON formatting, GraphQL version metadata, and function wrapping.
- The manifest both depends on and enables @oclif/plugin-not-found as a runtime plugin, but its prepared source was unavailable for inspection.
Source & flagged code
7 flaggedPackage source references child process execution.
dist/open-SJMVVA3H.jsView on unpkg · L11Source spawns a local helper that also contains network and dynamic execution context; review data flow before blocking.
dist/chunk-VPOARVKJ.jsView on unpkg · L105Findings
Affected versions and remediation
This report applies to @fragment-dev/cli@2026.10.23-3.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.23-3 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.