Recordspypijsonschema4.26.0
Change the conditions
Current conditions
jsonschema @4.26.0alpine musl · x64 · python 3.12 · pip · python
package-level total, not an API
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
- 2 / 2
- Contract verifications
- 1 / 1
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-05
Evidence you can open
Dependency Health
Observed combinations and failure evidence for this release
Observed problems 1 ·
Steady 4
First observed break
4.26.0
windows · python@3.10
4 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| attrs | 26.1.0 | PASS All observations passed | contract passed | 7 project-days |
| jsonschema-specifications | 2025.9.1 | PASS All observations passed | contract passed | 7 project-days |
| referencing | 0.37.0 | PASS All observations passed | contract passed | 7 project-days |
| rpds-py | 2026.6.3 | PASS All observations passed | contract passed | 7 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.