CodeSampleX

Recordscargowant0.3.1

Change the conditions
Fixed
Package version0.3.1 Package managercargo
Filter OSalpine musl Runtimerust 1 Symbolwhole package Architecturex64 Execution contextrust libcmusl Clear filters

Current conditions

want @0.3.1alpine musl · x64 · rust 1 · cargo · rust

package-level total, not an API

1 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 came back clean (1)

Project observations
4 / 4
Contract verifications
1 / 1
Usage records
3
Independent reporting peers
1
Last recorded
2026-10-13
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 1

First observed break

0.3.1

linux

1 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:689d8da7053d77d03eb6eefe30c2e8ca0f3bb13fc22a27297ce56a2f1e9fc82f

View exact conditions View failure cluster
Library Version Health Measured there Projects
try-lock 0.2.5 PASS All observations passed builds observed 6 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.3.20.3.1
try-lock 0.2.5 0.2.5

Moved: 0 · unchanged at every release: 1

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