Read 2026-10-04
pypa/pip: technical due diligence, read from its repository
What Borehole read in pypa/pip's code and history at a7002c9: its licence, security advisories, releases, review practice, tests, dependencies and operations. Every finding cites the file and line it rests on. The full report also covers the team and asks the questions the code cannot answer.
| Dimension | Rating |
|---|---|
| Architecture & Codebase — including AI provenance | strong |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | strong |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
.github/CONTRIBUTING.md:8: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongsrc/pip/_internal/cli/cmdoptions.py is 1,410 lines, 13× this codebase's median file
adequateThe median source file here is 104 lines. 2 files exceed 1,040 lines, the largest being 1,410. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.
src/pip/_internal/cli/cmdoptions.py:1 — 1,410 lines (13× median) |
src/pip/_internal/index/package_finder.py:1 — 1,153 lines (11× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
strong7 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-09-29. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 1 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 26.2.1. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 11 records name pip with nothing tying them to this repository (CVE-2013-5123, CVE-2024-21574, CVE-2025-61774, …).
| 2026-09-29: CVE-2026-102930 (high): virtualenv is a tool for creating isolated virtual python environments. Prior to 21.7.12, download_wheel() accepts pip and setuptools seed wheels fetched for pe |
| 2026-07-29: GHSA-qwm4-qh6w-59xr (moderate), fixed in 26.2.0: pip would incorrectly handle doubly-encoded package URLs from indexes |
| 2026-06-01: GHSA-wf93-45jw-7689 (moderate), fixed in 26.1.2: pip: Path traversal in console_scripts/gui_scripts entry point names allows installing scripts outside of target directory |
| 2026-04-27: GHSA-jp4c-xjxw-mgf9 (moderate), fixed in 26.1: pip Vulnerable to Inclusion of Functionality from Untrusted Control Sphere |
| 2026-04-20: GHSA-58qw-9mgm-455v (moderate), fixed in 26.1: pip has an interpretation conflict due to handling both concatenated tar and ZIP files as ZIP files |
Observability & Operations
not assessableNot rated: only 5 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on pypa/pip: every dimension, the questions for the room, and the audit log.
Survey a repository: free on public repositories. Private code is read on your own machine by a collector whose source you can read first.