Recordsnpmiconv-lite0.6.3
Change the conditions
Current conditions
iconv-lite @0.6.3windows 11 · x64 · node 24 · npm 11 · node
package-level total, not an API
0 of 20 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed (3)
- Project observations
- 45 / 96
- Contract verifications
- 0 / 20
- Usage records
- 91
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 49 / 51
- Last recorded
- 2026-09-16
Evidence you can open
Dependency Health
Observed combinations and failure evidence for this release
Observed problems 1 ·
Steady 1
First observed break
0.6.3
executionContext=node
14 FAIL · stage: PROJECT_PROCESS
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| safer-buffer | 2.1.2 | PASS All observations passed | contract passed | 29 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 | 0.7.3 | 0.7.2 | 0.6.3 | 0.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
-
observed PROJECT_PROCESS ERR_MODULE_NOT_FOUND Evidence gap ×14 0.6.3 → 0.7.3 executionContext=nodeEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-13 · Last seen: 2026-08-21Diagnostic re-verification candidate
-
observed PROCESS_START process start failed Evidence gap ×7 0.6.3 → 0.7.3 executionContext=node sha256:c12549970456…· structured-termination · gap diagnostic-missingEvidence quality: partial · Environment variants: 3 · First recorded: 2026-08-31 · Last seen: 2026-09-16Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×6 0.6.3 → 0.7.3 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:c113861ea657…<str> is not recognized as an internal or external command, · operable program or batch file. · > wslpad@1.1.0 test · > vitest runnpm · unclassified-diagnostic · outer npm test · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-16 · Last seen: 2026-09-16Diagnostic re-verification candidate
-
observed PROJECT_COMPILE exit 2 TS2307 ×4 0.6.3 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:0470f88d95bb…lib/hooks/queries/index.ts(<n>,<n>): error TS2307: Cannot find module <str> or its corresponding type declarations. …typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS7006 ×4 0.6.3 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:21025cd78572…app/api/politicians/[id]/real-estates/route.ts(<n>,<n>): error TS7006: Parameter <str> implicitly has an <str> type. …typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2561 ×4 0.6.3 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:5f96e966539e…app/api/politicians/[id]/real-estates/route.ts(<n>,<n>): error TS2561: Object literal may only specify known properties, but <str> does not exist in type …typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2345 ×4 0.6.3 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:7e077f646acc…lib/api/real-estate-statistics.ts(<n>,<n>): error TS2345: Argument of type <str> is not assignable to parameter of type <str>.typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2551 ×4 0.6.3 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:8a1ebc675f2b…app/api/politicians/[id]/real-estates/route.ts(<n>,<n>): error TS2551: Property <str> does not exist on type <str>. Did you mean <str>? …typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2339 ×4 0.6.3 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:e51205820175…lib/api/real-estate-map-addresses.ts(<n>,<n>): error TS2339: Property <str> does not exist on type <str>.typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2305 ×4 0.6.3 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:e7aa54217e13…app/api/politicians/[id]/real-estates/route.ts(<n>,<n>): error TS2305: Module <str> has no exported member <str>. …typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_TEST Evidence gap ×3 0.6.3 → 0.7.3 executionContext=node · os=windows · runtime=node@24.13Evidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-21 · Last seen: 2026-08-25Diagnostic re-verification candidate
-
observed PROJECT_TYPECHECK Evidence gap ×2 0.6.3 → 0.7.3 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-21 · Last seen: 2026-08-21Diagnostic re-verification candidate
Showing the 12 most-reported of 42 recorded failure clusters. The rest are single reports.