Recordsnpmpostcss
Change the conditions
Current conditions
postcss.list @8.5.25x64 · node 22 · 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
- 2 / 2
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-30
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
alpine musl · x64 · node 22 · npm · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
ubuntu glibc · x64 · node 22 · npm 10 · node
2 of 2 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
8.5.26
windows · node@24.13 · moduleSystem=esm · executionContext=node
27 FAIL
· stage: UNKNOWN
· fingerprint: sha256:979755e6489d54fbc02ff712a1ad44c541d0fea0a79afc307d5bbd18aef3107a
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.