Recordsnpmtldts7.4.12tldts.getHostname
Change the conditions
Current conditions
tldts.getHostname @7.4.12ubuntu glibc · x64 · node 22 · npm 10 · node
4 of 4 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 (1)
- Project observations
- 4 / 4
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-09-13
Dependency Health
Observed combinations and failure evidence for this release
First observed break
7.4.12
windows · node@24.13 · moduleSystem=esm · executionContext=node
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.
| Library | 7.4.12 | 7.4.11 | 7.0.19 | 6.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.