@fragment-dev/cli@2026.10.29-4
FRAGMENT CLI
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe CLI sends runtime analytics by default without a disclosure found in the inspected package files, although it provides an environment-variable opt-out. The event contains command and runtime metadata rather than credentials or file contents, so this is suspicious telemetry rather than malicious exfiltration.
Decision evidence
public snapshot- Every CLI command sends a PostHog event by default; users must set DISABLE_CLI_ANALYTICS=true to stop it.
- The event includes the command name, platform, architecture, shell value, and beta flag, and uses the fixed distinct ID "fragment-cli".
- The bundled PostHog client defaults to https://us.i.posthog.com.
- The package has no install, preinstall, or postinstall script; its listed scripts are build, development, packaging, and test tasks.
- Fragment credentials are sent to the OAuth URL stored in the Fragment auth configuration to obtain an access token.
- The executable delegates to oclif command execution; the telemetry is sent during CLI command initialization.
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-4.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.29-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.