Compatibilitynpm@bramus/specificity2.4.2@bramus/specificity.compare
Change the conditions
Current conditions
@bramus/specificity.compare @2.4.2ubuntu glibc · x64 · node 22 · npm 10 · node
0 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 failed
- Project observations
- 1 / 1
- Contract verifications
- 0 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-31
Evidence you can open
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| css-tree | 3.2.1 | contract passed | 1 project-day |
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 2.4.2 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 @bramus/specificity.compare 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-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 2.4.2 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:b9e50f8a45ca…<url>]:<n> …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate