CodeSampleX

Recordsnpmcacheable-request7.0.4

Change the conditions
Fixed
Runtimenode 22 Package managernpm 11
Filter OSwindows 11 Package version7.0.4 Symbolwhole package Architecturex64 Execution contextnode Clear filters

Current conditions

cacheable-request @7.0.4windows 11 · x64 · node 22 · npm 11 · node

package-level total, not an API

11 of 12 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 (3)

Project observations
11 / 12
Contract verifications
nothing at this coordinate
Usage records
5
Independent reporting peers
1
Failures with a captured fingerprint
0 / 1
Last recorded
2026-08-24
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 7

First observed break

7.0.4

windows · node@24.13 · executionContext=node · moduleSystem=esm

32 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

View exact conditions View failure cluster
Library Version Health Measured there Projects
clone-response 1.0.3 PASS All observations passed contract passed 44 project-days
get-stream 5.2.0 PASS All observations passed contract passed 44 project-days
http-cache-semantics 4.2.0 PASS All observations passed contract passed 45 project-days
keyv 4.5.4 PASS All observations passed contract passed 41 project-days
lowercase-keys 2.0.0 PASS All observations passed contract passed 45 project-days
normalize-url 6.1.0 PASS All observations passed contract passed 43 project-days
responselike 2.0.1 PASS All observations passed contract passed 42 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.

Recent failure clusters