@fragment-dev/cli@2026.10.14-7
FRAGMENT CLI
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe manifest has no install hook, and the executable delegates to oclif. The flagged process and dynamic-code signals resolve to bundled dependencies; inspected source supports routine CLI functionality and limited package-aligned analytics, not a concrete attack.
Decision evidence
public snapshot- The manifest identifies a CLI whose executable is bin/run.js and has no install lifecycle hook.
- The executable starts the oclif CLI; its command base sends limited command and platform analytics to PostHog, using a fixed CLI identifier and an opt-out setting.
- The required bundled files include parser, GraphQL, color-name, and browser-opening library code; inspection found no package-specific attack behavior in those locations.
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.14-7.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.14-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.