@fragment-dev/cli@2026.10.29-6
FRAGMENT CLI
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe CLI sends default-on runtime analytics to PostHog without disclosure in the inspected package metadata. The collected fields are limited to command and ordinary runtime details, so this warrants a warning rather than a malicious verdict.
Decision evidence
public snapshot- CLI startup sends a `ran CLI command` event with command ID, architecture, platform, and shell when analytics are enabled by default; `DISABLE_CLI_ANALYTICS=true` disables it.
- The bundled analytics client defaults to `https://us.i.posthog.com`.
- The package manifest identifies this as Fragment’s CLI and exposes `bin/run.js` as its command entry point.
- The analytics event uses the fixed distinct ID `fragment-cli` and collects only ordinary runtime and command-mode fields in the inspected code.
- The package declares no install or postinstall lifecycle scripts.
- The flagged child-process reference is in bundled `cross-spawn`; the inspected excerpt shows it wraps standard child-process spawning.
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-6.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.29-6 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.