Recordspypisqlalchemy
Change the conditions
Current conditions
sqlalchemy @2.0.51debian glibc · x64 · python 3.12 · pip · python
11 of 11 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 (25)
- Project observations
- 12 / 12
- Contract verifications
- 11 / 11
- Usage records
- 6
- Independent reporting peers
- 1
- Last recorded
- 2026-09-04
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
11 of 11 passed
Verified — this network ran a contract at this coordinate.
-
sqlalchemy.Table
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
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| greenlet | 3.5.4 | FAIL Linked failure observed on this release | contract passed | 6 project-days |
| greenlet | 3.5.5 | FAIL Linked failure observed on this release | contract passed | 8 project-days |
| typing-extensions | 4.16.0 | FAIL Linked failure observed on this release | contract passed | 14 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.