registry / @fragment-dev/cli / 2026.10.16-1
@fragment-dev/cli@2026.10.16-1
FRAGMENT CLI
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected execution and network signals are consistent with CLI utilities and package telemetry. The scanner hints do not establish a concrete attack.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user invokes the fragment CLI; no package install hook is declared.
Impact
No confirmed attack impact.
Mechanism
The inspected sources show CLI startup, utility bundles, and analytics initialization with a disable flag; they do not establish credential export or other attack behavior.
AI rationale
The manifest has no install lifecycle hook, and the inspected execution and network signals are consistent with CLI utilities and package telemetry. The scanner hints do not establish a concrete attack.
Decision evidence
public snapshotAI called this Clean at 78.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json has no preinstall, install, or postinstall hook; its scripts are development and packaging commands.
- The bundled analytics client initializes PostHog unless DISABLE_CLI_ANALYTICS is true, consistent with package telemetry.
- The flagged chunks contain bundled parser, GraphQL, and color utility code; the child-process helper spawns a command passed to it by its caller.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsPossibleObfuscationTelemetryUrlStrings
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-1.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.16-1 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.