Recordsnpm@ampproject/remapping
Change the conditions
Current conditions
@ampproject/remapping @2.3.0alpine musl · x64 · node 22 · npm · node
2 of 2 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 (2)
- Project observations
- 4 / 4
- Contract verifications
- 2 / 2
- Usage records
- 2
- Independent reporting peers
- 1
- Last recorded
- 2026-09-05
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
2 of 2 passed
Verified — this network ran a contract at this coordinate.
-
remapping
1 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
2.3.0
linux · node@22.23 · moduleSystem=cjs · executionContext=node
3 FAIL
· stage: UNKNOWN
· fingerprint: sha256:91ad26545eb1f3df29e3d9731c4244f3cf919942db2aa314b6b8d67ca84b47ef
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @jridgewell/gen-mapping | 0.3.13 | PASS All observations passed | contract passed | 58 project-days |
| @jridgewell/trace-mapping | 0.3.31 | PASS All observations passed | contract passed | 58 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.