Recordsnpmpostcss8.5.25
Change the conditions
Current conditions
postcss @8.5.25alpine musl · x64 · node 22 · npm · node
package-level total, not an API
3 of 3 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 (3)
- Project observations
- 8 / 8
- Contract verifications
- 3 / 3
- Usage records
- 4
- Independent reporting peers
- 1
- Last recorded
- 2026-09-05
Dependency Health
Observed combinations and failure evidence for this release
First observed break
8.5.25
windows · executionContext=node
7 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| nanoid | 3.3.16 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| nanoid | 3.3.18 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| picocolors | 1.1.1 | PASS All observations passed | contract passed | 4 project-days |
| source-map-js | 1.2.1 | PASS All observations passed | contract passed | 4 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 | 8.5.28 | 8.5.26 | 8.5.25 | 8.5.6 | 8.4.31 |
|---|---|---|---|---|---|
| nanoid | 3.3.18 | 3.3.18 | 3.3.16 | 3.3.11 | 3.3.11 |
| picocolors | 1.1.1 | 1.1.1 | 1.1.1 | 1.1.1 | 1.1.1 |
| source-map-js | 1.2.1 | 1.2.1 | 1.2.1 | 1.2.1 | 1.2.1 |
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.