google/material-design-icons
google/material-design-iconsClick 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.
High cognitive complexity: Function `main` has cognitive complexity 34 (SonarSource scale)
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `google/material-design-icons` **Score: 77/100 (B)** · 9 findings · scanned 2026-06-05 11:15 UTC · 0 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 5 | | MEDIUM | 1 | | LOW | 1 | 📊 [Full filterable report](https://repobility.com/scan/e0bade49-2d04-41a0-b852-29f7e0ddaf56/) ·  ### Top findings 1. **HIGH** `SEC103` — LDAP injection — non-constant search filter `update/update_repo.py:178` · A03:2021 Injection 2. **HIGH** `SEC078` — Python: requests without timeout `update/update_repo.py:104` · A05:2021 Security Misconfiguration 3. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input `update/update_repo.py:104` · A10:2021 SSRF 4. **HIGH** `SEC128` — Async function without await — fire-and-forget Promise (AI mistake) `update/icons.py:36` 5. **HIGH** `COMP001` — High cognitive complexity: Function `main` has cognitive complexity 34 (SonarSource scale) `update/update_repo.py:218` --- **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/e0bade49-2d04-41a0-b852-29f7e0ddaf56/_
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.