Recordsnpmqs6.16.0
Change the conditions
Current conditions
qs @6.16.0debian 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
- 2
- Independent reporting peers
- 1
- Last recorded
- 2026-09-14
Dependency Health
Observed combinations and failure evidence for this release
First observed break
6.16.0
windows · node@24.13 · moduleSystem=esm · executionContext=node
3 FAIL
· stage: PROCESS_START
· fingerprint: sha256:c12549970456efb5abdc90b679695c6689107d4f097d612245d6bfb25e01ec32
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| es-define-property | 1.0.1 | PASS All observations passed | contract passed | 10 project-days |
| side-channel | 1.1.1 | PASS All observations passed | contract passed | 10 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 | 6.16.0 | 6.15.3 | 6.13.0 | 6.11.0 |
|---|---|---|---|---|
| es-define-property | 1.0.1 | 1.0.1 | — | — |
| side-channel | 1.1.1 | 1.1.1 | 1.1.1 | 1.1.1 |
Moved: 0 · unchanged at every release: 2
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.