Recordsnpmupdate-browserslist-db1.2.3update-browserslist-db.name
Change the conditions
Current conditions
update-browserslist-db.name @1.2.3ubuntu glibc · x64 · node 22 · npm 10 · node
3 of 3 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 (1)
- Project observations
- 3 / 3
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-09-07
Dependency Health
Observed combinations and failure evidence for this release
First observed break
1.2.3
windows · executionContext=node
7 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| escalade | 3.2.0 | PASS All observations passed | contract passed | 10 project-days |
| picocolors | 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 | 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.