tock/tock

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.

67 of your 109 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 13.15s · analysis 14.7s · 39.2 MB · GitHub API rate-limit (preflight)

https://github.com/tock/tock · scanned 2026-06-06 00:51 UTC (4 days, 1 hour ago) · 10 languages

264 raw signals (102 security + 162 graph) 11/13 scanners ran 51st percentile · Rust · large (100-500K LoC) System graph score 91 (lower by 22)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 1 hour ago · v2 · 95 actionable findings from 2 signal sources. 88 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 61 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	100.0	0.25	25.00
`testing_score`	28.0	0.20	5.60
`documentation_score`	80.0	0.15	12.00
`practices_score`	72.0	0.15	10.80
`code_quality`	61.0	0.10	6.10
Overall		1.00	68.5

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 18 Medium 2 Low 56 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 34 System graph 61 Crowd 0 Layer: Quality 70 Software 16 Security 3 Cicd 4 Api 1 Frontend 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.

Duplicates & near-duplicates 4 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

4 matching findings on this repo

low Near-duplicate function bodies in 3 places
low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 18 places
low Near-duplicate function bodies in 4 places

View all duplicates & near-duplicates findings →

Commented-out code 6 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

6 matching findings on this repo

info Commented-code block (8 lines) in tools/debugging-and-development/print_tock_me…
info Commented-code block (6 lines) in tools/debugging-and-development/svd2regs/svd2…
info Commented-code block (6 lines) in tools/svd2regs/svd2regs.py:14
info Commented-code block (10 lines) in boards/apollo3/ambiq/ambiq_bin2board.py:24
info Commented-code block (10 lines) in boards/apollo3/ambiq/keys_info.py:24
info Commented-code block (10 lines) in boards/apollo3/ambiq/am_defines.py:24

View all commented-out code 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/c0959f70-06b2-4a06-a3db-a45c1498ba13/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/c0959f70-06b2-4a06-a3db-a45c1498ba13/

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.