CodeSampleX

Recordsnpmfunction.prototype.name1.2.0

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

Current conditions

function.prototype.name @1.2.0ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 2 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed

Project observations
3 / 3
Contract verifications
0 / 2
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 7

First observed break

1.2.0

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

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
hasown 2.0.4 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
call-bound 1.0.4 PASS All observations passed contract passed 2 project-days
es-define-property 1.0.1 PASS All observations passed contract passed 2 project-days
es-errors 1.3.0 PASS All observations passed contract passed 2 project-days
functions-have-names 1.2.3 PASS All observations passed contract passed 1 project-day
has-property-descriptors 1.0.2 PASS All observations passed contract passed 2 project-days
is-callable 1.2.7 PASS All observations passed contract passed 2 project-days
is-document.all 1.0.0 PASS All observations passed contract passed 1 project-day

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.01.1.8
call-bind 1.0.9 1.0.8
hasown 2.0.4 2.0.2
call-bound 1.0.4 1.0.4
define-properties — 1.2.1
es-define-property 1.0.1 —
es-errors 1.3.0 —
functions-have-names 1.2.3 1.2.3
has-property-descriptors 1.0.2 —
is-callable 1.2.7 1.2.7
is-document.all 1.0.0 —

Moved: 2 · unchanged at every release: 8

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