Recordspypisqlalchemy
Change the conditions
Current conditions
select @2.0.44musl · x64 · python
1 of 1 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 (1)
- Project observations
- 1 / 2
- Contract verifications
- 1 / 1
- Usage records
- 1
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 0 / 1
- Last recorded
- 2026-08-17
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
windows 11 · x64 · python 3.10 · pip 26
1 of 2 passed
Observed — real project builds reported from this coordinate.
-
alpine musl · x64 · python 3.12 · pip · python
1 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
2.0.51
windows · python@3.10
4 FAIL · stage: PROJECT_TEST
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.0.52 | 2.0.51 | 2.0.44 | 2.0.43 |
|---|---|---|---|---|
| greenlet | 3.5.5 | 3.5.4 | 3.5.6 | 3.5.5 |
| typing-extensions | 4.16.0 | 4.16.0 | 4.16.0 | 4.16.0 |
Moved: 1 · unchanged at every release: 1
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.