Recordspypisqlalchemy
Change the conditions
Current conditions
alembic.script.ScriptDirectory @2.0.52x64 · python 3.12 · pip · python
3 of 3 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
- nothing at this coordinate
- Contract verifications
- 3 / 3
- Cross-checked
- reproduced by two or more independent peers
- Last recorded
- 2026-09-08
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
debian glibc · x64 · python 3.12 · pip · python
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
alpine musl · x64 · python 3.12 · pip · python
2 of 2 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 1. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| greenlet | 3.5.5 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| typing-extensions | 4.16.0 | PASS All observations passed | contract passed | 1 project-day |
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.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.