@wordpress/api-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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): WordPress Gutenberg monorepo packages consistently lack Sigstore provenance; stable false positive for this publisher. | ai | |
| dependencies | unvetted-dep:@wordpress/url | AI (dependencies): @wordpress/url is a sibling WordPress core package from the same Gutenberg monorepo; stable false positive. | ai | |
| provenance | publisher-changed | AI (provenance): gutenbergplugin is the official WordPress Gutenberg org account; transition from individual maintainer is expected. | ai |
Versions (showing 61 of 61)
| Version | Deps | Published |
|---|---|---|
| 7.51.0 | 3 / 0 | |
| 7.50.0 | 3 / 0 | |
| 7.49.0 | 3 / 0 | |
| 7.48.1 | 3 / 0 | |
| 7.48.0 | 3 / 0 | |
| 7.47.0 | 3 / 0 | |
| 7.46.0 | 2 / 0 | |
| 7.45.0 | 2 / 0 | |
| 7.44.0 | 2 / 0 | |
| 7.43.0 | 2 / 0 | |
| 7.42.0 | 2 / 0 | |
| 7.41.0 | 2 / 0 | |
| 7.40.1 | 2 / 0 | |
| 7.40.0 | 2 / 0 | |
| 7.39.0 | 2 / 0 | |
| 7.38.0 | 2 / 0 | |
| 7.37.0 | 2 / 0 | |
| 7.36.0 | 2 / 0 | |
| 7.35.0 | 2 / 0 | |
| 7.34.0 | 2 / 0 | |
| 7.33.1 | 2 / 0 | |
| 7.33.0 | 2 / 0 | |
| 7.32.0 | 3 / 0 | |
| 7.31.0 | 3 / 0 | |
| 7.30.0 | 3 / 0 | |
| 7.29.0 | 3 / 0 | |
| 7.28.0 | 3 / 0 | |
| 7.27.0 | 3 / 0 | |
| 7.26.0 | 3 / 0 | |
| 7.25.0 | 3 / 0 | |
| 7.24.0 | 3 / 0 | |
| 7.23.0 | 3 / 0 | |
| 7.22.0 | 3 / 0 | |
| 7.21.0 | 3 / 0 | |
| 7.20.0 | 3 / 0 | |
| 7.19.2 | 3 / 0 | |
| 7.19.1 | 3 / 0 | |
| 7.19.0 | 3 / 0 | |
| 7.18.0 | 3 / 0 | |
| 7.17.0 | 3 / 0 | |
| 7.16.0 | 3 / 0 | |
| 7.15.1 | 3 / 0 | |
| 7.15.0 | 3 / 0 | |
| 7.14.0 | 3 / 0 | |
| 7.13.0 | 3 / 0 | |
| 7.12.0 | 3 / 0 | |
| 7.11.0 | 3 / 0 | |
| 7.10.0 | 3 / 0 | |
| 7.9.0 | 3 / 0 | |
| 7.8.2 | 3 / 0 | |
| 7.8.1 | 3 / 0 | |
| 7.8.0 | 3 / 0 | |
| 7.7.0 | 3 / 0 | |
| 7.6.0 | 3 / 0 | |
| 7.5.0 | 3 / 0 | |
| 7.4.0 | 3 / 0 | |
| 7.3.0 | 3 / 0 | |
| 7.2.0 | 3 / 0 | |
| 7.1.0 | 3 / 0 | |
| 7.0.1 | 3 / 0 | |
| 7.0.0 | 3 / 0 |
v7.51.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (desrosj) than the most recent previously approved version (gutenbergplugin) on 2026-07-14, but desrosj 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.
v7.50.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.40.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (desrosj) than the most recent previously approved version (gutenbergplugin) on 2026-06-30, but desrosj 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.
v7.22.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gziolo) than the most recent previously approved version (gutenbergplugin) on 2025-04-11, but gziolo 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.
v7.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.19.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gziolo) than the most recent previously approved version (gutenbergplugin) on 2025-01-03, but gziolo 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.
v7.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.