← Back to scan
File as GitHub Issue repo: astral-sh/uv

Push this scan report to astral-sh/uv

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.

Repobility score card

Issue title

ZipSlip — Archive Path Traversal

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)
Severity Rule Title File:line
HIGH DKR006 Dockerfile pipes a remote script into a shell crates/uv-trampoline/Dockerfile:38
HIGH SEC013 [SEC013] Path Traversal — User Input in File Path: User-controlled input used in file pat… scripts/benchmark/src/benchmark/resolve…:228
HIGH SEC013 [SEC013] Path Traversal — User Input in File Path: User-controlled input used in file pat… scripts/publish-crates.py:80
HIGH SEC004 [SEC004] SQL Injection Risk: String interpolation in SQL execution. Allows SQL injection. scripts/update_schemastore.py:38
MED SEC012 [SEC012] ZipSlip — Archive Path Traversal: Archive extraction without path validation all… scripts/repair-sdist-cargo-lock.py:32
MED DKR007 Docker build context has no .dockerignore .dockerignore
MED AIC003 Duplicated implementation block across source files crates/uv-keyring/src/windows.rs:490
MED AIC003 Duplicated implementation block across source files crates/uv-keyring/src/secret_service.rs:438
MED AIC003 Duplicated implementation block across source files crates/uv-keyring/src/mock.rs:154
MED AIC003 Duplicated implementation block across source files crates/uv-installer/src/satisfies.rs:322
MED AIC003 Duplicated implementation block across source files crates/uv-install-wheel/src/uninstall.rs:312
MED AIC003 Duplicated implementation block across source files crates/uv-distribution/src/metadata/req…:190
MED AIC003 Duplicated implementation block across source files crates/uv-distribution/src/metadata/req…:152
MED AIC003 Duplicated implementation block across source files crates/uv-dev/src/generate_sysconfig_ma…:50
MED AIC003 Duplicated implementation block across source files crates/uv-dev/src/generate_sysconfig_ma…:28
MED AIC003 Duplicated implementation block across source files crates/uv-dev/src/generate_options_refe…:25
MED AIC003 Duplicated implementation block across source files crates/uv-dev/src/generate_options_refe…:11
MED AIC003 Duplicated implementation block across source files crates/uv-configuration/src/sources.rs:30
MED DKR001 Docker final stage has no non-root USER crates/uv-trampoline/Dockerfile:63
MED AGT015 Remote install command pipes network code directly to a shell docs/reference/installer.md:57
MED AGT015 Remote install command pipes network code directly to a shell docs/getting-started/installation.md:16
MED CORE_LARGE_FILES Average file size is 732 lines (recommend <300) —
LOW DKR011 Dockerfile installs recommended OS packages crates/uv-trampoline/Dockerfile:28
LOW AIC002 Source file name looks like an AI patch artifact crates/uv/src/commands/self_update.rs:1
LOW AIC002 Source file name looks like an AI patch artifact crates/uv/src/commands/cache_clean.rs:1
Reset to top 5 25 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `astral-sh/uv`

**Score: 73/100 (B+)**  ·  29 findings  ·  scanned 2026-05-16 09:40 UTC  ·  488,470 LOC

| Severity | Count |
|---|---|
| CRITICAL | 0 |
| HIGH | 4 |
| MEDIUM | 18 |
| LOW | 3 |

📊 [Full filterable report](https://repobility.com/scan/9d80afe6-b891-4d50-b2cd-9006567d3dc2/)  ·  ![scorecard](https://repobility.com/scan/9d80afe6-b891-4d50-b2cd-9006567d3dc2/report.png?v=1778924415-s2)

### Top findings

1. **HIGH** `DKR006` — Dockerfile pipes a remote script into a shell
   `crates/uv-trampoline/Dockerfile:38`
2. **HIGH** `SEC013` — Path Traversal — User Input in File Path
   `scripts/benchmark/src/benchmark/resolver.py:228` · A01:2021 Broken Access Control (path traversal)
3. **HIGH** `SEC013` — Path Traversal — User Input in File Path
   `scripts/publish-crates.py:80` · A01:2021 Broken Access Control (path traversal)
4. **HIGH** `SEC004` — SQL Injection Risk
   `scripts/update_schemastore.py:38` · A03:2021 Injection
5. **MEDIUM** `SEC012` — ZipSlip — Archive Path Traversal
   `scripts/repair-sdist-cargo-lock.py:32` · A01:2021 Broken Access Control (path traversal)

---

**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/9d80afe6-b891-4d50-b2cd-9006567d3dc2/_
Premium account
This scan was submitted by a Enterprise-tier account. Premium accounts have full outreach control â Repobility doesn't pre-fill the 'file as GitHub issue' button for paid users. You can still file the issue manually using the markdown body above (Copy markdown), or contact us if you'd like batch-filing enabled for your account.
Already filed
This repo publishes a SECURITY.md policy and the scan contains 3 Critical/High security finding(s). Public issue filing would violate coordinated disclosure. Submit privately via the project's security reporting channel.
Megaproject â high spam risk
Could not determine 'astral-sh/uv' 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.
Cancel

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.