@fragment-dev/cli@2026.10.30-1
FRAGMENT CLI
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package sends runtime telemetry on by default, and its README does not disclose this collection. The event contains ordinary CLI metadata and no identified credentials or file contents, so this warrants a warning rather than a block.
Decision evidence
public snapshot- On CLI initialization, unless DISABLE_CLI_ANALYTICS=true, the package sends a PostHog event containing the command name, platform, architecture, shell, and beta status.
- The bundled PostHog client defaults to https://us.i.posthog.com.
- The telemetry uses a fixed distinct ID and reports ordinary CLI and environment metadata; I found no credential or file collection in this event.
- The package has no install lifecycle scripts, and its executable delegates to oclif.
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.30-1.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.30-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.