Recordspypisqlalchemy
Change the conditions
Current conditions
sqlalchemy.JSON @2.0.51musl · x64 · python
1 of 52 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and this coordinate records both a passing and a failing run of it (1)
- Project observations
- 397 / 424
- Contract verifications
- 1 / 52
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 23 / 27
- Last recorded
- 2026-09-01
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
windows 11 · x64 · python 3.10 · uv 0
0 of 51 passed
Verified — this network ran a contract at 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
| 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.