CodeSampleX

Recordsnpmpostcss8.5.26postcss.Container

Change the conditions
Fixed
OSubuntu glibc Symbolpostcss.Container
Filter Runtimenode 22 Package version8.5.26 Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

postcss.Container @8.5.26ubuntu glibc · x64 · node 22 · npm 10 · node

1 of 1 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
1 / 1
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-08-31

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 2

First observed break

8.5.26

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

27 FAIL · stage: UNKNOWN · fingerprint: sha256:979755e6489d54fbc02ff712a1ad44c541d0fea0a79afc307d5bbd18aef3107a

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

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