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.
Sign up free Scan another repo

Vilhelm82/Lloyd_Engine_V4

https://github.com/Vilhelm82/Lloyd_Engine_V4 · scanned 2026-06-16 00:50 UTC (2 months, 1 week ago)

199 raw signals (0 security + 199 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 182 actionable findings from 1 signal source. 17 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
85.1
/100
Security checks
85
0 findings
System graph
85
66.7% cov · 182 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 0 Medium 10 Low 148 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 182 Crowd 0 Layer: Software 20 Frontend 1 Security 1 Cicd 1 Quality 159

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 repo-level
  • low Near-duplicate function bodies in 4 places repo-level
View all duplicates & near-duplicates findings →
Commented-out code 22 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 (8 lines) in scratch/foldreadback_probe0_v8_outcomelaw.py:…
  • info Commented-code block (5 lines) in scratch/blowup_exponent_v4_audit.py:96
  • info Commented-code block (5 lines) in scratch/phase2A_precision_scaling_boundary.py…
  • info Commented-code block (6 lines) in scratch/phase2B_adversarial_verify.py:105
  • info Commented-code block (5 lines) in scratch/bacl_multi_format_audit.py:241
  • info Commented-code block (5 lines) in scratch/c2_lattice_binade_danger_zone.py:119
  • info Commented-code block (5 lines) in scratch/substrate_fingerprint_atlas_phase_bet…
  • info Commented-code block (5 lines) in scratch/phase2B_subnormal_topology.py:426
  • info Commented-code block (7 lines) in scratch/_revalidation/clusterFb/check_claim3_…
  • info Commented-code block (7 lines) in scratch/_revalidation/retestA/f2_residual_flo…
  • info Commented-code block (5 lines) in scratch/_revalidation/retestC/retestC_common_…
  • info Commented-code block (11 lines) in src/lloyd_v4/primitives/typed_finite_differe…
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/043bd680-d522-45fa-b13f-ec086165698b/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/043bd680-d522-45fa-b13f-ec086165698b/

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.