Recordsnpmexpect
Change the conditions
Current conditions
expect @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.
-
expect.extend
1 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
First observed break
29.7.0 @jest/expect-utils@29.7.0
linux · node@22.23 · moduleSystem=cjs · executionContext=node
2 FAIL
· stage: UNKNOWN
· fingerprint: sha256:91ad26545eb1f3df29e3d9731c4244f3cf919942db2aa314b6b8d67ca84b47ef
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @jest/expect-utils | 29.7.0 | FAIL Linked failure observed; version changed across releases | contract passed | 11 project-days |
| jest-get-type | 29.6.3 | FAIL Linked failure observed on this release | contract passed | 10 project-days |
| jest-matcher-utils | 29.7.0 | FAIL Linked failure observed; version changed across releases | contract passed | 8 project-days |
| jest-message-util | 29.7.0 | FAIL Linked failure observed; version changed across releases | contract passed | 10 project-days |
| jest-util | 29.7.0 | FAIL Linked failure observed; version changed across releases | 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 | 30.4.1 | 29.7.0 |
|---|---|---|
| @jest/expect-utils | 30.4.1 | 29.7.0 |
| jest-matcher-utils | 30.4.1 | 29.7.0 |
| jest-message-util | 30.4.1 | 29.7.0 |
| jest-util | 30.4.1 | 29.7.0 |
| @jest/get-type | 30.1.0 | — |
| jest-get-type | — | 29.6.3 |
| jest-mock | 30.4.1 | — |
Moved: 4 · unchanged at every release: 3
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.