CodeSampleX

Recordsnpmserve-static2.2.1

Change the conditions
Fixed
Package managerpnpm 10
Filter OSwindows 11 Runtimenode 24 Package version2.2.1 Symbolwhole package Architecturex64 Execution contextnode Clear filters

Current conditions

serve-static @2.2.1windows 11 · x64 · node 24 · pnpm 10 · node

package-level total, not an API

0 of 2 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
25 / 27
Contract verifications
0 / 2
Usage records
25
Independent reporting peers
1
Failures with a captured fingerprint
1 / 2
Last recorded
2026-08-29
Evidence you can open

Dependencies

LibraryVersionMeasured thereProjects
encodeurl 2.0.0 contract passed 8 project-days
escape-html 1.0.3 contract passed 8 project-days
parseurl 1.3.3 contract passed 9 project-days
send 1.2.1 contract passed 8 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.2.11.15.0
encodeurl 2.0.0 1.0.2
send 1.2.1 0.18.0
escape-html 1.0.3 1.0.3
parseurl 1.3.3 1.3.3

Moved: 2 · 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