Records/npm/qs/failure issue

Where it was measured

PASS means the release recorded a passing observation at PROJECT_PROCESS and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• 6.16.0 PASS 22 passing observations
• 6.15.3 FAIL
• 6.14.0 not measured
• 6.13.0 PASS 8 passing observations
• 6.11.0 PASS 3 passing observations

Where it reproduced

• executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×12 2026-08-13 → 2026-08-14
• executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×1 2026-08-21 → 2026-08-21

Nearest known PASS/FAIL boundaries

The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.

• Last passing release 6.13.0 → first failing release 6.15.3

  Releases between them never measured at this stage: 1

  What differs across the boundary

  • es-define-property — → 1.0.1 hypothesis

  A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.

• Last failing release 6.15.3 → first passing release 6.16.0

  Both trees resolved every dependency to the same version. Nothing here moved.

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.

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.

Evidence gaps

• The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
• Releases in this window never measured at PROJECT_PROCESS: 1
• No failure domain was inferred for this failure.

Published answers for the affected releases

• qs 6.15.3 Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW MIT-0 · 2026-08-20
• qs 6.15.3: Preserve conflicting scalar and object query values in an array via strictMerge introduced in qs 6.15.0 instead of mutating scalars into boolean object keys Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWqs.parsenode MIT-0 · 2026-08-16
• qs 6.15.3: Parse and build nested query strings that URLSearchParams cannot express Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWqs.parseqs.stringifynode 22 MIT-0 · 2026-08-13