@fragment-dev/cli@2026.10.16-12
FRAGMENT CLI
AI Security Review
scanned 18d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or concrete attack behavior. The flagged process and bundled parser/GraphQL modules have ordinary CLI, browser-detection, and data-processing uses; analytics is limited to CLI usage and platform details.
Decision evidence
public snapshot- package.json points the executable to bin/run.js; its scripts list contains build and packaging tasks, with no install lifecycle hook.
- bin/run.js dispatches the CLI through oclif.
- On CLI startup, analytics records the command ID, architecture, platform, shell and beta flag; setting DISABLE_CLI_ANALYTICS to true disables it. The bundled analytics client defaults to PostHog’s us.i.posthog.com endpoint.
- The update method chooses npm or Homebrew to update this same CLI package.
- The reviewed parser helper parses JSON and returns parsing errors; the GraphQL helper invokes GraphQL execution.
- The bundled browser helper runs a fixed PowerShell query to identify the default browser. The color data module contains a color-name lookup table.
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-12.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.16-12 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.