chromepilot@0.2.6
ChromePilot CLI
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe flagged execution and browser-control capabilities align with ChromePilot’s stated CLI and extension purpose. The telemetry sink requires configuration that this package’s local API does not return, and the download-and-run command is behind an explicit external install action.
Decision evidence
public snapshot- The package exposes a CLI entry point and declares build, development, typecheck, and test scripts; it has no install lifecycle script.
- The extension’s telemetry setup looks for telemetry.devops in the local server configuration, but this version’s /api/config response provides only error-tracking settings.
- The Docker download-and-run command is part of the named external CLI installer and requires an explicit install command.
- The extension includes broad Chrome permissions for browser control, including cookies, debugger, scripting, and access to all URLs.
- The extension contains usage and log sinks that can send events and log messages to a configured endpoint.
- The CLI runs an automatic update check when most commands are 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 · L28Findings
Affected versions and remediation
This report applies to chromepilot@0.2.6.
See all versions of chromepilot for other recorded verdicts.
- Review the evidence and your use of chromepilot@0.2.6 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.