Click 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.
Embedded score card image
This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.
Issue title
Go Recover Without Log
Curate findings to include
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
Top 5 (default)
Issue body (markdown)
## Code-quality scan: `gin-gonic/gin`
**Score: 83/100 (B+)** · 84 findings · scanned 2026-06-05 07:00 UTC · 23,917 LOC
| Severity | Count |
|---|---|
| CRITICAL | 1 |
| HIGH | 73 |
| MEDIUM | 3 |
| LOW | 2 |
📊 [Full filterable report](https://repobility.com/scan/49e1c07a-fce2-4e25-965f-9ae544fa2dcb/) · 
### Top findings
1. **CRITICAL** `private-key` — Identified a Private Key, which may compromise cryptographic security and sensitive data e
`testdata/certificate/key.pem:1`
2. **HIGH** `MINED016` — Go Error Ignored
`render/json.go:73` · CWE-754 · ✓ Repobility
3. **HIGH** `MINED016` — Go Error Ignored
`render/data.go:24` · CWE-754 · ✓ Repobility
4. **HIGH** `MINED016` — Go Error Ignored
`render/bson.go:26` · CWE-754 · ✓ Repobility
5. **HIGH** `MINED033` — Go Recover Without Log
`recovery.go:60` · CWE-755 · ✓ Repobility
---
_Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/49e1c07a-fce2-4e25-965f-9ae544fa2dcb/_
Megaproject â high spam risk
Could not determine 'gin-gonic/gin' star count (GitHub API rate-limited or unreachable). When in doubt about repo size, prefer opening a focused PR or a discussion rather than an issue.
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.
