Recordscargojs-sys0.3.104
Change the conditions
Current conditions
js-sys @0.3.104alpine musl · x64 · rust 1 · cargo · rust
package-level total, not an API
Recorded as present in projects. Nothing was run at this coordinate.
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (1)
- Project observations
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-08
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 1. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| wasm-bindgen | 0.2.127 | CHANGED Version changed, no linked failure | builds observed | 6 project-days |
| cfg-if | 1.0.5 | UNKNOWN No linked outcome measured | nothing measured | 2 project-days |
| cfg-if | 1.0.4 | PASS All observations passed | contract passed | 4 project-days |
| futures-util | 0.3.34 | PASS All observations passed | contract passed | 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.
| Library | 0.3.105 | 0.3.104 |
|---|---|---|
| wasm-bindgen | 0.2.128 | 0.2.127 |
| cfg-if | 1.0.5 | 1.0.5 |
| futures-util | 0.3.34 | 0.3.34 |
Moved: 1 · 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.