@fragment-dev/cli@2026.10.13-16
FRAGMENT CLI
AI Security Review
scanned 18d ago · by lpm-firewall-aiSource inspection found no install hook or concrete attack behavior. The flagged process and dynamic-loading signals resolve to bundled dependencies and ordinary CLI helpers; command analytics is limited to basic usage and platform details and can be disabled.
Decision evidence
public snapshot- package.json exposes the Fragment CLI through bin/run.js and declares no install lifecycle hook.
- The CLI records the command name and basic platform details for Fragment CLI analytics, with a disable flag.
- The bundled analytics client uses PostHog’s standard host.
- The flagged terminal and GraphQL chunks contain ordinary dependency code.
- The flagged child-process calls belong to browser detection helpers.
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.13-16.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.13-16 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.