AI Security Review
scanned 2h ago · by lpm-firewall-aiLPM treats this as warn-only first-party agent extension lifecycle risk. The application exposes an explicit cc-connect launch capability that configures and starts a local agent-related service. The default CLI starts a web server, not an install-time hook.
Decision evidence
public snapshot- `dist/lib/cc-connect/launcher.mjs` can create and modify `~/.cc-connect/config.toml` and generate access tokens.
- Its launch flow can invoke `npx -y cc-connect` and start `cc-connect` after runtime activation.
- `package.json` declares no npm install lifecycle hooks.
- Observed network calls are localhost control-plane calls and an explicit npm-registry version check; no credential-exfiltration endpoint was found.
Source & flagged code
5 flagged · loading sourcePackage source references shell execution.
dist/lib/acp2aisdk/provider-command.mjsView on unpkg · L3Package source references dynamic require/import behavior.
dist/lib/conversations/client-adapter.mjsView on unpkg · L340A single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/lib/cc-connect/launcher.mjsView on unpkg · L1Package ships high-entropy non-source blobs.
public/image-playground/assets/KaTeX_Script-Regular-D3wIWfF6.woff2View on unpkg