@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 — 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 |
|---|---|---|---|---|
| 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 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 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.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 |
v2.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.33.3
2 findingsThis version was published by a different npm account than previous versions on 2026-01-29. 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.
v2.33.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.