@wordpress/data
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 | AI (provenance): mamaduka is an established WordPress org publisher with 352 approved packages; transition from gutenbergplugin is consistent with org maintainer rotation. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get used in a documented Proxy-based private API wrapper; not obfuscation. | ai | |
| phantom-deps | phantom-dep:use-memo-one | AI (phantom-deps): use-memo-one is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 64 of 64)
| Version | Deps | Published |
|---|---|---|
| 10.51.0 | 14 / 4 | |
| 10.50.0 | 14 / 4 | |
| 10.49.0 | 14 / 4 | |
| 10.48.1 | 15 / 4 | |
| 10.48.0 | 14 / 1 | |
| 10.47.0 | 14 / 1 | |
| 10.46.0 | 14 / 1 | |
| 10.45.0 | 14 / 1 | |
| 10.44.0 | 14 / 1 | |
| 10.43.0 | 14 / 1 | |
| 10.42.0 | 14 / 1 | |
| 10.41.0 | 14 / 1 | |
| 10.40.1 | 14 / 1 | |
| 10.40.0 | 14 / 1 | |
| 10.39.0 | 14 / 1 | |
| 10.38.0 | 14 / 1 | |
| 10.37.0 | 14 / 0 | |
| 10.36.0 | 14 / 0 | |
| 10.35.0 | 14 / 0 | |
| 10.34.0 | 14 / 0 | |
| 10.33.1 | 14 / 0 | |
| 10.33.0 | 14 / 0 | |
| 10.32.0 | 15 / 0 | |
| 10.31.0 | 15 / 0 | |
| 10.30.0 | 15 / 0 | |
| 10.29.0 | 15 / 0 | |
| 10.28.0 | 15 / 0 | |
| 10.27.0 | 15 / 0 | |
| 10.26.0 | 15 / 0 | |
| 10.25.0 | 15 / 0 | |
| 10.24.0 | 15 / 0 | |
| 10.23.0 | 15 / 0 | |
| 10.22.0 | 15 / 0 | |
| 10.21.0 | 15 / 0 | |
| 10.20.0 | 15 / 0 | |
| 10.19.2 | 15 / 0 | |
| 10.19.1 | 15 / 0 | |
| 10.19.0 | 15 / 0 | |
| 10.18.0 | 15 / 0 | |
| 10.17.0 | 15 / 0 | |
| 10.16.0 | 15 / 0 | |
| 10.15.1 | 15 / 0 | |
| 10.15.0 | 15 / 0 | |
| 10.14.0 | 15 / 0 | |
| 10.13.0 | 15 / 0 | |
| 10.12.0 | 15 / 0 | |
| 10.11.0 | 15 / 0 | |
| 10.10.0 | 15 / 0 | |
| 10.9.0 | 15 / 0 | |
| 10.8.4 | 15 / 0 | |
| 10.8.3 | 15 / 0 | |
| 10.8.2 | 15 / 0 | |
| 10.8.1 | 15 / 0 | |
| 10.8.0 | 15 / 0 | |
| 10.7.0 | 15 / 0 | |
| 10.6.0 | 15 / 0 | |
| 10.5.0 | 15 / 0 | |
| 10.4.0 | 15 / 0 | |
| 10.3.0 | 15 / 0 | |
| 10.2.0 | 15 / 0 | |
| 10.1.0 | 15 / 0 | |
| 10.0.2 | 15 / 0 | |
| 10.0.1 | 15 / 0 | |
| 10.0.0 | 15 / 0 |
v10.51.0
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 (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.
v10.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.40.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 (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.
v10.22.0
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 (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.
v10.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.15.0
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 (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.
v10.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.