CodeSampleX

Recordspypinumba0.67.0

Change the conditions
Fixed
Package version0.67.0 Symbolwhole package Package manageruv 0
Filter OSubuntu glibc Runtimepython 3.12 Architecturex64 libcglibc Clear filters

Current conditions

numba @0.67.0ubuntu glibc · x64 · python 3.12 · uv 0

package-level total, not an API

1 of 1 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
1 / 1
Contract verifications
nothing at this coordinate
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 · Changed 2 · Steady 0

First observed break

0.67.0

linux · python@3.12

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
llvmlite 0.49.0 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
numpy 2.5.2 CANDIDATE Correlated change; unproven combination 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.

Library0.67.00.67.0rc1
llvmlite 0.49.0 0.49.0rc1
numpy 2.5.2 2.5.1

Moved: 2 · 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