@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, 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 |
|---|---|---|---|---|
| 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 51 of 80)
| Version | Deps | Published |
|---|---|---|
| 10.3.0 | 2 / 3 | |
| 10.2.0 | 2 / 3 | |
| 10.1.0 | 2 / 3 | |
| 10.0.1 | 2 / 3 | |
| 10.0.0 | 2 / 3 | |
| 9.48.0 | 8 / 0 | |
| 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.1 | 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.22.0 | 8 / 0 | |
| 9.21.0 | 8 / 0 | |
| 9.20.0 | 8 / 0 | |
| 9.19.4 | 8 / 0 | |
| 9.19.3 | 8 / 0 | |
| 9.19.2 | 8 / 0 | |
| 9.19.1 | 8 / 0 | |
| 9.19.0 | 8 / 0 | |
| 9.18.0 | 8 / 0 | |
| 9.17.0 | 8 / 0 | |
| 9.16.0 | 8 / 0 | |
| 9.15.1 | 8 / 0 | |
| 9.15.0 | 8 / 0 | |
| 9.14.0 | 8 / 0 |
v10.3.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.2.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.
v9.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.
v9.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.
v9.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.19.3
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-04-28, 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.
v9.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.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.
v9.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.
v9.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.
v9.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.