CodeSampleX

Recordscargoredox_syscall0.5.18

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

Current conditions

redox_syscall @0.5.18alpine 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
4
Independent reporting peers
1
Last recorded
2026-11-11

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 0

First observed break

0.5.18

linux

2 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:4c786cbbce8a4d62372582ec22f7ee5dde092da981551c703d9b07deb35c9524

Library Version Health Measured there Projects
bitflags 2.13.1 CANDIDATE Correlated change; unproven combination nothing measured 1 project-day
bitflags 2.13.2 CANDIDATE Correlated change; unproven combination builds observed 20 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.40.5.18
bitflags 2.13.2 2.13.1

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 13 recorded failure clusters. The rest are single reports.