CodeSampleX

Recordsnpmnode-abi3.96.0node-abi.deprecatedTargets

Change the conditions
Fixed
Package version3.96.0 Symbolnode-abi.deprecatedTargets Package managernpm
Filter OSdebian glibc Runtimenode 22 Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

node-abi.deprecatedTargets @3.96.0debian glibc · x64 · node 22 · npm · node

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 (2)

Project observations
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-09-17

Dependency Health

Observed combinations and failure evidence for this release

Changed 1 · Steady 0

Dependency changes observed: 1. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
semver 7.8.5 CHANGED Version changed, no linked failure contract passed 30 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.35.04.34.04.33.03.96.03.95.03.94.0
semver 7.8.5 7.8.5 7.7.4 7.8.5 7.8.5 7.8.5

Moved: 1 · unchanged at every release: 0

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.