Recordsnpm@jridgewell/gen-mapping0.3.13
Change the conditions
Current conditions
@jridgewell/gen-mapping @0.3.13windows 11 · x64 · node (version not recorded) · pnpm 10 · node
package-level total, not an API
Recorded as present in projects. Nothing was run at this coordinate.
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (6)
- Project observations
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-01
Dependency Health
Observed combinations and failure evidence for this release
First observed break
0.3.13
windows · node@24.13 · moduleSystem=esm · executionContext=node
31 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @jridgewell/sourcemap-codec | 1.5.5 | PASS All observations passed | contract passed | 43 project-days |
| @jridgewell/sourcemap-codec | 1.6.0 | PASS All observations passed | contract passed | 174 project-days |
| @jridgewell/trace-mapping | 0.3.31 | PASS All observations passed | contract passed | 229 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.
Recent failure clusters
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×10 0.3.13 executionContext=nodeEvidence quality: legacy-evidence-incomplete · Environment variants: 3 · First recorded: 2026-08-16 · Last seen: 2026-08-23Diagnostic re-verification candidate
-
observed PROCESS_START process start failed Evidence gap ×3 0.3.13 executionContext=node sha256:c12549970456…· structured-termination · gap diagnostic-missingEvidence quality: partial · Environment variants: 2 · First recorded: 2026-09-05 · Last seen: 2026-09-16Diagnostic re-verification candidate