Recordscargozerovec0.11.8
Change the conditions
Current conditions
zerovec @0.11.8ubuntu glibc · x64 · cargo 1
package-level total, not an API
2 of 2 passed
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
- 2 / 2
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-14
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 |
|---|---|---|---|---|
| zerovec-derive | 0.11.6 | CHANGED Version changed, no linked failure | builds observed | 32 project-days |
| serde | 1.0.229 | PASS All observations passed | contract passed | 24 project-days |
| yoke | 0.8.3 | PASS All observations passed | builds observed | 30 project-days |
| zerofrom | 0.1.8 | PASS All observations passed | builds observed | 51 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.11.8 | 0.11.7 | 0.11.6 |
|---|---|---|---|
| zerovec-derive | 0.11.6 | 0.11.4 | 0.11.6 |
| serde | 1.0.229 | 1.0.229 | 1.0.229 |
| yoke | 0.8.3 | 0.8.3 | — |
| zerofrom | 0.1.8 | 0.1.8 | 0.1.8 |
Moved: 1 · unchanged at every release: 3
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.