@fragment-dev/cli@2026.10.30-7
FRAGMENT CLI
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe CLI sends runtime analytics by default and includes the SHELL environment value, which exceeds the limited anonymous usage and platform details allowed for clean telemetry. The observed event does not include credentials or free-form command input, so this supports a warning rather than a malicious verdict.
Decision evidence
public snapshot- CLI initialization sends analytics by default unless DISABLE_CLI_ANALYTICS=true.
- The event includes process.env.SHELL along with the command ID, architecture, platform, and beta flag.
- The bundled PostHog client defaults to https://us.i.posthog.com.
- The event uses the fixed distinct ID fragment-cli and does not show credentials, file contents, or free-form command input.
- The package exposes a CLI entry point, and its manifest contains no install lifecycle hook.
Source & flagged code
13 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.10.30-7.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.30-7 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.