Recordsnpmserve-static1.15.0
Change the conditions
Current conditions
serve-static @1.15.0ubuntu glibc · x64 · node 22 · npm 10 · node
package-level total, not an API
1 of 1 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (1)
- Project observations
- 1 / 1
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-30
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| encodeurl | 1.0.2 | contract passed | 1 project-day |
| escape-html | 1.0.3 | contract passed | 1 project-day |
| parseurl | 1.3.3 | contract passed | 1 project-day |
| send | 0.18.0 | contract passed | 1 project-day |
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.
| Library | 2.2.1 | 1.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.