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

ghc/ghc

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
Combined
74.1
/100
Repobility
65
8 legacy
9-layer
84
100.0% cov · 120 gaps
Critical
1
click to filter
Agents
6
0 votes
Crowd
0
reported
{# ── 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
Severity: Critical 1 High 4 Medium 19 Low 76 Source: Legacy 8 9-layer 120 Crowd 0 Layer: Quality 54 Security 9 Software 40 Api 1 Frontend 22 Network 2

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Possible secret in .gitlab/rel_eng/upload_ghc_libs.py
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in .gitlab/rel_eng/upload_ghc_libs.py:254; move to env var / secrets manager.
.gitlab/rel_eng/upload_ghc_libs.py:254
#2
Insecure pattern 'eval_used' in ghc-interp.js:34
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
ghc-interp.js:34
#3
Insecure pattern 'eval_used' in rts/js/environment.js:460
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
rts/js/environment.js:460
#4
`dangerouslySetInnerHTML` used in a React component — utils/haddock/haddock-api/resources/html/quick-jump.min.js:1
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity
#5
`dangerouslySetInnerHTML` used in a React component — utils/haddock/haddock-api/resources/html/haddock-bundle.min.js:1
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity
#6
`dangerouslySetInnerHTML` used in a React component — utils/haddock/haddock-api/resources/html/js-src/quick-jump.tsx:350
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity
#7
Privileged port 17 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in .gitlab/ci.sh is a real port, change the binding to ≥1024 or run behind a proxy.
.gitlab/ci.sh
#8
Privileged port 36 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in .gitlab/ci.sh is a real port, change the binding to ≥1024 or run behind a proxy.
.gitlab/ci.sh
#9
No auth library detected
GapSeverity.MEDIUM Layer.SECURITY score 0.338
Why: medium severity
#10
Insecure pattern 'subprocess_shell_true' in testsuite/driver/testlib.py:723
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
testsuite/driver/testlib.py:723

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

{# ── 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.