Recordsnpmfinalhandler1.2.0
Change the conditions
Current conditions
finalhandler @1.2.0debian glibc · x64 · node 22 · npm · node
package-level total, not an API
1 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 came back clean (1)
- Project observations
- 4 / 4
- Contract verifications
- 1 / 1
- Usage records
- 2
- Independent reporting peers
- 1
- Last recorded
- 2026-10-13
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 3. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| debug | 2.6.9 | CHANGED Version changed, no linked failure | contract passed | 6 project-days |
| encodeurl | 1.0.2 | CHANGED Version changed, no linked failure | contract passed | 6 project-days |
| statuses | 2.0.1 | CHANGED Version changed, no linked failure | contract passed | 6 project-days |
| escape-html | 1.0.3 | PASS All observations passed | contract passed | 6 project-days |
| on-finished | 2.4.1 | PASS All observations passed | contract passed | 6 project-days |
| parseurl | 1.3.3 | PASS All observations passed | contract passed | 6 project-days |
| unpipe | 1.0.0 | PASS All observations passed | contract passed | 6 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.
| Library | 2.1.1 | 1.3.2 | 1.3.1 | 1.2.0 |
|---|---|---|---|---|
| debug | 4.4.3 | 2.6.9 | 2.6.9 | 2.6.9 |
| encodeurl | 2.0.0 | 2.0.0 | 2.0.0 | 1.0.2 |
| statuses | 2.0.2 | 2.0.2 | 2.0.1 | 2.0.1 |
| escape-html | 1.0.3 | 1.0.3 | 1.0.3 | 1.0.3 |
| on-finished | 2.4.1 | 2.4.1 | 2.4.1 | 2.4.1 |
| parseurl | 1.3.3 | 1.3.3 | 1.3.3 | 1.3.3 |
| unpipe | — | 1.0.0 | 1.0.0 | 1.0.0 |
Moved: 3 · unchanged at every release: 4
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.