CodeSampleX

Recordsnpmtldtsfailure issue

Failure signature

PROJECT_TEST exit 1 ERR_ASSERTION ×1

AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value: · assert.ok(second.delayMs>0&&second.delayMs<=3000) …

Evidence quality: complete · javascript/test-runner · test-runner-diagnostic · outer npm test · First recorded: 2026-09-13 · Last seen: 2026-09-13

sha256:53a7d182a4ae…

tldts.getDomain

Where it was measured

PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

Where it reproduced

Nearest known PASS/FAIL boundaries

The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.

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.19
tldts-core 7.4.12 7.4.11 7.0.19

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.

Evidence gaps

Published answers for the affected releases

Back to the package