registry  /  @geeeger/ocusage  /  3.9.0

@geeeger/ocusage@3.9.0

AI client daily token usage report CLI — supports OpenCode, MiMoCode, Qoder, Claude Code, CodeWhale, and more

AI Security Review

scanned 2h ago · by lpm-firewall-ai

No confirmed malicious attack surface. The main sensitive behavior is user-invoked local AI usage inspection, including optional Trae database key extraction/decryption for reporting.

Static reason
No blocking static signals were detected.
Trigger
User runs ocusage CLI, especially with Trae selected or all clients enabled.
Impact
Reads local AI usage records and may store a Trae SQLCipher key locally; no network exfiltration or install-time mutation found.
Mechanism
Local filesystem/database parsing and Windows-only Trae process memory key extraction
Rationale
The package is a local token-usage reporting CLI with sensitive but documented, user-invoked local reads and Trae decryption support. Source inspection found no install-time execution, network exfiltration, remote payload loading, destructive behavior, or AI-agent control-surface mutation.
Evidence
package.jsoncli.mjsconfig.mjscommands/config.mjsproviders/index.mjsproviders/base.mjsproviders/trae.mjsproviders/helpers/trae-key-extract.mjsproviders/helpers/trae-crypto.mjsscripts/extract-trae-key.ps1README.mduser ocusage config.jsontemporary ocusage-trae-*/decrypted.db

Decision evidence

public snapshot
AI called this Clean at 88.0% confidence as Benign with medium false-positive risk.
Evidence for block
  • providers/helpers/trae-key-extract.mjs runs powershell.exe to scan Trae process memory for SQLCipher keys on Windows.
  • scripts/extract-trae-key.ps1 uses OpenProcess/ReadProcessMemory against Trae.exe and returns key candidates.
  • config.mjs can persist extracted encryption keys in user config.
Evidence against
  • package.json has only prepare husky; no preinstall/install/postinstall execution.
  • cli.mjs exposes user-invoked CLI commands; no import-time payload or hidden lifecycle behavior found.
  • Providers read local AI client SQLite/JSON/JSONL usage data and aggregate token statistics.
  • No fetch/http client, exfiltration endpoint, credential upload, destructive deletion, or persistence mechanism found.
  • Trae memory/key behavior is package-aligned with documented local SQLCipher usage reporting.
Behavioral surface
Source
ChildProcessCryptoEnvironmentVarsFilesystemShell
Supply chain
HighEntropyStrings
ManifestNo manifest risk signals triggered.
scanned 25 file(s), 143 KB of source

Source & flagged code

1 flagged · loading source
scripts/extract-trae-key.ps1View file
•path = scripts/extract-trae-key.ps1 kind = build_helper sizeBytes = 7116 magicHex = [redacted]
Medium
Ships Build Helper

Package ships non-JavaScript build or shell helper files.

scripts/extract-trae-key.ps1View on unpkg

Findings

3 Medium4 Low
MediumEnvironment Vars
MediumShips Build Helperscripts/extract-trae-key.ps1
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings