Recordsnpmarchiver5.3.2
Change the conditions
Current conditions
archiver @5.3.2debian glibc · x64 · node 22 · npm · node
package-level total, not an API
Recorded as present in projects. Nothing was run at this coordinate.
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 4
- Independent reporting peers
- 1
- Last recorded
- 2026-09-07
Evidence you can open
Dependency Health
Observed combinations and failure evidence for this release
Observed problems 1 ·
Steady 7
First observed break
5.3.2
windows · node@24.13 · moduleSystem=cjs · executionContext=node
3 FAIL
· stage: UNKNOWN
· fingerprint: sha256:c113861ea6575a55f8e3a44f91634852da7cbcd3825a7f52264c417b812b7599
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| archiver-utils | 2.1.0 | PASS All observations passed | contract passed | 16 project-days |
| async | 3.2.6 | PASS All observations passed | contract passed | 16 project-days |
| buffer-crc32 | 0.2.13 | PASS All observations passed | contract passed | 16 project-days |
| readable-stream | 3.6.2 | PASS All observations passed | contract passed | 16 project-days |
| readdir-glob | 1.1.3 | PASS All observations passed | contract passed | 16 project-days |
| tar-stream | 2.2.0 | PASS All observations passed | contract passed | 16 project-days |
| zip-stream | 4.1.1 | PASS All observations passed | contract passed | 16 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.