tokenusage-cli@0.4.0
Self-hosted AI coding token usage collector for the Token Usage dashboard.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged persistence and agent configuration changes are part of the documented init workflow, and init provides confirmation and integration selection. Credential use is directed to Anthropic for Claude usage, while reporting and session uploads serve the package's dashboard purpose and have documented controls.
Decision evidence
public snapshot- The only lifecycle script is prepublishOnly, which runs tests.
- Interactive init asks before configuring the environment and lets users select integrations.
- The hourly schedule is registered by init, is documented, and can be skipped with --no-task.
- Run reports contain usage and run aggregates; the README documents --run-report=off.
- Claude OAuth credentials are sent as a bearer token to Anthropic's own usage endpoint.
- Session uploads exclude titles, local working directories, resume identifiers, and cache keys.
Source & flagged code
7 flaggedPackage source references dynamic require/import behavior.
bin/tokenusage.jsView on unpkg · L5Package source references weak cryptographic algorithms.
src/lib/claude-categorizer.jsView on unpkg · L335Findings
Affected versions and remediation
This report applies to tokenusage-cli@0.4.0.
See all versions of tokenusage-cli for other recorded verdicts.
- Review the evidence and your use of tokenusage-cli@0.4.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.