@fragment-dev/cli@2026.10.15-1
FRAGMENT CLI
AI Security Review
scanned 18d ago · by lpm-firewall-aiSource inspection found no npm install hook or concrete attack behavior. The flagged execution and dynamic-loading signals resolve to CLI support code and bundled dependencies; default telemetry is limited to usage and platform details.
Decision evidence
public snapshot- The manifest exposes a user-run CLI and packaging scripts; it has no install-time lifecycle hook.
- On CLI use, telemetry sends the command ID and basic platform details to PostHog, and can be disabled with an environment setting.
- Saved credentials are read from the Fragment auth configuration; token requests use its configured OAuth URL, while telemetry sends no credentials.
- The flagged excerpts show bundled conversion, parsing, GraphQL, and browser-opening code consistent with CLI dependencies and login behavior.
- Static hints flag process execution and dynamic loading, but inspected process calls support CLI functions such as update and opening the login browser.
- Telemetry is automatic by default, but the inspected event contains command and platform metadata rather than saved credentials or user content.
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-1.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.15-1 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.