Recordspypirequests2.34.2
Change the conditions
Current conditions
requests @2.34.2debian glibc · x64 · python 3.12 · pip · python
package-level total, not an API
5 of 5 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (8)
- Project observations
- 12 / 12
- Contract verifications
- 5 / 5
- Usage records
- 6
- Independent reporting peers
- 1
- Last recorded
- 2026-09-17
Dependency Health
Observed combinations and failure evidence for this release
First observed break
2.34.2
windows · python@3.10
4 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| charset-normalizer | 3.4.9 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| idna | 3.18 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| certifi | 2026.7.22 | PASS All observations passed | contract passed | 5 project-days |
| urllib3 | 2.7.0 | PASS All observations passed | contract passed | 4 project-days |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | 2.34.2 | 2.32.5 |
|---|---|---|
| charset-normalizer | 3.4.9 | 3.5.1 |
| idna | 3.18 | 3.19 |
| certifi | 2026.7.22 | 2026.7.22 |
| urllib3 | 2.7.0 | — |
Moved: 2 · unchanged at every release: 2
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.