chromepilot@0.2.9
ChromePilot CLI
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package has no install lifecycle hook, and the extension’s inspected token flow stays on localhost. Its potential external DevOps sinks are configuration-gated, and the package’s server config route does not provide that telemetry setting.
Decision evidence
public snapshot- The manifest has build, development, typecheck, and test scripts, with no install lifecycle hook.
- The extension obtains its session token from the local server and sends authenticated requests to localhost.
- Extension DevOps sinks are used only when enabled in configuration; the package’s config route returns error-tracking settings, not a DevOps telemetry setting.
- The extension requests access to all URLs and can control browser tabs, consistent with its browser automation purpose.
- The CLI can automatically check for updates when a command runs, using its updater dependency.
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.9.
See all versions of chromepilot for other recorded verdicts.
- Review the evidence and your use of chromepilot@0.2.9 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.