CodeSampleX

Recordsnpmpostcss-load-config4.0.2

Change the conditions
Fixed
Package version4.0.2
Filter OSalpine musl Runtimenode 22 Symbolwhole package Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

postcss-load-config @4.0.2alpine musl · x64 · node 22 · npm · node

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-08

Dependency Health

Observed combinations and failure evidence for this release

Steady 2

All 2 dependencies report steady passing evidence.

Library Version Health Measured there Projects
lilconfig 3.1.3 PASS All observations passed contract passed 2 project-days
yaml 2.9.0 PASS All observations passed contract passed 2 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.

Library6.0.14.0.2
lilconfig 3.1.3 3.1.3
yaml — 2.9.0

Moved: 0 · 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.