Recordsnpm@peculiar/asn1-schema2.9.3
Change the conditions
Current conditions
@peculiar/asn1-schema @2.9.3windows 11 · x64 · node 22 · npm 11 · node
package-level total, not an API
5 of 5 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (1)
- Project observations
- 5 / 5
- Contract verifications
- nothing at this coordinate
- Usage records
- 5
- Independent reporting peers
- 1
- Last recorded
- 2026-08-24
Dependency Health
Observed combinations and failure evidence for this release
First observed break
2.9.3
windows · node@24.13 · moduleSystem=cjs · executionContext=node
3 FAIL
· stage: UNKNOWN
· fingerprint: sha256:3e5f03903e292d9b19daef82b234201615ab763216b97feec6f325b598b3380d
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @peculiar/utils | 2.0.3 | PASS All observations passed | contract passed | 6 project-days |
| asn1js | 3.0.10 | PASS All observations passed | contract passed | 6 project-days |
| tslib | 2.8.1 | PASS All observations passed | contract passed | 6 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.
| Library | 2.9.4 | 2.9.3 | 2.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.