stormzhang/token-tracker

Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

Scan timing: clone 2.65s · analysis 0.39s · 1.2 MB · GitHub API rate-limit (preflight)

https://github.com/stormzhang/token-tracker · scanned 2026-05-31 01:22 UTC (5 days, 14 hours ago) · 10 languages

40 findings (16 legacy + 24 scanner) 26th percentile · Python · small (2-20K LoC) Scanner says 98 (lower by 39)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 14 hours ago · v2 · 28 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	100.0	0.15	15.00
`security_score`	96.9	0.25	24.23
`testing_score`	0.0	0.20	0.00
`documentation_score`	44.0	0.15	6.60
`practices_score`	40.0	0.15	6.00
`code_quality`	66.9	0.10	6.69
Overall		1.00	58.5

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 3 Medium 5 Low 10 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 16 9-layer 12 Crowd 0 Layer: Quality 16 Security 2 Software 7 Api 1 Frontend 1 Cicd 1

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Fragile runtime 9 findings

What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.

Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.

How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.

Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).

9 matching findings on this repo

medium [COMP001] High cognitive complexity: Function `_parse_jsonl` has cognitive comp… src/adapters/claude.py:78
medium Bare except continues silently src/analyzer/cost.py:71
medium Codex session log reader may expose prompts or tool-call content src/adapters/codex.py:9
low [COMP001] High cognitive complexity: Function `_parse_assistant_entry` has cogn… src/adapters/claude.py:115
info [MINED050] Stub Only Function: Function declared but body is just pass, return … src/analyzer/cost.py:67
info [MINED050] Stub Only Function: Function declared but body is just pass, return … src/adapters/claude.py:112
high [COMP001] High cognitive complexity: Function `_parse_jsonl` has cognitive comp… src/adapters/codex.py:143
high [MINED001] Bare Except Pass: except: pass or except Exception: pass — silently … src/analyzer/cost.py:66
high [MINED001] Bare Except Pass: except: pass or except Exception: pass — silently … src/adapters/claude.py:111

View all fragile runtime findings →

Legacy markers 2 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

2 matching findings on this repo

low Legacy-named symbol `codex_backup` in src/i18n.py:79
low Legacy-named symbol `codex_backup` in src/hooks.py:434

View all legacy markers findings →

Config drift 1 finding

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

1 matching finding on this repo

medium No CI/CD configuration found

View all config drift findings →

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/51a74ba1-3827-4fd0-8913-2687abfa7d1d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/51a74ba1-3827-4fd0-8913-2687abfa7d1d/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.