registry / tokenusage-cli
tokenusage-cli
Self-hosted AI coding token usage collector for the Token Usage dashboard.
This report shows the evidence for tokenusage-cli@0.4.5. 0 of 14 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 10h ago · by lpm-firewall-aiThe package declares no install-time hook beyond prepublishOnly testing. Its scheduled tasks and OpenClaw setup are part of the explicit init flow, while Claude credentials go to Anthropic and disclosed aggregate run reports can be disabled.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user runs tokenusage init to configure integrations or hourly sync; usage checks occur during sync.
Impact
Expected collection of token usage and disclosed aggregate run metrics; no unauthorized credential transfer or unrelated persistence was found.
Mechanism
The CLI can register a scheduled task, install a selected OpenClaw integration, query Claude usage at Anthropic, and send aggregate run records to the configured backend.
AI rationale
The package declares no install-time hook beyond prepublishOnly testing. Its scheduled tasks and OpenClaw setup are part of the explicit init flow, while Claude credentials go to Anthropic and disclosed aggregate run reports can be disabled.
Network endpoints2
api.anthropic.com/api/oauth/usageConfigured backend function path: token-usage-sync-report
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The only lifecycle script is prepublishOnly, which runs tests; no install hook is declared.
- The hourly scheduled sync is registered by the init command and can be skipped with --no-task.
- OpenClaw setup in init runs only when the openclaw integration is selected.
- Claude OAuth usage requests send the token to api.anthropic.com, its own provider.
- The README describes aggregate sync reports and says they contain no paths, titles or message bodies.
- Run reporting can be disabled with the persisted runReport setting.
Evidence against
- The package registers hourly background tasks and supports OpenClaw integration setup.
- Run reporting is enabled by default and includes aggregate usage counters.
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
HighPrevious Version Dangerous Deltasrc/lib/scheduled-task.js
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.4.5.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of tokenusage-cli@0.4.5 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.