Recordsnpm@jridgewell/remapping2.3.5
Change the conditions
Current conditions
@jridgewell/remapping @2.3.5windows 11 · x64 · node 22 · npm 11 · node
package-level total, not an API
5 of 5 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 (1)
- Project observations
- 5 / 5
- Contract verifications
- nothing at this coordinate
- Usage records
- 5
- Independent reporting peers
- 1
- Last recorded
- 2026-08-24
Evidence you can open
Dependency Health
Observed combinations and failure evidence for this release
Observed problems 1 ·
Steady 2
First observed break
2.3.5
windows · node@24.13 · executionContext=node · moduleSystem=esm
32 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @jridgewell/gen-mapping | 0.3.13 | PASS All observations passed | contract passed | 112 project-days |
| @jridgewell/trace-mapping | 0.3.31 | PASS All observations passed | contract passed | 112 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 ×11 2.3.5 executionContext=nodeEvidence quality: legacy-evidence-incomplete · Environment variants: 3 · First recorded: 2026-08-16 · Last seen: 2026-08-23Diagnostic re-verification candidate