amd-name-resolver
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed-stale | AI (provenance): 2019 handoff, unremoved 2750d; benign transfer stable for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same legitimate handoff to turbo87 with strong track record. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.3.1 | 2 / 4 | |
| 1.3.0 | 2 / 4 | |
| 1.2.1 | 2 / 3 | |
| 1.2.0 | 1 / 3 | |
| 1.0.0 | 1 / 3 |
v1.3.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: turbo87.
This version was published by a different npm account (turbo87) than the most recent previously approved version (rwjblue) on 2019-01-09. It has since remained available on npm for 2750 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rwjblue) than the most recent previously approved version (stefanpenner) on 2018-12-06, but rwjblue is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.2.0
2 findingsThis version was published by a different npm account (stefanpenner) than the most recent previously approved version (chadhietala) on 2018-01-11. It has since remained available on npm for 3113 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.