CodeSampleX

Recordsnpmstring.prototype.trim1.2.11

Change the conditions
Fixed
Architecturex64 Package manageryarn 4
Filter OSubuntu glibc Runtimenode 22 Package version1.2.11 Symbolwhole package Execution contextnode libcglibc Clear filters

Current conditions

string.prototype.trim @1.2.11ubuntu glibc · x64 · node 22 · yarn 4 · node

package-level total, not an API

4 of 4 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
4 / 4
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-09-07
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 5

First observed break

1.2.11

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

1 FAIL · stage: UNKNOWN · fingerprint: sha256:7761a9558e8935e97e22ee51cbabcc9265c6251abc26761abb3da1a6ed94a926

View exact conditions View failure cluster
Library Version Health Measured there Projects
call-bind 1.0.9 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
es-abstract 1.24.2 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
es-object-atoms 1.1.2 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
call-bound 1.0.4 PASS All observations passed contract passed 2 project-days
define-data-property 1.1.4 PASS All observations passed contract passed 2 project-days
define-properties 1.2.1 PASS All observations passed contract passed 2 project-days
has-property-descriptors 1.0.2 PASS All observations passed contract passed 2 project-days
safe-regex-test 1.1.0 PASS All observations passed contract passed 2 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.

Library1.2.111.2.10
call-bind 1.0.9 1.0.8
es-abstract 1.24.2 1.24.0
es-object-atoms 1.1.2 1.1.1
call-bound 1.0.4 1.0.4
define-data-property 1.1.4 1.1.4
define-properties 1.2.1 1.2.1
has-property-descriptors 1.0.2 1.0.2
safe-regex-test 1.1.0 —

Moved: 3 · unchanged at every release: 5

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