Recordsnpm@jest/test-result
Change the conditions
Current conditions
@jest/test-result @29.7.0alpine musl · x64 · node 22 · npm · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- 2 / 2
- Contract verifications
- 1 / 1
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-30
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
makeEmptyAggregatedTestResult
1 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
30.4.1
linux · node@22.23 · moduleSystem=cjs · executionContext=node
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:769e5b50934127934638762c5a14e135fd136d8f7f1621708b52dce382c93529
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 | 30.4.1 | 29.7.0 |
|---|---|---|
| @jest/console | 30.4.1 | 29.7.0 |
| @jest/types | 30.4.1 | 29.6.3 |
| @types/istanbul-lib-coverage | 2.0.6 | 2.0.6 |
| collect-v8-coverage | 1.0.3 | 1.0.3 |
Moved: 2 · 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.