@fragment-dev/cli@2026.10.28-6
FRAGMENT CLI
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe CLI sends runtime analytics by default, including the command ID and shell, and the inspected package metadata does not disclose this collection. The payload does not show credential or file-content exfiltration, so this warrants a warning rather than a malicious verdict.
Decision evidence
public snapshot- Each CLI command starts PostHog analytics by default unless DISABLE_CLI_ANALYTICS=true; the event reports the command ID, architecture, platform, shell, and beta flag.
- The bundled PostHog client defaults to https://us.i.posthog.com.
- The package entry point launches the oclif CLI, which invokes command initialization.
- The analytics event uses the fixed distinct ID "fragment-cli" and contains no credentials or file contents in the captured properties.
- The package is a CLI whose bundled child-process and network functionality supports normal CLI operations.
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.28-6.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.28-6 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.