CodeSampleX

Recordsnpmbare-fs4.8.0

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

Current conditions

bare-fs @4.8.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
bare-events 2.9.1 contract passed 5 project-days
bare-path 3.1.1 contract passed 6 project-days
bare-stream 2.13.3 contract passed 4 project-days
bare-url 2.5.2 contract passed 6 project-days
fast-fifo 1.3.2 contract passed 5 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.

Library4.8.14.8.0
bare-stream 2.13.4 2.13.3
bare-events 2.9.1 2.9.1
bare-path 3.1.1 3.1.1
bare-url 2.5.2 2.5.2
fast-fifo 1.3.2 1.3.2

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

Recent failure clusters