CodeSampleX

Recordsnpmstrip-ansi7.2.0

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

Current conditions

strip-ansi @7.2.0debian 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.

there is a sample here, and nothing of ours has run it at this coordinate yet (1)

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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 0

First observed break

7.2.0

windows · executionContext=node

7 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
ansi-regex 6.2.2 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
ansi-regex 6.3.0 CANDIDATE Correlated change; unproven combination contract passed 20 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.2.07.1.26.0.1
ansi-regex 6.2.2 6.2.2 5.0.1

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