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.
100 of your 144 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 1.72s · analysis 19.76s · 4.2 MB · GitHub API rate-limit (preflight)

jsiek/deduce

https://github.com/jsiek/deduce · scanned 2026-06-05 14:50 UTC (5 days, 4 hours ago) · 10 languages

428 raw signals (138 security + 290 graph) 88th percentile · Python · medium (20-100K LoC) System graph score 79 (higher by 4)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 100.0 0.15 15.00
security_score 83.1 0.25 20.77
testing_score 100.0 0.20 20.00
documentation_score 83.0 0.15 12.45
practices_score 72.0 0.15 10.80
code_quality 42.4 0.10 4.24
Overall 1.00 83.3
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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 3 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.
3 matching findings on this repo
  • low Near-duplicate function bodies in 2 places repo-level
  • low Near-duplicate function bodies in 3 places
  • low Near-duplicate function bodies in 6 places repo-level
View all duplicates & near-duplicates findings →
Commented-out code 48 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 checker_proofs.py:57
  • info Commented-code block (6 lines) in parser.py:225
  • info Commented-code block (8 lines) in checker_predicates.py:97
  • info Commented-code block (5 lines) in checker_cache.py:32
  • info Commented-code block (5 lines) in rec_desc_parser.py:126
  • info Commented-code block (5 lines) in checker_pipeline.py:190
  • info Commented-code block (5 lines) in checker_logic.py:433
  • info Commented-code block (5 lines) in flags.py:28
  • info Commented-code block (9 lines) in error.py:24
  • info Commented-code block (5 lines) in checker_common.py:26
  • info Commented-code block (6 lines) in checker_types.py:291
  • info Commented-code block (8 lines) in test-deduce.py:65
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/f2d99d98-d908-4ba5-a560-fb38bda710cd/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/f2d99d98-d908-4ba5-a560-fb38bda710cd/

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.