Recordspypiscipy
Change the conditions
Current conditions
scipy @1.18.0windows 11 · x64 · python 3.10 · uv 0
0 of 51 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed (2)
- Project observations
- 397 / 424
- Contract verifications
- 0 / 51
- Usage records
- 1
- 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.
-
0 of 51 passed
Verified — this network ran a contract at this coordinate.
-
scipy.ndimage
0 of 51 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
1.18.0 numpy@2.5.1
windows · python@3.10
4 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| numpy | 2.5.1 | FAIL Linked failure observed; version changed across releases | 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.
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.
Moved: 1 · unchanged at every release: 0
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.