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: layer: quality × 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

Scan summary Repository scanned at 97.5/100 with 77.8% coverage. It contains 127 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 12 findings — concentrated in software (4), quality (4), api (1). Risk profile is low: 0 critical, 0 high, 3 medium. Recommended next step: open the software layer findings first — that's where the highest-impact wins live.

Showing 9 of 28 findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

low Legacy quality quality conf 1.00 ✓ Repobility [MINED001] Bare Except Pass: except: pass or except Exception: pass — silently swallows everything including KeyboardInterrupt and bugs.

Review and fix per the pattern semantics. See CWE-755 / for context.

src/analyzer/cost.py:66 qualitylegacy

low Legacy quality quality conf 1.00 ✓ Repobility [MINED001] Bare Except Pass: except: pass or except Exception: pass — silently swallows everything including KeyboardInterrupt and bugs.

Review and fix per the pattern semantics. See CWE-755 / for context.

src/adapters/claude.py:111 qualitylegacy

high Legacy quality quality conf 1.00 ✓ Repobility Bare except continues silently

Bare `except:` (or `except Exception:`) that runs code without re-raising or logging the exception. Hides real failures and makes bugs hard to diagnose.

src/analyzer/cost.py:71 qualitylegacy

medium Legacy quality quality conf 0.73 Codex session log reader may expose prompts or tool-call content

Codex session JSONL files can contain prompts, tool events, paths, and operational metadata, not only token counts. Token dashboards and exporters should avoid retaining or sharing raw session text.

src/adapters/codex.py:9 qualitylegacy

medium 9-layer quality tests conf 1.00 Very low test-to-source ratio

0 test file(s) for 16 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.

testscoverage

low Legacy quality documentation No LICENSE file

Add a LICENSE file to your repository. Use choosealicense.com to pick the right license (MIT for permissive, Apache 2.0 for patent protection, GPL for copyleft).

documentationlegacy

low 9-layer quality integrity conf 1.00 Legacy-named symbol `codex_backup` in src/hooks.py:434

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

integritylegacy-markerdead-code

low 9-layer quality integrity conf 1.00 Legacy-named symbol `codex_backup` in src/i18n.py:79

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

integritylegacy-markerdead-code

low 9-layer quality integrity conf 1.00 Near-duplicate function bodies in 4 places

Functions with the same first-5-line body hash: src/ui/tables.py:render_daily, src/ui/tables.py:render_weekly, src/ui/tables.py:render_monthly, src/ui/tables.py:render_sessions This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consol…

integrityduplicatedry

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.