Recordsnpmonetime
Change the conditions
Current conditions
onetime @5.1.2ubuntu glibc · x64 · node 22 · npm 10 · node
0 of 52 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed (1)
- Project observations
- 49 / 49
- Contract verifications
- 0 / 52
- Usage records
- 88
- Independent reporting peers
- 3
- Last recorded
- 2026-09-07
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
0 of 52 passed
Verified — this network ran a contract at this coordinate.
-
onetime.callCount
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
5.1.2
linux · node@22.23 · executionContext=node · moduleSystem=cjs
15 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9be950af9140edade9f2c5aa029896fb7dd194960195369ee277ef42a11d6868
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| mimic-fn | 2.1.0 | CANDIDATE Correlated change; unproven combination | contract passed | 24 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.
Moved: 1 · unchanged at every release: 0
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.