CodeSampleX

Recordspypiscipy1.18.0

Change the conditions
Fixed
OSwindows 11 Symbolwhole package
Filter Runtimepython 3.10 Package version1.18.0 Architecturex64 Package manageruv 0 Clear filters

Current conditions

scipy @1.18.0windows 11 · x64 · python 3.10 · uv 0

package-level total, not an API

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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 0

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.

Library1.18.11.18.01.17.11.15.3
numpy 2.5.2 2.5.1 2.5.2 2.5.2

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.

Recent failure clusters

Showing the 12 most-reported of 67 recorded failure clusters. The rest are single reports.