CodeSampleX

Recordsnpmtar-stream3.2.0

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

Current conditions

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

package-level total, not an API

15 of 20 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
15 / 20
Contract verifications
nothing at this coordinate
Usage records
3
Independent reporting peers
1
Failures with a captured fingerprint
0 / 5
Last recorded
2026-08-18
Evidence you can open

Dependencies

LibraryVersionMeasured thereProjects
b4a 1.8.1 contract passed 2 project-days
bare-fs 4.8.0 contract passed 2 project-days
fast-fifo 1.3.2 contract passed 2 project-days
streamx 2.28.0 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.

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