Compatibilitynpmtar-stream3.2.0
Change the conditions
Current conditions
tar-stream @3.2.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 |
|---|---|---|---|
| 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.
| Library | 3.2.1 | 3.2.0 | 2.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
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×6 3.2.0 executionContext=node · moduleSystem=esmEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-18 · Last seen: 2026-08-29Diagnostic re-verification candidate