@wordpress/interactivity-router
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): es-module-lexer is a legitimate, widely-used ES module parsing library; addition is consistent with package's interactivity/routing purpose. | ai | |
| provenance | publisher-changed | AI (provenance): peterwilsoncc is a verified WordPress contributor with a long, clean publishing history; transition from gutenbergplugin is a known org account change. | ai |
Versions (showing 68 of 68)
| Version | Deps | Published |
|---|---|---|
| 2.51.0 | 3 / 0 | |
| 2.50.0 | 3 / 0 | |
| 2.49.0 | 3 / 0 | |
| 2.48.1 | 3 / 0 | |
| 2.48.0 | 3 / 0 | |
| 2.47.0 | 3 / 0 | |
| 2.46.0 | 3 / 0 | |
| 2.45.0 | 3 / 0 | |
| 2.44.0 | 3 / 0 | |
| 2.43.0 | 3 / 0 | |
| 2.42.0 | 3 / 0 | |
| 2.41.0 | 3 / 0 | |
| 2.40.1 | 3 / 0 | |
| 2.40.0 | 3 / 0 | |
| 2.39.0 | 3 / 0 | |
| 2.38.0 | 3 / 0 | |
| 2.37.0 | 3 / 0 | |
| 2.36.0 | 3 / 0 | |
| 2.35.0 | 3 / 0 | |
| 2.34.0 | 3 / 0 | |
| 2.33.3 | 3 / 0 | |
| 2.33.2 | 3 / 0 | |
| 2.33.1 | 3 / 0 | |
| 2.33.0 | 3 / 0 | |
| 2.32.0 | 3 / 0 | |
| 2.31.0 | 3 / 0 | |
| 2.30.0 | 3 / 0 | |
| 2.29.0 | 3 / 0 | |
| 2.28.0 | 3 / 0 | |
| 2.27.0 | 3 / 0 | |
| 2.26.0 | 3 / 0 | |
| 2.25.0 | 2 / 0 | |
| 2.24.0 | 2 / 0 | |
| 2.23.0 | 2 / 0 | |
| 2.22.0 | 2 / 0 | |
| 2.21.0 | 2 / 0 | |
| 2.20.0 | 2 / 0 | |
| 2.19.1 | 2 / 0 | |
| 2.19.0 | 2 / 0 | |
| 2.18.0 | 2 / 0 | |
| 2.17.0 | 2 / 0 | |
| 2.16.0 | 2 / 0 | |
| 2.15.1 | 2 / 0 | |
| 2.15.0 | 2 / 0 | |
| 2.14.0 | 2 / 0 | |
| 2.13.0 | 2 / 0 | |
| 2.12.0 | 2 / 0 | |
| 2.11.0 | 2 / 0 | |
| 2.10.0 | 2 / 0 | |
| 2.9.0 | 2 / 0 | |
| 2.8.7 | 2 / 0 | |
| 2.8.6 | 2 / 0 | |
| 2.8.5 | 2 / 0 | |
| 2.8.4 | 2 / 0 | |
| 2.8.3 | 2 / 0 | |
| 2.8.2 | 2 / 0 | |
| 2.8.1 | 2 / 0 | |
| 2.8.0 | 2 / 0 | |
| 2.7.0 | 1 / 0 | |
| 2.6.0 | 1 / 0 | |
| 2.5.0 | 1 / 0 | |
| 2.4.0 | 1 / 0 | |
| 2.3.0 | 1 / 0 | |
| 2.2.0 | 1 / 0 | |
| 2.1.0 | 1 / 0 | |
| 2.0.2 | 1 / 0 | |
| 2.0.1 | 1 / 0 | |
| 2.0.0 | 1 / 0 |
v2.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.
v2.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.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.
v2.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.
v2.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.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.
v2.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.
v2.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.