Recordsnpmnode-gyp12.1.0
Change the conditions
Current conditions
node-gyp @12.1.0debian glibc · x64 · node 22 · npm · 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.
no sample at this coordinate yet
- Project observations
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-14
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 7. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| make-fetch-happen | 15.0.3 | CHANGED Version changed, no linked failure | builds observed | 1 project-day |
| nopt | 9.0.0 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| proc-log | 6.1.0 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| semver | 7.7.3 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| tar | 7.5.4 | CHANGED Version changed, no linked failure | builds observed | 1 project-day |
| tinyglobby | 0.2.15 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| which | 6.0.0 | CHANGED Version changed, no linked failure | builds observed | 1 project-day |
| env-paths | 2.2.1 | PASS All observations passed | contract passed | 1 project-day |
| exponential-backoff | 3.1.3 | PASS All observations passed | contract passed | 1 project-day |
| graceful-fs | 4.2.11 | PASS All observations passed | contract passed | 1 project-day |
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 | 12.4.0 | 12.1.0 | 11.5.0 | 9.4.1 |
|---|---|---|---|---|
| make-fetch-happen | — | 15.0.3 | 14.0.3 | 10.2.1 |
| nopt | 9.0.0 | 9.0.0 | 8.1.0 | 6.0.0 |
| proc-log | 6.1.0 | 6.1.0 | 5.0.0 | — |
| semver | 7.7.4 | 7.7.3 | 7.7.4 | 7.8.5 |
| tar | 7.5.22 | 7.5.4 | 7.5.22 | 6.2.1 |
| tinyglobby | 0.2.17 | 0.2.15 | 0.2.15 | — |
| which | 6.0.1 | 6.0.0 | 5.0.0 | 2.0.2 |
| env-paths | 2.2.1 | 2.2.1 | 2.2.1 | 2.2.1 |
| exponential-backoff | 3.1.3 | 3.1.3 | 3.1.3 | 3.1.3 |
| glob | — | — | — | 7.2.3 |
| graceful-fs | 4.2.11 | 4.2.11 | 4.2.11 | 4.2.11 |
| npmlog | — | — | — | 6.0.2 |
| rimraf | — | — | — | 3.0.2 |
| undici | 6.28.1 | — | — | — |
Moved: 7 · unchanged at every release: 7
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.