Recordsnpmupdate-browserslist-dbfailure issue
Failure signature
PROJECT_TEST ELIFECYCLE Evidence gap ×7
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-21 · Last seen: 2026-08-26
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 1.3.3 PASS 1 passing observations
- 1.3.2 PASS 16 passing observations
- 1.3.1 PASS 61 passing observations
- 1.3.0 FAIL
- 1.2.3 FAIL
Where it reproduced
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@22.16 ×3 2026-08-24 → 2026-08-24
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×2 2026-08-26 → 2026-08-26
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×1 2026-08-21 → 2026-08-21
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×1 2026-08-25 → 2026-08-25
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 failing release 1.3.0 → first passing release 1.3.1
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.
| Library | 1.3.3 | 1.3.2 | 1.3.1 | 1.3.0 | 1.2.3 |
|---|---|---|---|---|---|
| escalade | 3.2.0 | 3.2.0 | 3.2.0 | 3.2.0 | 3.2.0 |
| picocolors | 1.1.1 | 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.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- update-browserslist-db 1.3.0 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. HOWnode 22.23.2 MIT-0 · 2026-08-26
- update-browserslist-db 1.3.0 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. HOWnode 22.23.2 MIT-0 · 2026-08-24
- update-browserslist-db 1.2.3: name 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. HOWupdate-browserslist-db.namenode 22.23.2 MIT-0 · 2026-09-07
- update-browserslist-db 1.2.3: update-browserslist-db 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. HOWupdate-browserslist-db MIT-0 · 2026-09-07
- update-browserslist-db 1.2.3: length 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. HOWupdate-browserslist-db.length MIT-0 · 2026-09-06