CodeSampleX

Recordsnpm@peculiar/asn1-schema2.9.4

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

Current conditions

@peculiar/asn1-schema @2.9.4alpine musl · x64 · node 22 · npm · node

package-level total, not an API

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
Usage records
1
Independent reporting peers
1
Last recorded
2026-08-30
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 3

First observed break

2.9.4

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

1 FAIL · stage: PROJECT_PROCESS

View exact conditions View failure cluster
Library Version Health Measured there Projects
@peculiar/utils 2.0.3 PASS All observations passed contract passed 4 project-days
asn1js 3.0.10 PASS All observations passed contract passed 4 project-days
tslib 2.8.1 PASS All observations passed contract passed 4 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.

Library2.9.42.9.32.8.0
@peculiar/utils 2.0.3 2.0.3 2.0.3
asn1js 3.0.10 3.0.10 3.0.10
tslib 2.8.1 2.8.1 2.8.1

Moved: 0 · unchanged at every release: 3

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