@wordpress/nux
NUX (New User eXperience) module for WordPress.
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:nuxt | AI (typosquat): Legitimate @wordpress scoped package from the Gutenberg monorepo; not a typosquat of nuxt. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): Legitimate @wordpress scoped package; not a typosquat of next. | ai | |
| typosquat | typosquat.levenshtein:knex | AI (typosquat): Legitimate @wordpress scoped package; not a typosquat of knex. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Legitimate @wordpress scoped package; not a typosquat of yup. | ai | |
| phantom-deps | phantom-dep:@wordpress/base-styles | AI (phantom-deps): @wordpress/base-styles is a CSS/SCSS dependency used at build time; not imported as JS, so phantom-dep is a stable false positive here. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 9.47.0 | 8 / 0 | |
| 9.46.0 | 8 / 0 | |
| 9.45.0 | 8 / 0 | |
| 9.44.0 | 8 / 0 | |
| 9.43.0 | 8 / 0 | |
| 9.42.0 | 8 / 0 | |
| 9.41.0 | 8 / 0 | |
| 9.40.0 | 8 / 0 | |
| 9.39.0 | 8 / 0 | |
| 9.38.0 | 8 / 0 | |
| 9.37.0 | 8 / 0 | |
| 9.36.0 | 8 / 0 | |
| 9.35.0 | 8 / 0 | |
| 9.34.0 | 8 / 0 | |
| 9.33.5 | 8 / 0 | |
| 9.33.4 | 8 / 0 | |
| 9.33.3 | 8 / 0 | |
| 9.33.2 | 8 / 0 | |
| 9.33.1 | 8 / 0 | |
| 9.33.0 | 8 / 0 | |
| 9.32.0 | 8 / 0 | |
| 9.31.0 | 8 / 0 | |
| 9.30.0 | 8 / 0 | |
| 9.29.0 | 8 / 0 | |
| 9.28.0 | 8 / 0 | |
| 9.27.0 | 8 / 0 | |
| 9.26.0 | 8 / 0 | |
| 9.25.0 | 8 / 0 | |
| 9.24.0 | 8 / 0 | |
| 9.23.0 | 8 / 0 | |
| 9.19.4 | 8 / 0 |
v9.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.46.0
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.45.0
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.44.0
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.43.0
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.42.0
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.41.0
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.40.0
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.39.0
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.38.0
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.37.0
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.36.0
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.35.0
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.34.0
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.33.5
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.33.4
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.33.3
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.33.2
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.33.1
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.33.0
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.32.0
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.31.0
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.30.0
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.29.0
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.28.0
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.27.0
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.26.0
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.25.0
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.24.0
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.23.0
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.19.4
2 findingsPackage name '@wordpress/nux' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.