CodeSampleX

Recordscargojs-sys

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

Current conditions

js-sys @0.3.105alpine musl · x64 · rust 1 · cargo · rust

2 of 2 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 (2)

Project observations
4 / 4
Contract verifications
2 / 2
Usage records
2
Independent reporting peers
1
Last recorded
2026-11-14

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

Dependency Health

Observed combinations and failure evidence for this release

Changed 2 · Steady 1

Dependency changes observed: 2. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
cfg-if 1.0.5 CHANGED Version changed, no linked failure contract passed 7 project-days
wasm-bindgen 0.2.128 CHANGED Version changed, no linked failure contract passed 7 project-days
futures-util 0.3.34 PASS All observations passed contract passed 7 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.

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