scikit-learn/scikit-learn
scikit-learn/scikit-learnClick 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.
Unsafe Deserialization
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `scikit-learn/scikit-learn` **Score: 74/100 (B+)** · 26 findings · scanned 2026-05-15 09:54 UTC · 445,841 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 0 | | MEDIUM | 18 | | LOW | 2 | 📊 [Full filterable report](https://repobility.com/scan/a5f73a3d-9c26-4983-8ec3-040adfc69698/) ·  ### Top findings 1. **MEDIUM** `SEC012` — ZipSlip — Archive Path Traversal `examples/applications/plot_out_of_core_classification.py:175` · A01:2021 Broken Access Control (path traversal) 2. **MEDIUM** `SEC012` — ZipSlip — Archive Path Traversal `sklearn/utils/fixes.py:348` · A01:2021 Broken Access Control (path traversal) 3. **MEDIUM** `SEC007` — Unsafe Deserialization `sklearn/utils/estimator_checks.py:2713` · A08:2021 Software & Data Integrity Failures 4. **MEDIUM** `SEC007` — Unsafe Deserialization `asv_benchmarks/benchmarks/common.py:176` · A08:2021 Software & Data Integrity Failures 5. **MEDIUM** `SEC007` — Unsafe Deserialization `benchmarks/bench_plot_randomized_svd.py:137` · A08:2021 Software & Data Integrity Failures --- _Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/a5f73a3d-9c26-4983-8ec3-040adfc69698/_
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.