CodeSampleX

Recordsnpm@modelcontextprotocol/sdk1.30.0@modelcontextprotocol/sdk.Client

Change the conditions
Fixed
Runtimenode 24 Symbol@modelcontextprotocol/sdk.Client
Filter OSwindows 11 Package version1.30.0 Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

@modelcontextprotocol/sdk.Client @1.30.0windows 11 · x64 · node 24 · npm 11 · node

0 of 12 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed (1)

Project observations
103 / 128
Contract verifications
0 / 12
Independent reporting peers
1
Failures with a captured fingerprint
1 / 25
Last recorded
2026-11-18

Dependency Health

Observed combinations and failure evidence for this release

Changed 12 · Unknown 21 · Steady 0

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

Library Version Health Measured there Projects
express-rate-limit 8.6.1 CHANGED Version changed, no linked failure 7 project-days
express-rate-limit 8.6.2 CHANGED Version changed, no linked failure 8 project-days
express-rate-limit 8.7.0 CHANGED Version changed, no linked failure 1 project-day
jose 6.2.10 CHANGED Version changed, no linked failure 4 project-days
jose 6.2.12 CHANGED Version changed, no linked failure 1 project-day
jose 6.2.4 CHANGED Version changed, no linked failure 7 project-days
jose 6.2.5 CHANGED Version changed, no linked failure 2 project-days
jose 6.2.8 CHANGED Version changed, no linked failure 1 project-day
jose 6.2.9 CHANGED Version changed, no linked failure 3 project-days
zod 3.25.76 CHANGED Version changed, no linked failure 1 project-day
zod 4.4.3 CHANGED Version changed, no linked failure 16 project-days
zod 4.6.5 CHANGED Version changed, no linked failure 1 project-day
@hono/node-server 2.0.12 UNKNOWN No linked outcome measured 8 project-days
@hono/node-server 2.1.1 UNKNOWN No linked outcome measured 10 project-days
ajv 8.20.0 UNKNOWN No linked outcome measured 15 project-days
ajv-formats 3.0.1 UNKNOWN No linked outcome measured 16 project-days
content-type 1.0.5 UNKNOWN No linked outcome measured 15 project-days
cors 2.8.6 UNKNOWN No linked outcome measured 15 project-days
cross-spawn 7.0.6 UNKNOWN No linked outcome measured 14 project-days
eventsource 3.0.7 UNKNOWN No linked outcome measured 16 project-days
eventsource-parser 3.1.0 UNKNOWN No linked outcome measured 7 project-days
eventsource-parser 3.1.1 UNKNOWN No linked outcome measured 9 project-days
express 5.2.1 UNKNOWN No linked outcome measured 15 project-days
hono 4.12.32 UNKNOWN No linked outcome measured 2 project-days
hono 4.13.1 UNKNOWN No linked outcome measured 6 project-days
hono 4.13.2 UNKNOWN No linked outcome measured 2 project-days
hono 4.13.3 UNKNOWN No linked outcome measured 2 project-days
hono 4.13.5 UNKNOWN No linked outcome measured 4 project-days
hono 4.13.8 UNKNOWN No linked outcome measured 1 project-day
json-schema-typed 8.0.2 UNKNOWN No linked outcome measured 16 project-days
pkce-challenge 5.0.1 UNKNOWN No linked outcome measured 14 project-days
raw-body 3.0.2 UNKNOWN No linked outcome measured 14 project-days
zod-to-json-schema 3.25.2 UNKNOWN No linked outcome measured 13 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.

Moved: 3 · unchanged at every release: 14

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.