Recordsnpmupdate-browserslist-db1.3.1
Change the conditions
Current conditions
update-browserslist-db @1.3.1windows 11 · x64 · node 22 · npm 11 · node
package-level total, not an API
13 of 14 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (2)
- Project observations
- 13 / 14
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 0 / 1
- Last recorded
- 2026-08-21
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| escalade | 3.2.0 | contract passed | 28 project-days |
| picocolors | 1.1.1 | contract passed | 17 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 | 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 |
| picocolors | 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.
Recent failure clusters
-
observed PROJECT_TYPECHECK Evidence gap ×2 1.2.3 → 1.3.1 executionContext=node · moduleSystem=cjs · os=windowsEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-21 · Last seen: 2026-08-21Diagnostic re-verification candidate