@fragment-dev/cli@2026.10.29-7
FRAGMENT CLI
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package is not clearly malicious: its default PostHog telemetry is limited to command and basic environment metadata. Because the source provides an opt-out but no disclosure of this runtime collection, classify it as suspicious telemetry.
Decision evidence
public snapshot- CLI initialization sends a PostHog event by default; users can disable it with DISABLE_CLI_ANALYTICS=true.
- The event includes the command name, platform, architecture, and shell, and PostHog defaults to https://us.i.posthog.com.
- The event uses the constant distinct ID "fragment-cli" and does not include credentials, files, or command arguments.
- The CLI sends its client credentials to the configured OAuth URL to obtain a service token.
- Version checks query the package’s npm registry entry or its Homebrew tap.
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-7.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.29-7 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.