@wordpress/compose
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
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 352 approved packages; transition from gutenbergplugin is consistent with org maintainer rotation. | ai | |
| phantom-deps | phantom-dep:@types/mousetrap | AI (phantom-deps): @types/mousetrap is a TypeScript type package for mousetrap, a direct dep; declared but not imported by convention. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 8.1.0 | 12 / 1 | |
| 8.0.0 | 12 / 1 | |
| 7.46.0 | 11 / 1 | |
| 7.45.0 | 11 / 1 | |
| 7.44.0 | 11 / 1 | |
| 7.43.0 | 11 / 1 | |
| 7.42.0 | 11 / 1 | |
| 7.41.0 | 12 / 1 | |
| 7.40.0 | 12 / 1 | |
| 7.39.0 | 12 / 1 | |
| 7.38.0 | 12 / 1 | |
| 7.37.0 | 12 / 0 | |
| 7.36.0 | 12 / 0 | |
| 7.35.0 | 12 / 0 | |
| 7.34.0 | 12 / 0 | |
| 7.33.1 | 12 / 0 | |
| 7.33.0 | 12 / 0 | |
| 7.32.0 | 13 / 0 | |
| 7.31.0 | 13 / 0 | |
| 7.30.0 | 13 / 0 | |
| 7.29.0 | 13 / 0 | |
| 7.28.0 | 13 / 0 | |
| 7.27.0 | 13 / 0 | |
| 7.26.0 | 13 / 0 | |
| 7.25.0 | 13 / 0 | |
| 7.24.0 | 13 / 0 | |
| 7.23.0 | 13 / 0 | |
| 7.19.2 | 13 / 0 |
v8.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.19.2
2 findingsThis version was published by a different npm account than previous versions on 2025-07-08. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.