aeyakovenko/percolator
aeyakovenko/percolatorClick 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.
Python Open No Context
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `aeyakovenko/percolator` **Score: 91/100 (A-)** · 4 findings · scanned 2026-06-05 22:31 UTC · 25,333 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 2 | | MEDIUM | 1 | | LOW | 0 | 📊 [Full filterable report](https://repobility.com/scan/dff8a637-55cd-4aa5-a540-e6154745b8b0/) ·  ### Top findings 1. **HIGH** `SEC103` — LDAP injection — non-constant search filter `scripts/run_kani_full_audit.sh:25` · A03:2021 Injection 2. **HIGH** `RUSTSEC-2026-0097` — rand: RUSTSEC-2026-0097 `Cargo.lock` 3. **MEDIUM** `CORE_LARGE_FILES` — Average file size is 2533 lines (recommend <300) 4. **INFO** `MINED077` — Python Open No Context `scripts/restore_resolved_payout.py:60` · CWE-772 · ✓ Repobility --- **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/dff8a637-55cd-4aa5-a540-e6154745b8b0/_
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.