CodeSampleX

Recordsnpmspdx-expression-parse4.0.0

Change the conditions
Fixed
Package version4.0.0 Package manageryarn 4
Filter OSubuntu glibc Runtimenode 22 Symbolwhole package Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

spdx-expression-parse @4.0.0ubuntu glibc · x64 · node 22 · yarn 4 · node

package-level total, not an API

3 of 3 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
3 / 3
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-09-07
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Unknown 1 · Steady 2

First observed break

4.0.0

linux · node@22.23 · moduleSystem=cjs · executionContext=node

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
spdx-license-ids 3.0.22 UNKNOWN No linked outcome measured nothing measured 1 project-day
spdx-exceptions 2.5.0 PASS All observations passed contract passed 5 project-days
spdx-license-ids 3.0.23 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.

Library4.0.03.0.1
spdx-exceptions 2.5.0 2.5.0
spdx-license-ids 3.0.22 3.0.22

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.

Recent failure clusters