registry / tokenusage-cli / 0.3.0
tokenusage-cli@0.3.0
Self-hosted AI coding token usage collector for the Token Usage dashboard.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe manifest has no install-time execution hook, and the flagged setup behavior is reached through the explicit init flow. Session uploads are designed to send usage fields while excluding local project paths and other sidecar-only data, consistent with the package's dashboard purpose.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Explicit CLI use, including init, sync, and setup of detected integrations.
Impact
Usage metrics are collected for the dashboard. No unauthorized credential transfer, unrelated account action, or harmful persistence was identified.
Mechanism
Sync queries provider usage APIs and uploads whitelisted session usage fields to the configured ingest service; init may register an hourly Windows task and install detected agent integrations.
AI rationale
The manifest has no install-time execution hook, and the flagged setup behavior is reached through the explicit init flow. Session uploads are designed to send usage fields while excluding local project paths and other sidecar-only data, consistent with the package's dashboard purpose.
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exposes a CLI and has no install, preinstall, or postinstall hook; its only lifecycle script is prepublishOnly.
- The initial sync runs as part of the explicit init flow, and the Windows hourly sync task is registered by that setup flow.
- Session uploads are described as sending whitelisted usage fields while excluding titles, local project paths, resume identifiers, and cache keys.
Evidence against
- The package accesses provider APIs and sends session usage data to its configured ingest service as part of its token-usage collection purpose.
- Init installs integrations for detected agent tools, including the OpenClaw session plugin, as part of user-requested setup.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
7 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
4 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
HighPrevious Version Dangerous Deltasrc/lib/session-upload.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
Affected versions and remediation
This report applies to tokenusage-cli@0.3.0.
See all versions of tokenusage-cli for other recorded verdicts.
- Review the evidence and your use of tokenusage-cli@0.3.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.