CodeSampleX

Recordsnpmtldts7.4.12getDomain

Change the conditions
Fixed
Runtimenode 24 SymbolgetDomain
Filter OSwindows 11 Package version7.4.12 Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

getDomain @7.4.12windows 11 · x64 · node 24 · npm 11 · node

0 of 22 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
64 / 75
Contract verifications
0 / 22
Independent reporting peers
1
Last recorded
2026-09-14

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

7.4.12

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

2 FAIL · stage: UNKNOWN · fingerprint: sha256:340c5f78ca350e182b7069dc6d9481ef0fa77573d019e926c7b05c0cc108f20c

Library Version Health Measured there Projects
tldts-core 7.4.12 CANDIDATE Correlated change; unproven combination contract passed 4 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.

Library7.4.127.4.117.0.196.1.86
tldts-core 7.4.12 7.4.11 7.0.19 6.1.86

Moved: 1 · unchanged at every release: 0

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 32 recorded failure clusters. The rest are single reports.