Recordsnpmistanbul-lib-source-maps4.0.1
Change the conditions
Current conditions
istanbul-lib-source-maps @4.0.1windows 11 · x64 · node 24 · npm 11 · node
package-level total, not an API
1 of 1 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- 1 / 1
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-17
Dependency Health
Observed combinations and failure evidence for this release
First observed break
4.0.1
linux · node@22.23 · moduleSystem=cjs · executionContext=node
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:91ad26545eb1f3df29e3d9731c4244f3cf919942db2aa314b6b8d67ca84b47ef
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| debug | 4.4.3 | PASS All observations passed | contract passed | 6 project-days |
| istanbul-lib-coverage | 3.2.2 | PASS All observations passed | contract passed | 6 project-days |
| source-map | 0.6.1 | PASS All observations passed | contract passed | 6 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 | 5.0.6 | 4.0.1 |
|---|---|---|
| @jridgewell/trace-mapping | 0.3.31 | — |
| debug | 4.4.3 | 4.4.3 |
| istanbul-lib-coverage | 3.2.2 | 3.2.2 |
| source-map | — | 0.6.1 |
Moved: 0 · unchanged at every release: 4
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.