tokenusage-cli@0.1.0
Self-hosted AI coding token usage collector for token-usage (forked from TokenTracker, MIT).
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe default sync flow sends runtime telemetry that the README does not disclose, making the package suspicious under the telemetry rules. The payload is limited to a machine hash and runtime metadata, and users can opt out, so this warrants a warning rather than a publish block.
Decision evidence
public snapshot- Sync invokes a heartbeat; its comment says it is throttled to one network request per day.
- The heartbeat payload contains a hashed machine ID, package version, platform, and shell.
- It POSTs that payload to the tokenusage-telemetry function on the package’s default service.
- The README describes uploads as aggregated usage and session metadata but does not disclose this heartbeat.
- The heartbeat omits raw machine IDs, credentials, token counts, usernames, and paths.
- Users can disable telemetry with environment variables or telemetry:false in config.
- The package’s stated purpose includes syncing usage data to its service.
- Claude OAuth tokens are sent to Anthropic’s own usage endpoint.
Source & flagged code
5 flaggedPackage source references weak cryptographic algorithms.
src/lib/claude-categorizer.jsView on unpkg · L335Findings
Affected versions and remediation
This report applies to tokenusage-cli@0.1.0.
See all versions of tokenusage-cli for other recorded verdicts.
- Review the evidence and your use of tokenusage-cli@0.1.0 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.