Recordsnpm@npmcli/git7.0.1
Change the conditions
Current conditions
@npmcli/git @7.0.1debian 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 |
|---|---|---|---|---|
| @npmcli/promise-spawn | 9.0.1 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| ini | 6.0.0 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| lru-cache | 11.2.4 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| npm-pick-manifest | 11.0.3 | 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 |
| which | 6.0.0 | CHANGED Version changed, no linked failure | builds observed | 1 project-day |
| promise-retry | 2.0.1 | 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 | 7.0.2 | 7.0.1 | 6.0.3 |
|---|---|---|---|
| @npmcli/promise-spawn | 9.0.1 | 9.0.1 | 8.0.3 |
| ini | 6.0.0 | 6.0.0 | 5.0.0 |
| lru-cache | 11.5.1 | 11.2.4 | 10.4.3 |
| npm-pick-manifest | 11.0.3 | 11.0.3 | 10.0.0 |
| proc-log | 6.1.0 | 6.1.0 | 5.0.0 |
| semver | 7.8.5 | 7.7.3 | 7.7.4 |
| which | 6.0.1 | 6.0.0 | 5.0.0 |
| @gar/promise-retry | 1.0.3 | — | — |
| promise-retry | — | 2.0.1 | 2.0.1 |
Moved: 7 · unchanged at every release: 2
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.