Recordsnpm@npmcli/map-workspaces4.0.2mapWorkspaces
Change the conditions
Current conditions
mapWorkspaces @4.0.2debian glibc · x64 · node 22 · npm · node
1 of 1 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 (1)
- Project observations
- 2 / 2
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-10-19
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 4. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @npmcli/name-from-folder | 3.0.0 | CHANGED Version changed, no linked failure | contract passed | 7 project-days |
| @npmcli/package-json | 6.2.0 | CHANGED Version changed, no linked failure | contract passed | 7 project-days |
| glob | 10.5.0 | CHANGED Version changed, no linked failure | contract passed | 6 project-days |
| minimatch | 9.0.9 | CHANGED Version changed, no linked failure | contract passed | 7 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.3 | 4.0.2 |
|---|---|---|
| @npmcli/name-from-folder | 4.0.0 | 3.0.0 |
| @npmcli/package-json | 7.0.4 | 6.2.0 |
| glob | 13.0.0 | 10.5.0 |
| minimatch | 10.1.1 | 9.0.9 |
Moved: 4 · unchanged at every release: 0
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.