Recordsnpmsharp0.35.2sharp.composite
Change the conditions
Current conditions
sharp.composite @0.35.2alpine musl · x64 · node 22 · npm · node
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
- nothing at this coordinate
- Contract verifications
- 1 / 1
- Last recorded
- 2026-08-20
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 2. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @img/colour | 1.1.0 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| semver | 7.8.5 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| detect-libc | 2.1.2 | PASS All observations passed | contract passed | 1 project-day |
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.35.4 | 0.35.2 | 0.34.5 |
|---|---|---|---|
| @img/colour | 1.1.0 | 1.1.0 | 1.0.0 |
| semver | 7.8.5 | 7.8.5 | 7.7.3 |
| detect-libc | 2.1.2 | 2.1.2 | 2.1.2 |
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.