Recordsnpm@electron/osx-sign1.3.1flatAsync
Change the conditions
Current conditions
flatAsync @1.3.1ubuntu glibc · x64 · node 22 · npm 10 · node
3 of 3 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (2)
- Project observations
- 3 / 3
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-09-05
Dependency Health
Observed combinations and failure evidence for this release
First observed break
1.3.1
windows · executionContext=node
5 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| compare-version | 0.1.2 | PASS All observations passed | contract passed | 30 project-days |
| debug | 4.4.3 | PASS All observations passed | contract passed | 30 project-days |
| fs-extra | 10.1.0 | PASS All observations passed | contract passed | 29 project-days |
| isbinaryfile | 4.0.10 | PASS All observations passed | contract passed | 29 project-days |
| minimist | 1.2.8 | PASS All observations passed | contract passed | 30 project-days |
| plist | 3.1.1 | PASS All observations passed | contract passed | 29 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 | 1.3.3 | 1.3.1 |
|---|---|---|
| compare-version | 0.1.2 | 0.1.2 |
| debug | 4.4.3 | 4.4.3 |
| fs-extra | 10.1.0 | 10.1.0 |
| isbinaryfile | 4.0.10 | 4.0.10 |
| minimist | 1.2.8 | 1.2.8 |
| plist | 3.1.1 | 3.1.1 |
Moved: 0 · unchanged at every release: 6
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 1.3.1 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 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