CodeSampleX

Recordsnpmproxy-addr2.0.8

Change the conditions
Fixed
Runtimenode 24 Package version2.0.8
Filter OSwindows 11 Symbolwhole package Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

proxy-addr @2.0.8windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

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 / 2
Contract verifications
0 / 1
Usage records
2
Independent reporting peers
1
Last recorded
2026-09-26
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 2

First observed break

2.0.8

windows · node@24.13 · moduleSystem=esm · executionContext=node

1 FAIL · stage: PROJECT_TEST · fingerprint: sha256:e5d62c8db895569f759b66aa8be625284c284de63376f44003d140e8986c6f1a

View exact conditions View failure cluster
Library Version Health Measured there Projects
forwarded 0.2.0 PASS All observations passed contract passed 2 project-days
ipaddr.js 1.9.1 PASS All observations passed contract passed 2 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.0.82.0.7
forwarded 0.2.0 0.2.0
ipaddr.js 1.9.1 1.9.1

Moved: 0 · unchanged at every release: 2

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