registry / chromepilot / 0.2.5
chromepilot@0.2.5
ChromePilot CLI
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe flagged process execution is tied to explicit CLI actions or local server management. The extension's reporting path is gated, and the bundled server does not provide the devops telemetry configuration it requires.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
CLI commands and Chrome extension startup.
Impact
No malicious or unauthorized behavior was identified in the reviewed paths.
Mechanism
The extension communicates with the local server; optional devops reporting requires enabled local configuration and credentials.
AI rationale
The flagged process execution is tied to explicit CLI actions or local server management. The extension's reporting path is gated, and the bundled server does not provide the devops telemetry configuration it requires.
Network endpoints1
localhost:34568/api/config
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exposes a ChromePilot CLI and has no npm install lifecycle scripts.
- The extension initializes its devops sinks only when local configuration enables them and supplies an endpoint and API key.
- The bundled server's /api/config response contains error-tracking settings but no devops telemetry configuration.
- The Docker curl-to-shell installer is selected by the explicit external install command.
Evidence against
- The extension declares broad browser permissions and runs on all URLs, consistent with its stated browser recording and control purpose.
- The CLI and extension use local filesystem access, process spawning, and localhost APIs as part of their normal functions.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShellWebSocket
HighEntropyStringsMinified
Source & flagged code
8 flaggeddist/index.jsView file
28import { initCliLogger, flushCliLogger, getCliLogger } from "./logger.js";
L29: import { spawn } from "node:child_process";
L30: import fs from "node:fs";
High
28import { initCliLogger, flushCliLogger, getCliLogger } from "./logger.js";
L29: import { spawn } from "node:child_process";
L30: import fs from "node:fs";
...
L35: initCliLogger({
L36: serverUrl: process.env.CP_PORT
L37: ? `http://localhost:${process.env.CP_PORT}/api`
L38: : `http://localhost:${__cliCfg.port}/api`,
High
Same File Env Network Execution
A single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/index.jsView on unpkg · L28dist/utils/quarantine.jsView file
14* single argv element and never interpreted by a shell — important on
L15: * Windows where `cmd.exe` would re-interpret `%` characters.
L16: */
Findings
1 Critical4 High4 Medium7 Low
CriticalPrevious Version Dangerous Deltadist/commands/doctor.js
HighChild Processdist/index.js
HighShelldist/utils/quarantine.js
HighSame File Env Network Executiondist/index.js
HighCross File Remote Execution Contextdist/commands/start.js
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperdist/index.cmd
MediumStructural Risk Force Deep Review
LowScripts Present
LowEvaldist/assets/extension/background.js
LowWeak Cryptodist/version-manager.js
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to chromepilot@0.2.5.
See all versions of chromepilot for other recorded verdicts.
- Review the evidence and your use of chromepilot@0.2.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.