CodeSampleX

Recordsnpmpostcss8.5.6

Change the conditions
Fixed
OSwindows Package version8.5.6 Package managernpm 11
Filter Runtimenode 24 Symbolwhole package Architecturex64 Execution contextnode Clear filters

Current conditions

postcss @8.5.6windows · x64 · node 24 · npm 11 · node

package-level total, not an API

0 of 9 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed (3)

Project observations
19 / 66
Contract verifications
0 / 9
Usage records
45
Independent reporting peers
1
Last recorded
2026-09-01

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 2

First observed break

8.5.6

windows · node@24.13 · moduleSystem=cjs · executionContext=node

8 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:0470f88d95bb52932e5704cdc30cfcecbd43ae71af54d4c5f93d16aa27317cd2

Library Version Health Measured there Projects
nanoid 3.3.11 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
picocolors 1.1.1 PASS All observations passed contract passed 1 project-day
source-map-js 1.2.1 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.

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.

Recent failure clusters

Showing the 12 most-reported of 27 recorded failure clusters. The rest are single reports.