CodeSampleX

Recordsnpm@asamuzakjp/dom-selector7.1.1

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

Current conditions

@asamuzakjp/dom-selector @7.1.1debian 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 3 · Steady 3

First observed break

7.1.1

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

1 FAIL · stage: UNKNOWN · fingerprint: sha256:1be69c1584909f830d69e106adb00b0cc501e3da58d75fe81bcab93528ff0b3d

View exact conditions View failure cluster
Library Version Health Measured there Projects
bidi-js 1.0.3 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
bidi-js 1.1.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
css-tree 3.2.1 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
@asamuzakjp/generational-cache 1.0.1 PASS All observations passed contract passed 3 project-days
@asamuzakjp/nwsapi 2.3.9 PASS All observations passed contract passed 3 project-days
is-potential-custom-element-name 1.0.1 PASS All observations passed contract passed 3 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.

Library8.3.27.1.16.7.6
bidi-js 1.1.0 1.0.3 1.0.3
css-tree 3.2.1 3.2.1 3.1.0
lru-cache 11.5.2 — 11.2.4
@asamuzakjp/generational-cache — 1.0.1 —
@asamuzakjp/nwsapi — 2.3.9 2.3.9
is-potential-custom-element-name 1.0.1 1.0.1 1.0.1

Moved: 3 · unchanged at every release: 3

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