CodeSampleX

Recordsnpmpostcss-selector-parser7.1.1postcss-selector-parser.id

Change the conditions
Fixed
OSdebian glibc Symbolpostcss-selector-parser.id
Filter Runtimenode 22 Package version7.1.1 Architecturex64 Package managernpm Execution contextnode libcglibc Clear filters

Current conditions

postcss-selector-parser.id @7.1.1debian glibc · x64 · node 22 · npm · node

1 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (1)

Project observations
2 / 2
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-10-13

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
cssesc 3.0.0 PASS All observations passed contract passed 11 project-days
util-deprecate 1.0.2 PASS All observations passed contract passed 9 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: 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.