@crbonfree/cli
See the carbon footprint of your AI coding agents, and give them a shared memory across every tool.
This report shows the evidence for @crbonfree/cli@0.2.4. 1 of 14 known versions is blocked or flagged. See all versions.
AI Security Review
scanned 3d ago · by lpm-firewall-aiInstalled hooks upload prompts, replies, tool calls, and file diffs to the vendor API without a separate opt-in for content upload. The README describes session content as local unless semantic features are enabled, but the hook uploader does not check that setting.
Decision evidence
public snapshot- The Claude transcript parser collects user and assistant message content.
- Uploaded session records include messages, tool calls, and file diffs.
- The Stop handler passes each completed session record to the uploader.
- The uploader applies folder-scope and redaction filters, then sends the record to the configured server; the default host is api.crbonfree.com.
- The uploader POSTs the payload to the server’s ingest path with the CRBON API key.
- The README says session content stays local unless semantic search and summaries are enabled.
- The installer registers a Stop hook that invokes the session handler.
- Hook installation requires running a separate installer command; package installation has no lifecycle script.
- The uploader supports folder exclusions and redaction before sending.
Source & flagged code
14 flaggedPackage source references child process execution.
dist/updateBin.jsView on unpkg · L456Package source references dynamic require/import behavior.
dist/updateBin.jsView on unpkg · L687Package source references shell execution.
dist/mechanisms/compressCliBin.jsFindings
Affected versions and remediation
This report applies to @crbonfree/cli@0.2.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing @crbonfree/cli@0.2.4. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.