@wordpress/notices
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 contributor with 354 approved packages; change consistent with team rotation. | ai | |
| dependencies | unvetted-dep:@wordpress/a11y | AI (dependencies): Sibling WordPress monorepo package; unvetted status is a registry gap, not a risk signal. | ai | |
| dependencies | unvetted-dep:@wordpress/data | AI (dependencies): Sibling WordPress monorepo package; unvetted status is a registry gap, not a risk signal. | ai | |
| dependencies | unvetted-dep:@wordpress/components | AI (dependencies): Sibling WordPress monorepo package; unvetted status is a registry gap, not a risk signal. | ai |
Versions (showing 65 of 65)
| Version | Deps | Published |
|---|---|---|
| 5.51.0 | 4 / 3 | |
| 5.50.0 | 4 / 3 | |
| 5.49.1 | 4 / 3 | |
| 5.49.0 | 4 / 3 | |
| 5.48.1 | 5 / 3 | |
| 5.48.0 | 4 / 1 | |
| 5.47.0 | 4 / 1 | |
| 5.46.0 | 4 / 1 | |
| 5.45.0 | 4 / 1 | |
| 5.44.0 | 4 / 1 | |
| 5.43.0 | 4 / 1 | |
| 5.42.0 | 4 / 1 | |
| 5.41.0 | 4 / 1 | |
| 5.40.1 | 4 / 1 | |
| 5.40.0 | 4 / 1 | |
| 5.39.0 | 2 / 1 | |
| 5.38.0 | 2 / 1 | |
| 5.37.0 | 2 / 0 | |
| 5.36.0 | 2 / 0 | |
| 5.35.0 | 2 / 0 | |
| 5.34.0 | 2 / 0 | |
| 5.33.1 | 2 / 0 | |
| 5.33.0 | 2 / 0 | |
| 5.32.0 | 3 / 0 | |
| 5.31.0 | 3 / 0 | |
| 5.30.0 | 3 / 0 | |
| 5.29.0 | 3 / 0 | |
| 5.28.0 | 3 / 0 | |
| 5.27.0 | 3 / 0 | |
| 5.26.0 | 3 / 0 | |
| 5.25.0 | 3 / 0 | |
| 5.24.0 | 3 / 0 | |
| 5.23.0 | 3 / 0 | |
| 5.22.0 | 3 / 0 | |
| 5.21.0 | 3 / 0 | |
| 5.20.0 | 3 / 0 | |
| 5.19.2 | 3 / 0 | |
| 5.19.1 | 3 / 0 | |
| 5.19.0 | 3 / 0 | |
| 5.18.0 | 3 / 0 | |
| 5.17.0 | 3 / 0 | |
| 5.16.0 | 3 / 0 | |
| 5.15.1 | 3 / 0 | |
| 5.15.0 | 3 / 0 | |
| 5.14.0 | 3 / 0 | |
| 5.13.0 | 3 / 0 | |
| 5.12.0 | 3 / 0 | |
| 5.11.0 | 3 / 0 | |
| 5.10.0 | 3 / 0 | |
| 5.9.0 | 3 / 0 | |
| 5.8.4 | 3 / 0 | |
| 5.8.3 | 3 / 0 | |
| 5.8.2 | 3 / 0 | |
| 5.8.1 | 3 / 0 | |
| 5.8.0 | 3 / 0 | |
| 5.7.0 | 3 / 0 | |
| 5.6.0 | 3 / 0 | |
| 5.5.0 | 3 / 0 | |
| 5.4.0 | 3 / 0 | |
| 5.3.0 | 3 / 0 | |
| 5.2.0 | 3 / 0 | |
| 5.1.0 | 3 / 0 | |
| 5.0.2 | 3 / 0 | |
| 5.0.1 | 3 / 0 | |
| 5.0.0 | 3 / 0 |
v5.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.
v5.50.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 (gutenbergplugin) than the most recent previously approved version (desrosj) on 2026-07-01, but gutenbergplugin 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.
v5.49.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.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.
v5.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.
v5.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.16.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 (gutenbergplugin) than the most recent previously approved version (gziolo) on 2025-01-15, but gutenbergplugin 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.
v5.15.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 (gutenbergplugin) than the most recent previously approved version (gziolo) on 2025-01-03, but gutenbergplugin 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.
v5.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.
v5.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.