@fragment-dev/cli@2026.10.28-1
FRAGMENT CLI
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe CLI sends runtime telemetry by default, and the package README does not disclose the collection. The inspected payload is limited to command and runtime metadata, so this warrants a warning rather than a malicious verdict.
Decision evidence
public snapshot- CLI startup sends a PostHog event by default unless DISABLE_CLI_ANALYTICS=true.
- The event includes the command id, platform, architecture, shell, and beta status.
- The bundled PostHog client defaults to https://us.i.posthog.com.
- The event uses the fixed distinct id "fragment-cli" and the fields inspected do not include credentials or file contents.
- The runtime analytics can be disabled with DISABLE_CLI_ANALYTICS=true.
- The launcher delegates to oclif; the flagged process spawn is in a helper that opens a requested target.
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-1.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.28-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.