Recordsnpmpuppeteer24.4.0
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
| alpine musl | debian glibc | 11 | |
|---|---|---|---|
| OutputPass | |||
| OutputPass.render | |||
| WebGLRenderer.outputColorSpace | |||
| WebGLRenderer.toneMapping | |||
| WebGLRenderer.toneMappingExposure | |||
| page.$$eval |
Showing the environments with the most evidence.
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Environment detail
Project-level observations and symbol/contract verifications are counted separately and never combined.
These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| chrome 134 · JS · npm · linux glibc · docker
Observations: PROJECT_LOAD 1✓ · PROJECT_TEST 1✓ — Usage: USED 1✓ — Verified: CONTRACT 5✓
|
LOW | 2 +1 | 5 | 100% | 1 · 1✓ | 2026-08-30 |
| node 22 · JS · npm · linux musl · docker
Observations: PROJECT_LOAD 1✓ · PROJECT_TEST 1✓ — Usage: USED 1✓ — Verified: CONTRACT 2✓
|
LOW | 2 +1 | 2 | 100% | 1 · 1✓ | 2026-08-30 |
| node 22 · JS · npm · linux musl · docker
Observations: PROJECT_LOAD 2✓ · PROJECT_TEST 2✓ — Usage: USED 2✓ — Verified: CONTRACT 2✓
|
MEDIUM | 4 +2 | 2 | 100% | 1 · 2✓ | 2026-08-30 |
| node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 12✓ 4✕ · PROJECT_TEST 1✓ — Usage: USED 2✓
|
LOW | 17 +2 | 0 | 76% | 1 | 2026-08-18 |
Recent failure clusters
-
observed PROJECT_PROCESS ENOENT Evidence gap ×4 24.4.0 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 puppeteer.launchEvidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-18 · Last seen: 2026-08-18Diagnostic re-verification candidate
Symbols
- page.$$eval 1 1 of 1 runs passed
- page.$eval 1 1 of 1 runs passed
- puppeteer.KnownDevices 1
- OutputPass shared ×2 1 of 1 runs passed
- puppeteer.PredefinedNetworkConditions 1
- defaultArgs 1
- page.evaluate 2 2 of 2 runs passed
- page.evaluateHandle 1 1 of 1 runs passed
- executablePath 1
- page.exposeFunction 3 3 of 3 runs passed
- puppeteer.launch 1 shared ×2
- WebGLRenderer.outputColorSpace shared ×2 1 of 1 runs passed
- OutputPass.render shared ×2 1 of 1 runs passed
- WebGLRenderer.toneMapping shared ×2 1 of 1 runs passed
- WebGLRenderer.toneMappingExposure shared ×2 2 of 2 runs passed
Published samples
- puppeteer 24.4.0 This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW MIT-0 · 2026-08-23