CodeSampleX

Recordsnpmiconv-lite0.7.3

Change the conditions
Fixed
Package version0.7.3 Package managernpm 11 Execution contextnode
Filter OSwindows 11 Runtimenode 24 Symbolwhole package Architecturex64 Clear filters

Current conditions

iconv-lite @0.7.3windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

0 of 70 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
140 / 173
Contract verifications
0 / 70
Usage records
314
Independent reporting peers
2
Failures with a captured fingerprint
19 / 33
Last recorded
2026-09-26
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 1

First observed break

0.7.3

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

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
safer-buffer 2.1.2 PASS All observations passed contract passed 21 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.

Library0.7.30.7.20.6.30.4.24
safer-buffer 2.1.2 2.1.2 2.1.2 2.1.2

Moved: 0 · unchanged at every release: 1

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

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