Recordsnpmnormalize-package-data7.0.1
Change the conditions
Current conditions
normalize-package-data @7.0.1ubuntu glibc · x64 · node 22 · yarn 4 · node
package-level total, not an API
3 of 3 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- 3 / 3
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-09-07
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 2. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| hosted-git-info | 8.1.0 | CHANGED Version changed, no linked failure | builds observed | 2 project-days |
| semver | 7.7.4 | CHANGED Version changed, no linked failure | contract passed | 2 project-days |
| validate-npm-package-license | 3.0.4 | PASS All observations passed | contract passed | 2 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 | 8.0.0 | 7.0.1 | 6.0.2 |
|---|---|---|---|
| hosted-git-info | 9.0.3 | 8.1.0 | 7.0.2 |
| semver | 7.8.5 | 7.7.4 | 7.8.5 |
| validate-npm-package-license | 3.0.4 | 3.0.4 | 3.0.4 |
Moved: 2 · unchanged at every release: 1
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.