CodeSampleX

Recordscargominiz_oxide0.9.1

Change the conditions
Fixed
Package version0.9.1 Package managercargo 1
Filter OSubuntu glibc Symbolwhole package Architecturex64 libcglibc Clear filters

Current conditions

miniz_oxide @0.9.1ubuntu glibc · x64 · cargo 1

package-level total, not an API

0 of 1 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
10 / 16
Contract verifications
0 / 1
Independent reporting peers
1
Last recorded
2026-09-19

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 2

First observed break

0.9.1

linux

2 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:40827ed6270443985b87902d50b257ee40df217d061c0098b7070f9287145dc9

Library Version Health Measured there Projects
adler2 2.0.1 PASS All observations passed contract passed 3 project-days
simd-adler32 0.3.10 PASS All observations passed contract passed 2 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.9.10.8.9
adler2 2.0.1 2.0.1
simd-adler32 0.3.10 —

Moved: 0 · unchanged at every release: 2

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