Recordspypiscipy
Change the conditions
Current conditions
scipy @1.18.1ubuntu glibc · x64 · python 3.12 · pip
0 of 2 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed
- Project observations
- 6 / 6
- Contract verifications
- 0 / 2
- Independent reporting peers
- 3
- Last recorded
- 2026-09-02
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
0 of 2 passed
Verified — this network ran a contract at this coordinate.
-
scipy.sparse
1 of 1 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
1.18.1 numpy@2.5.2
linux · python@3.12
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9e6183e4b97fa15682c95a74b0c48c8ec186d7ab0affc9357739909beb749997
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| numpy | 2.5.2 | FAIL Linked failure observed; version changed across releases | contract passed | 4 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.