ghc/ghc

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.

https://github.com/ghc/ghc.git · scanned 2026-05-16 13:30 UTC (1 day, 8 hours ago) · 10 languages

249 findings (9 legacy + 240 scanner) 8/10 scanners ran Scanner says 84 (lower by 30)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 day, 11 hours ago · v2 · 128 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

100.0% cov · 120 gaps

{# ── 2026-05-17 R27 #5: score breakdown panel ────────────────────── Surfaces the score_breakdown JSON that's been silently stored on Repository for months. Turns hidden math into a trust signal. #}

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.

Fragile runtime 9 findings

What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.

Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.

How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.

Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).

9 matching findings on this repo

low Duplicated implementation block across source files rts/adjustor/NativeAmd64Mingw.c:20
low Duplicated implementation block across source files hadrian/bindist/cwrappers/getLocation.c:1
low Duplicated implementation block across source files hadrian/bindist/cwrappers/cwrapper.c:1
medium Network/subprocess call without timeout or try/except — .gitlab/rel_eng/fetch-g…
medium Network/subprocess call without timeout or try/except — testsuite/driver/testut…
medium Network/subprocess call without timeout or try/except — testsuite/driver/perf_n…
medium Network/subprocess call without timeout or try/except — docs/users_guide/compar…
medium Network/subprocess call without timeout or try/except — mk/get-win32-tarballs.p…
medium Network/subprocess call without timeout or try/except — hadrian/bootstrap/boots…

View all fragile runtime findings →

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

3 matching findings on this repo

low Legacy-named symbol `do_not_copy` in testsuite/driver/testlib.py:1564
low Legacy-named symbol `force_copy` in testsuite/driver/testutil.py:68
low Legacy-named symbol `cmp_legacy` in testsuite/driver/cpuinfo.py:1347

View all legacy markers findings →

Commented-out code 16 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 (5 lines) in compiler/jsbits/genSym.js:8
info Commented-code block (6 lines) in testsuite/tests/pmcheck/should_compile/genS.p…
info Commented-code block (5 lines) in testsuite/driver/testlib.py:205
info Commented-code block (6 lines) in testsuite/driver/runtests.py:21
info Commented-code block (5 lines) in testsuite/driver/perf_notes.py:72
info Commented-code block (6 lines) in testsuite/driver/testglobals.py:418
info Commented-code block (7 lines) in testsuite/driver/cpuinfo.py:14
info Commented-code block (6 lines) in docs/users_guide/flags.py:6
info Commented-code block (5 lines) in rts/js/mem.js:68
info Commented-code block (5 lines) in rts/js/string.js:225
info Commented-code block (7 lines) in rts/js/stableptr.js:21
info Commented-code block (7 lines) in rts/js/rts.js:365

View all commented-out code findings →

Config drift 2 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

2 matching findings on this repo

medium No CI/CD configuration found
low Possibly dead Python function: config_initiated docs/users_guide/rtd-theme/__init__.py:27

View all config drift findings →

{# ── 2026-05-17 Round 14: AI-agent bridge footer ────────────────────── Discoverability: the /agents/voting/ guide + MCP manifest exist but aren't linked from anywhere users actually land. Small, opt-in footer. #}

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/2375b6d0-a6b1-42a0-92ae-4a23b5c8f9ee/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/2375b6d0-a6b1-42a0-92ae-4a23b5c8f9ee/

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.