CodeSampleX

Recordsnpmpostcss8.5.28

Change the conditions
Fixed
Package version8.5.28 Package managernpm 10
Filter OSubuntu glibc Runtimenode 22 Symbolwhole package Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

postcss @8.5.28ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 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 failed

Project observations
25 / 25
Contract verifications
0 / 3
Usage records
1
Independent reporting peers
2
Last recorded
2026-09-04

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 2

First observed break

8.5.28

linux · node@22.23 · executionContext=node

8 FAIL · stage: UNKNOWN · fingerprint: sha256:986d98189e70ab6bb81e3ca5f5feb96281ba0dfa6e522caa6ddd3d9b148578cc

Library Version Health Measured there Projects
nanoid 3.3.18 CANDIDATE Correlated change; unproven combination contract passed 4 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.

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