CodeSampleX

Recordsnpmtar-stream2.2.0

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

Current conditions

tar-stream @2.2.0windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

8 of 10 passed

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
8 / 10
Contract verifications
nothing at this coordinate
Usage records
11
Independent reporting peers
1
Failures with a captured fingerprint
0 / 2
Last recorded
2026-08-21
Evidence you can open

Dependencies

LibraryVersionMeasured thereProjects
bl 4.1.0 contract passed 3 project-days
end-of-stream 1.4.5 contract passed 3 project-days
fs-constants 1.0.0 contract passed 3 project-days
inherits 2.0.4 contract passed 3 project-days
readable-stream 3.6.2 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.

Library3.2.13.2.02.2.0
bare-fs 4.8.1 4.8.0 —
streamx 2.28.1 2.28.0 —
b4a 1.8.1 1.8.1 —
bl — — 4.1.0
end-of-stream — — 1.4.5
fast-fifo 1.3.2 1.3.2 —
fs-constants — — 1.0.0
inherits — — 2.0.4
readable-stream — — 3.6.2

Moved: 2 · unchanged at every release: 7

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