@fragment-dev/cli@2026.10.16-14
FRAGMENT CLI
AI Security Review
scanned 18d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or malicious behavior. The flagged process and dynamic-loading code is consistent with CLI support and browser authentication, while the observed analytics sends limited command and platform metadata to PostHog.
Decision evidence
public snapshot- The manifest exposes a CLI entrypoint and lists development, build, and test scripts; it has no install lifecycle hook.
- The CLI entrypoint delegates execution to oclif.
- On CLI startup, analytics can send the command identifier and basic platform metadata to PostHog; an environment variable disables it.
- The PostHog client defaults to its service endpoint, and browser-launch support is invoked through the OAuth browser-auth helper.
- Flagged bundled chunks contain Esprima, GraphQL, and color-name modules, while the browser helper launches the requested URL through the operating system.
Source & flagged code
7 flaggedPackage source references child process execution.
dist/open-SJMVVA3H.jsView on unpkg · L11This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/chunk-3IA6BI6A.jsView on unpkgFindings
Affected versions and remediation
This report applies to @fragment-dev/cli@2026.10.16-14.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.16-14 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.