registry / @fragment-dev/cli / 2026.10.16-4
@fragment-dev/cli@2026.10.16-4
FRAGMENT CLI
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe flagged process execution is in a bundled helper, while the inspected CLI analytics are command-triggered product telemetry. The manifest has no install lifecycle hook, and the inspected source does not establish an attack.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs a CLI command.
Impact
The inspected behavior does not establish credential theft, destructive activity, or unauthorized control of the consumer environment.
Mechanism
The command runner captures the command identifier, architecture, platform, and shell for analytics unless the disable environment variable is set.
AI rationale
The flagged process execution is in a bundled helper, while the inspected CLI analytics are command-triggered product telemetry. The manifest has no install lifecycle hook, and the inspected source does not establish an attack.
Decision evidence
public snapshotAI called this Clean at 87.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json identifies the package as a CLI and declares no install lifecycle hook.
- The bin entrypoint delegates to the Oclif command runner.
- The CLI sends command, architecture, platform, and shell analytics unless disabled; the source shows no secret collection in this event.
- The version helper checks Fragment’s Homebrew tap or npm registry for release versions.
- The flagged process-spawn code is part of the bundled cross-spawn helper.
- The remaining required chunks contain bundled terminal-color and GraphQL support code.
Evidence against
- The manifest’s scripts show ordinary build and packaging tasks, with no install hook.
- The observed analytics are tied to running a CLI command and use a Fragment CLI identifier.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStrings
Source & flagged code
7 flaggeddist/open-SJMVVA3H.jsView file
11import { promisify as promisify5 } from "node:util";
L12: import childProcess from "node:child_process";
L13: import fs5, { constants as fsConstants2 } from "node:fs/promises";
High
Child Process
Package source references child process execution.
dist/open-SJMVVA3H.jsView on unpkg · L11dist/chunk-3IA6BI6A.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @fragment-dev/cli@2026.9.15-1
matchedIdentity = npm:QGZyYWdtZW50LWRldi9jbGk:2026.9.15-1
similarity = 0.928
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/chunk-3IA6BI6A.jsView on unpkg105Cross-file remote execution chain: dist/chunk-3IA6BI6A.js spawns dist/chunk-QF5EN33L.js; helper contains network access plus dynamic code execution.
L105: function isProd() {
L106: return !["development", "test"].includes(process.env.NODE_ENV ?? "");
L107: }
...
L2227: if (useCache && cache.has(path)) {
L2228: return JSON.parse(cache.get(path));
L2229: }
...
L2308:
L2309: // ../../node_modules/@oclif/core/package.json
L2310: var require_package = __commonJS({
...
L2316: author: "Salesforce",
L2317: bugs: "https://github.com/oclif/core/issues",
L2318: dependencies: {
Findings
1 Critical3 High5 Medium6 Low
CriticalPrevious Version Dangerous Deltadist/chunk-3IA6BI6A.js
HighChild Processdist/open-SJMVVA3H.js
HighCross File Remote Execution Contextdist/chunk-3IA6BI6A.js
HighSemantic Analysis Limiteddist/chunk-QDAKBUNO.js#virtual:normalized:round1
MediumDynamic Requiredist/chunk-3IA6BI6A.js
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperbin/dev.cmd
MediumStructural Risk Force Deep Review
LowScripts Present
LowEvaldist/chunk-3IA6BI6A.js
LowFilesystem
LowHigh Entropy Strings
LowTelemetry
Affected versions and remediation
This report applies to @fragment-dev/cli@2026.10.16-4.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.16-4 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.