chromepilot@0.2.12
ChromePilot CLI
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe flagged shell execution is part of an explicit external CLI installation command, while extension telemetry requires an enabled local configuration and uses its configured destination. The inspected automatic startup paths did not show credential theft or unrelated execution.
Decision evidence
public snapshot- The package exposes a CLI entry point at dist/index.js; no install lifecycle hook is declared in the inspected metadata.
- Extension telemetry starts only when local config sets telemetry.devops.enabled and provides an endpoint and API key.
- The extension telemetry payload contains install IDs and usage events; its destination comes from local configuration.
- CLI logging sends to localhost using the configured port and CP_TOKEN.
- External CLI installation runs only through the explicit external install action.
- Doctor self-healing requires the explicit --self-heal option.
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 · L32Findings
Affected versions and remediation
This report applies to chromepilot@0.2.12.
See all versions of chromepilot for other recorded verdicts.
- Review the evidence and your use of chromepilot@0.2.12 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.