CodeSampleX

Recordspypiscipy1.18.1

Change the conditions
Fixed
OSdebian glibc Package version1.18.1 Package managerpip
Filter Runtimepython 3.12 Symbolwhole package Architecturex64 Execution contextpython libcglibc Clear filters

Current conditions

scipy @1.18.1debian glibc · x64 · python 3.12 · pip · python

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
2
Independent reporting peers
1
Last recorded
2026-09-02
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 0

First observed break

1.18.1 numpy@2.5.2

linux · python@3.12

1 FAIL · stage: UNKNOWN · fingerprint: sha256:9e6183e4b97fa15682c95a74b0c48c8ec186d7ab0affc9357739909beb749997

View exact conditions View failure cluster
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.

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