@fragment-dev/cli@2026.10.29
FRAGMENT CLI
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe CLI sends runtime usage analytics to PostHog by default without disclosing the collection in its README. The observed event contains limited usage and runtime fields, so this is suspicious telemetry rather than malicious data theft.
Decision evidence
public snapshot- Each CLI command initializes PostHog analytics unless DISABLE_CLI_ANALYTICS=true.
- The event includes the command ID, architecture, platform, shell, and beta flag.
- The PostHog client defaults to https://us.i.posthog.com.
- The event uses the fixed distinct ID "fragment-cli" and does not include credentials or project contents.
- The analytics can be disabled with DISABLE_CLI_ANALYTICS=true.
- The README does not disclose this runtime analytics collection.
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.29.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.29 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.