chromepilot@0.2.11
ChromePilot CLI
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe manifest has no install lifecycle hooks, and the reviewed CLI and extension behavior aligns with ChromePilot’s stated browser-control purpose. Although the extension includes telemetry sink code, its setup is gated on configuration fields absent from the shipped server response.
Decision evidence
public snapshot- The manifest exposes a CLI and contains no install, preinstall, or postinstall hook.
- The extension telemetry setup requires an enabled configuration with an endpoint and API key; the shipped server config route returns only error-tracking settings.
- The telemetry startup event contains only the generic `plugin` / `sw.boot` event.
- The extension’s network recording code redacts common credential headers and query parameters.
- The extension’s all-sites access and recording capabilities fit its stated browser-control purpose.
- The extension requests `<all_urls>` access and runs a content script on all URLs.
- The extension bundle contains code for telemetry sinks, though the shipped config route does not activate them.
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.11.
See all versions of chromepilot for other recorded verdicts.
- Review the evidence and your use of chromepilot@0.2.11 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.