ghc/ghc
ghc/ghcClick the green button below to open GitHub’s new-issue form, pre-filled with the report title, summary table, top findings, and an embedded score-card image. No authentication needed — you review on GitHub before submitting. Repobility is credited as the scanner.
This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.
No CI/CD configuration found
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `ghc/ghc` **Score: 74/100 (C-)** · 9 findings · scanned 2026-05-16 13:30 UTC · 72,479 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 2 | | MEDIUM | 3 | | LOW | 3 | 📊 [Full filterable report](https://repobility.com/scan/2375b6d0-a6b1-42a0-92ae-4a23b5c8f9ee/) ·  ### Top findings 1. **HIGH** `SEC035` — Unbounded Resource Allocation — DoS risk `docs/users_guide/conf.py:312` · CWE-770 · A04:2021 Insecure Design (DoS) 2. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input `mk/get-win32-tarballs.py:29` · A10:2021 SSRF 3. **MEDIUM** `CFG006` — Missing .gitignore 4. **MEDIUM** `SEC007` — Unsafe Deserialization `.gitlab/rel_eng/upload_ghc_libs.py:258` · A08:2021 Software & Data Integrity Failures 5. **MEDIUM** `CORE_NO_CI` — No CI/CD configuration found --- **Security note**: this issue is public. If any flagged finding is a real, exploitable vulnerability, please redirect to your `SECURITY.md` policy or open a [private security advisory](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability) instead. We're happy to close this and re-submit privately. --- _Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/2375b6d0-a6b1-42a0-92ae-4a23b5c8f9ee/_
The button opens GitHubâs new-issue page in a new tab. You will see the title + body pre-filled â review, edit if you want, then click GitHubâs "Submit new issue" button. Repobility never posts anything on your behalf.
For real security findings on big repos: use the project's SECURITY.md or
private advisory flow instead of a public issue.