Recordsnpmspdx-correct3.2.0
Change the conditions
Current conditions
spdx-correct @3.2.0debian glibc · 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
- 2
- Independent reporting peers
- 1
- Last recorded
- 2026-09-14
Evidence you can open
Dependency Health
Observed combinations and failure evidence for this release
Observed problems 1 ·
Unknown 1 ·
Steady 2
First observed break
3.2.0
linux · node@22.23 · executionContext=node · moduleSystem=cjs
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:986d98189e70ab6bb81e3ca5f5feb96281ba0dfa6e522caa6ddd3d9b148578cc
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| spdx-license-ids | 3.0.22 | UNKNOWN No linked outcome measured | nothing measured | 1 project-day |
| spdx-expression-parse | 3.0.1 | PASS All observations passed | contract passed | 6 project-days |
| spdx-license-ids | 3.0.23 | PASS All observations passed | contract passed | 3 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.
Recent failure clusters
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 3.2.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:986d98189e70…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-14 · Last seen: 2026-09-14Diagnostic re-verification candidate