@fragment-dev/cli@2026.10.29-3
FRAGMENT CLI
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe source shows undisclosed runtime telemetry enabled by default, which warrants a warning under the telemetry rule. Its event contains command and ordinary runtime metadata, with no evidence of credential or project-data exfiltration.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
CLI command initialization, unless DISABLE_CLI_ANALYTICS=true.
Impact
The vendor can observe CLI command usage and basic runtime metadata; the source shows no credential or project-content collection in this event.
Mechanism
The command creates a PostHog client and captures the command name, platform, architecture, shell, and beta status using a fixed distinct ID.
AI rationale
The source shows undisclosed runtime telemetry enabled by default, which warrants a warning under the telemetry rule. Its event contains command and ordinary runtime metadata, with no evidence of credential or project-data exfiltration.
Evidence
dist/chunk-VPOARVKJ.js
Network endpoints1
us.i.posthog.com
Decision evidence
public snapshotAI called this Suspicious at 97.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- Each CLI command initializes PostHog analytics by default; an environment variable can disable it.
- The event contains the command name, platform, architecture, shell, and beta status, and uses a fixed CLI identity.
- The package identifies itself as the FRAGMENT CLI.
Evidence against
- The reported fields are limited to CLI usage and ordinary runtime metadata; no credentials or project content appear in the event.
- The executable delegates to the oclif CLI framework.
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-VPOARVKJ.jsView file
105Cross-file remote execution chain: dist/chunk-VPOARVKJ.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: {
High
Cross File Remote Execution Context
Source spawns a local helper that also contains network and dynamic execution context; review data flow before blocking.
dist/chunk-VPOARVKJ.jsView on unpkg · L105Findings
1 Critical3 High5 Medium6 Low
CriticalPrevious Version Dangerous Deltadist/chunk-YKGESMWT.js
HighChild Processdist/open-SJMVVA3H.js
HighCross File Remote Execution Contextdist/chunk-VPOARVKJ.js
HighSemantic Analysis Limiteddist/chunk-QDAKBUNO.js#virtual:normalized:round1
MediumDynamic Requiredist/chunk-VPOARVKJ.js
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperbin/dev.cmd
MediumStructural Risk Force Deep Review
LowScripts Present
LowEvaldist/chunk-VPOARVKJ.js
LowFilesystem
LowHigh Entropy Strings
LowTelemetry
Affected versions and remediation
This report applies to @fragment-dev/cli@2026.10.29-3.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.29-3 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.