CodeSampleX

Recordsnpmpacote21.0.4

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

Current conditions

pacote @21.0.4debian 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-14
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Changed 15 · Steady 2

Dependency changes observed: 15. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
@npmcli/git 7.0.1 CHANGED Version changed, no linked failure builds observed 1 project-day
@npmcli/installed-package-contents 4.0.0 CHANGED Version changed, no linked failure contract passed 1 project-day
@npmcli/package-json 7.0.4 CHANGED Version changed, no linked failure builds observed 1 project-day
@npmcli/promise-spawn 9.0.1 CHANGED Version changed, no linked failure contract passed 1 project-day
@npmcli/run-script 10.0.3 CHANGED Version changed, no linked failure builds observed 1 project-day
cacache 20.0.3 CHANGED Version changed, no linked failure builds observed 1 project-day
minipass 7.1.2 CHANGED Version changed, no linked failure contract passed 1 project-day
npm-package-arg 13.0.2 CHANGED Version changed, no linked failure contract passed 1 project-day
npm-packlist 10.0.3 CHANGED Version changed, no linked failure builds observed 1 project-day
npm-pick-manifest 11.0.3 CHANGED Version changed, no linked failure contract passed 1 project-day
npm-registry-fetch 19.1.1 CHANGED Version changed, no linked failure contract passed 1 project-day
proc-log 6.1.0 CHANGED Version changed, no linked failure contract passed 1 project-day
sigstore 4.1.0 CHANGED Version changed, no linked failure builds observed 1 project-day
ssri 13.0.0 CHANGED Version changed, no linked failure builds observed 1 project-day
tar 7.5.4 CHANGED Version changed, no linked failure builds observed 1 project-day
fs-minipass 3.0.3 PASS All observations passed contract passed 1 project-day
promise-retry 2.0.1 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.

Library21.5.121.0.420.0.119.0.2
@npmcli/git 7.0.2 7.0.1 6.0.3 6.0.3
@npmcli/installed-package-contents 4.0.0 4.0.0 3.0.0 3.0.0
@npmcli/package-json 7.0.5 7.0.4 6.2.0 6.2.0
@npmcli/promise-spawn 9.0.1 9.0.1 8.0.3 8.0.3
@npmcli/run-script 10.0.4 10.0.3 9.1.0 9.1.0
cacache 20.0.4 20.0.3 19.0.1 19.0.1
minipass 7.1.3 7.1.2 7.1.3 7.1.3
npm-package-arg 13.0.2 13.0.2 12.0.2 12.0.2
npm-packlist 10.0.4 10.0.3 9.0.0 9.0.0
npm-pick-manifest 11.0.3 11.0.3 10.0.0 10.0.0
npm-registry-fetch 19.1.1 19.1.1 18.0.2 18.0.2
proc-log 6.1.0 6.1.0 5.0.0 5.0.0
sigstore 4.1.1 4.1.0 3.1.0 3.1.0
ssri 13.0.1 13.0.0 12.0.0 12.0.0
tar 7.5.22 7.5.4 7.5.22 7.5.22
@gar/promise-retry 1.0.3 — — —
fs-minipass 3.0.3 3.0.3 3.0.3 3.0.3
promise-retry — 2.0.1 2.0.1 2.0.1

Moved: 15 · 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.