kubernetes-sigs/headlamp
kubernetes-sigs/headlampClick 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.
Duplicated implementation block across source files
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `kubernetes-sigs/headlamp` **Score: 86/100 (B+)** · 34 findings · scanned 2026-05-15 11:08 UTC · 177,418 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 0 | | MEDIUM | 19 | | LOW | 6 | 📊 [Full filterable report](https://repobility.com/scan/5145cc36-1cd4-41ae-9163-2dd7117aa847/) ·  ### Top findings 1. **MEDIUM** `SEC007` — Unsafe Deserialization `frontend/src/stateless/deleteClusterKubeconfig.ts:69` · A08:2021 Software & Data Integrity Failures 2. **MEDIUM** `SEC007` — Unsafe Deserialization `frontend/src/stateless/findKubeconfigByClusterName.ts:68` · A08:2021 Software & Data Integrity Failures 3. **MEDIUM** `SEC007` — Unsafe Deserialization `frontend/src/stateless/updateStatelessClusterKubeconfig.ts:76` · A08:2021 Software & Data Integrity Failures 4. **MEDIUM** `SEC015` — Insecure Randomness for Security `frontend/src/redux/clusterActionSlice.ts:164` · A02:2021 Cryptographic Failures 5. **MEDIUM** `AIC003` — Duplicated implementation block across source files `frontend/src/components/App/Settings/ClusterSelector.stories.tsx:15` --- _Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/5145cc36-1cd4-41ae-9163-2dd7117aa847/_
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.