@fragment-dev/cli@2026.11.4
FRAGMENT CLI
AI Security Review
scanned 23h ago · by lpm-firewall-aiThe CLI sends runtime analytics by default to PostHog, and its README does not disclose the collection. The captured fields are limited to command and ordinary runtime metadata, so this warrants a warning rather than a malicious verdict.
Decision evidence
public snapshot- CLI startup enables PostHog capture by default unless DISABLE_CLI_ANALYTICS=true, sending a "ran CLI command" event.
- The event includes the command ID, architecture, platform and shell; the reviewed payload does not include credentials or file contents.
- The PostHog client defaults to https://us.i.posthog.com.
- The package manifest has no install, preinstall or postinstall hook.
- The executable delegates to the oclif CLI; the flagged browser process helper is used in the explicit browser-auth flow.
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-ZYFQDN2K.jsView on unpkg · L105Findings
Affected versions and remediation
This report applies to @fragment-dev/cli@2026.11.4.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.11.4 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.