chromepilot@0.2.10
ChromePilot CLI
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe flagged process execution is used for the CLI's own self-healing start command or an explicit external install request. The extension sends its token to the local ChromePilot API, and telemetry setup is gated on enabled local configuration with a supplied endpoint.
Decision evidence
public snapshot- The package is a ChromePilot CLI, and its browser control requests go to the local ChromePilot API.
- The extension reads telemetry settings from the local server and skips telemetry setup unless devops telemetry is enabled and an endpoint and API key are supplied.
- The browser extension sends its stored token to the configured localhost ChromePilot API.
- The shell installer belongs to the explicit external install command.
- The extension requests broad browser permissions, including cookies, debugger, and access to all URLs, consistent with browser automation capabilities.
- The external install command can run shell commands, including a Docker installer, when explicitly invoked.
Source & flagged code
8 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/index.jsView on unpkg · L30Findings
Affected versions and remediation
This report applies to chromepilot@0.2.10.
See all versions of chromepilot for other recorded verdicts.
- Review the evidence and your use of chromepilot@0.2.10 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.