CodeSampleX

Recordspypirequests

Change the conditions
Fixed
Package version2.34.2 Symbolrequests.Response
Filter Architecturex64 Execution contextpython libcmusl Clear filters

Current conditions

requests.Response @2.34.2musl · x64 · python

2 of 2 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 (2)

Project observations
1 / 1
Contract verifications
2 / 2
Independent reporting peers
1
Cross-checked
reproduced by two or more independent peers
Last recorded
2026-08-18

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 2

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.

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.