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.

wilcompute/W33-Theory

https://github.com/wilcompute/W33-Theory · scanned 2026-06-16 01:03 UTC (2 months, 1 week ago)

1178 raw signals (0 security + 1178 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 1067 actionable findings from 1 signal source. 111 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 · 1067 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 30 Medium 102 Low 228 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 1067 Crowd 0 Layer: Software 47 Data 1 Frontend 1 Security 36 Cicd 3 Quality 979

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 10 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.

10 matching findings on this repo

low Near-duplicate function bodies in 22 places
low Near-duplicate function bodies in 138 places
low Near-duplicate function bodies in 124 places
low Near-duplicate function bodies in 9 places
low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 6 places
low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 11 places
low Near-duplicate function bodies in 5 places
low Near-duplicate function bodies in 4 places

View all duplicates & near-duplicates findings →

Legacy markers 74 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.

12 matching findings on this repo

low Very large file: legacy/root_solvers/MASTER_SOLVER.py (1340 lines)
low Old/deprecated-named symbol `voevodsky_legacy` in tests/test_motivic_homotopy.p…
low Old/deprecated-named symbol `voevodsky_legacy` in pillars/THEORY_PART_CCLIV_MOT…
low Old/deprecated-named symbol `sin2_th12_legacy` in scripts/w33_conflict_clearanc…
low Old/deprecated-named symbol `nufit53_legacy` in scripts/SOLVE_RG_NEUTRINO.py:9
info Commented-code block (5 lines) in legacy/one_off_root/phase5_computations.py:52
info Commented-code block (5 lines) in legacy/one_off_root/_explore31b.py:429
info Commented-code block (5 lines) in legacy/one_off_root/_explore_L.py:82
info Commented-code block (6 lines) in legacy/one_off_root/phase7_april2026.py:60
info Commented-code block (7 lines) in legacy/one_off_root/_explore_LI2.py:103
info Commented-code block (6 lines) in legacy/one_off_root/_explore_L2.py:97
low Old/deprecated-named symbol `r_adj_v2` in legacy/one_off_root/_explore_LII.py:5…

View all legacy markers findings →

Commented-out code 705 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/`.

12 matching findings on this repo

info Commented-code block (6 lines) in explore_kirchhoff_clustering.py:74
info Commented-code block (5 lines) in BT389_CKM_WOLFENSTEIN.py:60
info Commented-code block (6 lines) in SOLVE_IT.py:93
info Commented-code block (6 lines) in FINAL_SOLVER.py:651
info Commented-code block (5 lines) in deep_computations.py:86
info Commented-code block (5 lines) in W33_MASTER_IDENTITY.py:129
info Commented-code block (5 lines) in verify_w33_golden_ratio_structure.py:64
info Commented-code block (5 lines) in explore_spreads_codes.py:48
info Commented-code block (6 lines) in explore_twograph2.py:246
info Commented-code block (7 lines) in SOLVE_PLANCK_EW_HIERARCHY.py:100
info Commented-code block (9 lines) in PART_CLIV_SRG_DERIVED_FROM_RING.py:94
info Commented-code block (5 lines) in verify_w33_mW_exact.py:128

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/d240618d-a7b6-4eb7-9184-9ca0d220bdb7/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/d240618d-a7b6-4eb7-9184-9ca0d220bdb7/

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.