@metaplex-foundation/umi-http-fetch
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): No behavior change vs prior approved version; publisher track record is clean. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Likely monorepo batch release cadence, not takeover; no malicious diff. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.5.1 | 1 / 5 | |
| 1.4.1 | 1 / 5 | |
| 1.4.0 | 1 / 5 | |
| 1.3.0 | 1 / 5 | |
| 1.2.0 | 1 / 5 | |
| 1.1.1 | 1 / 5 | |
| 1.1.0 | 1 / 5 | |
| 1.0.0 | 1 / 5 |
v1.4.1
3 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nhanphan.
This version was published by a different npm account (nhanphan) than the most recent previously approved version (blockiosaurus) on 2025-09-01, but nhanphan 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.4.0
3 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nhanphan.
This version was published by a different npm account (nhanphan) than the most recent previously approved version (blockiosaurus) on 2025-08-29, but nhanphan 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 has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: blockiosaurus.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: blockiosaurus.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.