CodeSampleX

Recordsnpmtldts7.4.11

Change the conditions
Fixed
OSdebian glibc Package version7.4.11 Package managernpm
Filter Runtimenode 22 Symbolwhole package Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

tldts @7.4.11debian glibc · x64 · node 22 · npm · node

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-06
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

7.4.11

linux · node@22.23 · moduleSystem=esm · executionContext=node

2 FAIL · stage: UNKNOWN · fingerprint: sha256:529aac3b1da710068c9dcfe93d0864269e86bebfbe110ca5beeed398860460e7

View exact conditions View failure cluster
Library Version Health Measured there Projects
tldts-core 7.4.11 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