Recordsnpmansi-escapes
Change the conditions
Current conditions
ansi-escapes @4.3.2ubuntu glibc · x64 · node 22 · npm 10 · node
0 of 10 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed (2)
- Project observations
- 50 / 50
- Contract verifications
- 0 / 10
- Usage records
- 3
- Independent reporting peers
- 3
- Last recorded
- 2026-09-17
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
0 of 10 passed
Verified — this network ran a contract at this coordinate.
-
ansi-escapes.default
2 of 2 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
4.3.2
windows · node@24.13 · executionContext=node · moduleSystem=esm
3 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| type-fest | 0.21.3 | PASS All observations passed | contract passed | 36 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 | 7.3.0 | 4.3.2 |
|---|---|---|
| environment | 1.1.0 | — |
| type-fest | — | 0.21.3 |
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.