registry / tokenusage-cli / 0.2.6
tokenusage-cli@0.2.6
Self-hosted AI coding token usage collector for the Token Usage dashboard.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe reviewed lifecycle, entry points, credential flow, and persistence behavior are consistent with a usage-collection CLI. Integration setup and scheduled syncing are reached through the documented init command, and the identified credential flow targets Anthropic’s usage API.
Static reason
No blocking static signals were detected.
Trigger
The user invokes commands such as init, device-login, or sync; init can configure integrations and scheduled collection.
Impact
Expected collection and reporting behavior; no malicious or unauthorized impact found.
Mechanism
Usage credentials are used for provider usage endpoints, while aggregate usage and documented session metadata are uploaded to the configured service.
AI rationale
The reviewed lifecycle, entry points, credential flow, and persistence behavior are consistent with a usage-collection CLI. Integration setup and scheduled syncing are reached through the documented init command, and the identified credential flow targets Anthropic’s usage API.
Network endpoints2
api.anthropic.comtoken-usage.baiwumm.com
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a CLI; its prepublishOnly script runs tests and is not an install hook.
- OpenClaw plugin setup and Windows scheduled-task registration occur in the explicit init command.
- Claude OAuth tokens are sent to Anthropic’s own usage endpoint to fetch usage limits.
- The README documents aggregate usage uploads, run reporting, and the data excluded from uploads.
Evidence against
- The CLI dispatches work only for selected commands; requiring its entry point does not start syncing.
- The README describes pairing and sync steps, and documents how to disable run reporting and automatic collection.
- No unrelated credential destination or unauthorized account action was identified.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggedbin/tokenusage.jsView file
5// ExperimentalWarning out of redirected sync logs.
L6: require('../src/lib/quiet-warnings').[redacted]();
L7:
Medium
Dynamic Require
Package source references dynamic require/import behavior.
bin/tokenusage.jsView on unpkg · L5src/lib/claude-categorizer.jsView file
335function defaultClaudeProjectsDir() {
L336: return path.join(os.homedir(), ".claude", "projects");
L337: }
...
L512: try {
L513: obj = JSON.parse(line);
L514: } catch (_e) {
Low
Weak Crypto
Package source references weak cryptographic algorithms.
src/lib/claude-categorizer.jsView on unpkg · L335src/lib/scheduled-task.jsView file
Findings
3 High5 Medium6 Low
HighTrigger Reachable External Ai Agent Control Surface Mutationsrc/lib/openclaw-hook.js
HighTrigger Reachable Persistencesrc/lib/scheduled-task.js
HighSemantic Analysis Limitedsrc/lib/qoder-limits.js#virtual:normalized:round1
MediumDynamic Requirebin/tokenusage.js
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencesrc/lib/scheduled-task.js
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowWeak Cryptosrc/lib/claude-categorizer.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to tokenusage-cli@0.2.6.
See all versions of tokenusage-cli for other recorded verdicts.
- Review the evidence and your use of tokenusage-cli@0.2.6 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.