@fragment-dev/cli@2026.11.1
FRAGMENT CLI
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe CLI sends runtime usage telemetry by default, with only ordinary command and machine fields and an opt-out environment variable. The source does not disclose the telemetry, so this is suspicious rather than malicious.
Decision evidence
public snapshot- Each CLI command starts PostHog analytics unless DISABLE_CLI_ANALYTICS=true.
- The event includes a fixed distinct ID, command name, architecture, platform, shell name and beta flag.
- The package manifest identifies this as a Fragment CLI with bin/run.js as its command entry point.
- The captured fields are limited to ordinary CLI and machine telemetry; no credentials or file contents appear in the event.
- No install, preinstall or postinstall scripts are declared.
- The launcher delegates command execution to oclif.
Source & flagged code
12 flaggedPackage source references child process execution.
dist/open-SJMVVA3H.jsView on unpkg · L11Source file is highly similar to a previously finalized malicious package; route for source-aware review.
dist/open-SJMVVA3H.jsView on unpkgFindings
Affected versions and remediation
This report applies to @fragment-dev/cli@2026.11.1.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.11.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.