Recordsnpmbare-fs4.8.0
Change the conditions
Current conditions
bare-fs @4.8.0alpine musl · x64 · node 22 · npm · node
package-level total, not an API
1 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- 2 / 2
- Contract verifications
- 1 / 1
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-30
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| 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.
| Library | 4.8.1 | 4.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
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×17 4.8.0 executionContext=nodeEvidence quality: legacy-evidence-incomplete · Environment variants: 3 · First recorded: 2026-08-18 · Last seen: 2026-08-30Diagnostic re-verification candidate