@fragment-dev/cli@2026.10.28-9
FRAGMENT CLI
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe source shows runtime analytics that collect command and environment metadata without an evident disclosure. The payload inspected is limited and the collection has an opt-out, so this warrants a warning rather than a block.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Running a CLI command; analytics are enabled unless DISABLE_CLI_ANALYTICS=true.
Impact
Reports command usage and environment metadata to PostHog without an evident disclosure in the inspected source.
Mechanism
The command initializes a PostHog client and captures the command ID plus CLI, architecture, platform, shell, and beta fields.
AI rationale
The source shows runtime analytics that collect command and environment metadata without an evident disclosure. The payload inspected is limited and the collection has an opt-out, so this warrants a warning rather than a block.
Evidence
dist/chunk-VPOARVKJ.jsdist/chunk-B23ACFAK.js
Network endpoints1
us.i.posthog.com
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- Each CLI command initializes PostHog analytics by default; users can disable it with DISABLE_CLI_ANALYTICS=true.
- The analytics event reports the command ID and CLI, architecture, platform, shell, and beta fields.
- PostHog’s default host is https://us.i.posthog.com.
Evidence against
- The event uses the fixed distinct ID "fragment-cli" and the inspected payload does not include credentials, file contents, or command arguments.
- The package is a Fragment CLI whose entry point delegates command execution to oclif.
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.28-9.
See all versions of @fragment-dev/cli for other recorded verdicts.
- Review the evidence and your use of @fragment-dev/cli@2026.10.28-9 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.