CodeSampleX

Recordsnpmgot11.8.6

Change the conditions
Fixed
OSalpine musl Runtimenode 22
Filter Package version11.8.6 Symbolwhole package Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

got @11.8.6alpine musl · 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 (4)

Project observations
2 / 2
Contract verifications
1 / 1
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-05

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 11

First observed break

11.8.6

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

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

Library Version Health Measured there Projects
@sindresorhus/is 4.6.0 PASS All observations passed contract passed 42 project-days
@szmarczak/http-timer 4.0.6 PASS All observations passed contract passed 42 project-days
@types/cacheable-request 6.0.3 PASS All observations passed contract passed 41 project-days
@types/responselike 1.0.3 PASS All observations passed contract passed 41 project-days
cacheable-lookup 5.0.4 PASS All observations passed contract passed 40 project-days
cacheable-request 7.0.4 PASS All observations passed contract passed 41 project-days
decompress-response 6.0.0 PASS All observations passed contract passed 41 project-days
http2-wrapper 1.0.3 PASS All observations passed contract passed 37 project-days
lowercase-keys 2.0.0 PASS All observations passed contract passed 40 project-days
p-cancelable 2.1.1 PASS All observations passed contract passed 36 project-days
responselike 2.0.1 PASS All observations passed contract passed 38 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

Showing the 12 most-reported of 31 recorded failure clusters. The rest are single reports.