tokenusage-cli@0.4.2
Self-hosted AI coding token usage collector for the Token Usage dashboard.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe persistence and agent-configuration findings are tied to the user-run init workflow, and scheduled collection serves the package’s stated dashboard purpose. The reviewed Claude credential is sent to api.anthropic.com; no install-time attack or unrelated credential destination was identified.
Decision evidence
public snapshot- The package describes itself as a self-hosted AI coding token usage collector for its dashboard.
- The only lifecycle script is prepublishOnly, which runs tests; there is no install hook.
- The init command registers scheduled sync by default and provides --no-task to skip it; init also runs a first sync to show collected totals.
- Generated scheduled tasks run sync --from-scheduled and upload data, consistent with the package’s stated collection purpose.
- OpenClaw setup is gated by the integration selection in init.
- Claude usage tokens are sent as bearer credentials to api.anthropic.com, their own service.
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.2.
See all versions of tokenusage-cli for other recorded verdicts.
- Review the evidence and your use of tokenusage-cli@0.4.2 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.