chromepilot@0.2.7
ChromePilot CLI
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe extension contains runtime telemetry that activates when server-provided configuration enables it, without a visible user consent prompt or opt-out in the reviewed package source. The observed event is limited to startup usage data, so this warrants a warning rather than a malware block.
Decision evidence
public snapshot- The extension fetches telemetry settings from its local server and proceeds only when the returned devops config enables telemetry.
- When configured, the extension sends usage events with an install ID to the configured endpoint; startup records a service-worker boot event. The source map gives https://dev-ops.hiredchina.com as the example endpoint.
- The package has no install, preinstall, or postinstall lifecycle script.
- The reviewed telemetry event is a service-worker boot event; I found no code sending credentials or browser page contents through this telemetry path.
- Telemetry is gated by a server-provided enabled flag and endpoint.
- The visible usage event contains a feature and event name, not credentials or page content.
- External CLI installation executes only when the user invokes the install command.
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.7.
See all versions of chromepilot for other recorded verdicts.
- Review the evidence and your use of chromepilot@0.2.7 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.