@fragment-dev/cli@2026.10.14-5
FRAGMENT CLI
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe flagged process execution and dynamic-loading signals resolve to bundled CLI and utility code in the inspected excerpts. Analytics is command-triggered and package-aligned, while saved credentials are sent to the OAuth URL configured for Fragment authentication; no concrete attack surface was established.
Decision evidence
public snapshot- package.json points the fragment command to bin/run.js; the inspected scripts are build, lint, and packaging tasks, with no install hook shown.
- bin/run.js delegates command execution to oclif.
- CLI analytics captures the command name and basic platform details; it is disabled when DISABLE_CLI_ANALYTICS is true and uses the bundled PostHog client, whose default host is us.i.posthog.com.
- Saved Fragment client credentials are loaded from the Fragment auth file and used in a client-credentials POST to the OAuth URL in that configuration.
- The child-process match in open-SJMVVA3H.js is in a browser-opening helper.
- Inspected excerpts from the other flagged bundles show JSON parsing, GraphQL version code, and terminal styling utilities.
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-5.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.14-5 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.