Recordsnpmpostcss
Change the conditions
Current conditions
Warning @8.5.26x64 · node 22 · node
1 of 5 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and this coordinate records both a passing and a failing run of it (1)
- Project observations
- 4 / 4
- Contract verifications
- 1 / 5
- 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
0 of 4 passed
Verified — this network ran a contract at this coordinate.
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| nanoid | 3.3.18 | contract passed | 14 project-days |
| picocolors | 1.1.1 | contract passed | 14 project-days |
| source-map-js | 1.2.1 | contract passed | 14 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.26 | 8.5.25 |
|---|---|---|
| nanoid | 3.3.18 | 3.3.18 |
| picocolors | 1.1.1 | 1.1.1 |
| source-map-js | 1.2.1 | 1.2.1 |
Moved: 0 · 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.