CodeSampleX

Recordsnpmcall-bind1.0.9

Change the conditions
Fixed
OSwindows 11 Package version1.0.9
Filter Runtimenode 24 Symbolwhole package Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

call-bind @1.0.9windows 11 · x64 · node 24 · npm 11 · 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-08-13

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 4

First observed break

1.0.9

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

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

Library Version Health Measured there Projects
call-bind-apply-helpers 1.0.2 PASS All observations passed contract passed 3 project-days
es-define-property 1.0.1 PASS All observations passed contract passed 3 project-days
get-intrinsic 1.3.0 PASS All observations passed contract passed 3 project-days
set-function-length 1.2.2 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.

Moved: 0 · unchanged at every release: 4

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.