Recordsnpmdmg-builder25.1.8dmg-builder.serializeString
Change the conditions
Current conditions
dmg-builder.serializeString @25.1.8ubuntu glibc · x64 · node 22 · npm 10 · node
0 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 failed
- Project observations
- nothing at this coordinate
- Contract verifications
- 0 / 1
- Last recorded
- 2026-08-29
Dependency Health
Observed combinations and failure evidence for this release
First observed break
25.1.8
windows · executionContext=node
5 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| app-builder-lib | 25.1.8 | CANDIDATE Correlated change; unproven combination | contract passed | 16 project-days |
| builder-util | 25.1.7 | CANDIDATE Correlated change; unproven combination | contract passed | 16 project-days |
| js-yaml | 4.3.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| js-yaml | 4.3.2 | CANDIDATE Correlated change; unproven combination | contract passed | 13 project-days |
| builder-util-runtime | 9.2.10 | PASS All observations passed | contract passed | 16 project-days |
| fs-extra | 10.1.0 | PASS All observations passed | contract passed | 16 project-days |
| iconv-lite | 0.6.3 | PASS All observations passed | contract passed | 15 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 | 26.15.3 | 25.1.8 |
|---|---|---|
| app-builder-lib | 26.15.3 | 25.1.8 |
| builder-util | 26.15.3 | 25.1.7 |
| js-yaml | 4.3.2 | 4.3.0 |
| builder-util-runtime | — | 9.2.10 |
| fs-extra | 10.1.0 | 10.1.0 |
| iconv-lite | — | 0.6.3 |
Moved: 3 · 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.
Recent failure clusters
-
observed UNKNOWN exit 1 Evidence gap ×1 25.1.8 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 dmg-builder.serializeString sha256:795cbb5ee086…Error: Cannot find module <str> · Require stack: · - <path> · - <path>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29Diagnostic re-verification candidate