Recordsnpm@puppeteer/browsers2.8.0detectBrowserPlatform
Change the conditions
Current conditions
detectBrowserPlatform @2.8.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
- nothing at this coordinate
- Contract verifications
- 1 / 1
- Last recorded
- 2026-08-23
Dependency Health
Observed combinations and failure evidence for this release
First observed break
2.8.0
moduleSystem=esm · executionContext=node
6 FAIL · stage: PROJECT_PROCESS
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| yargs | 17.7.3 | CANDIDATE Correlated change; unproven combination | contract passed | 10 project-days |
| debug | 4.4.3 | PASS All observations passed | contract passed | 10 project-days |
| extract-zip | 2.0.1 | PASS All observations passed | contract passed | 10 project-days |
| progress | 2.0.3 | PASS All observations passed | contract passed | 10 project-days |
| proxy-agent | 6.5.0 | PASS All observations passed | contract passed | 10 project-days |
| semver | 7.8.5 | PASS All observations passed | contract passed | 10 project-days |
| tar-fs | 3.1.3 | PASS All observations passed | 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 | 3.2.0 | 2.13.2 | 2.8.0 | 2.7.1 |
|---|---|---|---|---|
| yargs | 18.1.0 | 17.7.3 | 17.7.3 | 17.7.3 |
| debug | — | 4.4.3 | 4.4.3 | 4.4.3 |
| extract-zip | — | 2.0.1 | 2.0.1 | 2.0.1 |
| modern-tar | 0.8.4 | — | — | — |
| progress | — | 2.0.3 | 2.0.3 | 2.0.3 |
| proxy-agent | — | 6.5.0 | 6.5.0 | 6.5.0 |
| semver | — | 7.8.5 | 7.8.5 | 7.8.5 |
| tar-fs | — | 3.1.3 | 3.1.3 | 3.1.3 |
Moved: 1 · unchanged at every release: 7
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 PROJECT_PROCESS ERR_ASSERTION Evidence gap ×6 2.8.0 executionContext=node · moduleSystem=esmEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-18 · Last seen: 2026-08-27Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 2.8.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:91ad26545eb1…node:internal/modules/cjs/loader:<n> · throw err; · ^ · Error: Cannot find module <str>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate