CodeSampleX

Recordsnpm@modelcontextprotocol/sdk

Compatibility cube

Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.

Fixed
Package version1.31.0
Filter Architecturex64 Execution contextnode libcglibc Clear filters
Symbol × Runtime
4○ 12026-11-18

Showing the environments with the most evidence. The cube reads the newest 6 versions and the first 10 symbols of each, so an empty cell here can mean "outside that window" rather than "never measured".

How to read the grid

Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.

  • no sample at this coordinate yet
  • there is a sample here, and nothing of ours has run it at this coordinate yet
  • there is a sample here, and our run of it at this coordinate came back clean
  • there is a sample here, and our run of it at this coordinate failed
  • there is a sample here, and this coordinate records both a passing and a failing run of it
  • nothing recorded — unknown, never "works" and never "broken"
  • there is a level below this cell — click to open it

A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.

Cells are aggregates of everything still varying in this slice (the n/m count says how much). Click one to pin its coordinates and see the next level.

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 7 · Unknown 18 · Steady 0

First observed break

1.31.0

executionContext=node

16 FAIL · stage: PROJECT_PROCESS

Library Version Health Measured there Projects
express-rate-limit 8.6.1 CANDIDATE Correlated change; unproven combination 2 project-days
express-rate-limit 8.7.1 CANDIDATE Correlated change; unproven combination 39 project-days
jose 6.2.13 CANDIDATE Correlated change; unproven combination 39 project-days
jose 6.2.4 CANDIDATE Correlated change; unproven combination 2 project-days
zod 3.25.76 CANDIDATE Correlated change; unproven combination 2 project-days
zod 4.4.3 CANDIDATE Correlated change; unproven combination 2 project-days
zod 4.6.7 CANDIDATE Correlated change; unproven combination 37 project-days
@hono/node-server 2.0.12 UNKNOWN No linked outcome measured 2 project-days
@hono/node-server 2.1.5 UNKNOWN No linked outcome measured 39 project-days
ajv 8.20.0 UNKNOWN No linked outcome measured 41 project-days
ajv-formats 3.0.1 UNKNOWN No linked outcome measured 41 project-days
content-type 1.0.5 UNKNOWN No linked outcome measured 41 project-days
cors 2.8.6 UNKNOWN No linked outcome measured 41 project-days
cross-spawn 7.0.6 UNKNOWN No linked outcome measured 41 project-days
eventsource 3.0.7 UNKNOWN No linked outcome measured 41 project-days
eventsource-parser 3.1.0 UNKNOWN No linked outcome measured 2 project-days
eventsource-parser 3.1.1 UNKNOWN No linked outcome measured 39 project-days
express 5.2.1 UNKNOWN No linked outcome measured 2 project-days
express 5.3.0 UNKNOWN No linked outcome measured 39 project-days
hono 4.13.13 UNKNOWN No linked outcome measured 39 project-days
hono 4.13.8 UNKNOWN No linked outcome measured 2 project-days
json-schema-typed 8.0.2 UNKNOWN No linked outcome measured 41 project-days
pkce-challenge 5.0.1 UNKNOWN No linked outcome measured 41 project-days
raw-body 3.0.2 UNKNOWN No linked outcome measured 41 project-days
zod-to-json-schema 3.25.2 UNKNOWN No linked outcome measured 41 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.