@hizzlewp/settings
Display a settings page
Supply chain provenance
Status for the latest visible version.
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): Transition to GitHub Actions publisher is confirmed legitimate by SLSA provenance attestation; consistent with CI/CD automation. | ai | |
| provenance | no-provenance | AI (provenance): Common for WordPress ecosystem packages; no other risk signals present. | ai | |
| dependencies | unvetted-dep:@hizzlewp/interface | AI (dependencies): Sibling package from the same hizzle-co monorepo; consistent with the package's own origin. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 1.3.13 | 7 / 0 | |
| 1.3.12 | 7 / 0 | |
| 1.3.11 | 7 / 0 | |
| 1.3.10 | 7 / 0 | |
| 1.3.9 | 7 / 0 | |
| 1.3.8 | 7 / 0 | |
| 1.3.7 | 7 / 0 | |
| 1.3.6 | 7 / 0 | |
| 1.3.5 | 7 / 0 | |
| 1.3.4 | 7 / 0 | |
| 1.3.3 | 7 / 0 | |
| 1.3.2 | 7 / 0 | |
| 1.3.1 | 7 / 0 | |
| 1.3.0 | 7 / 0 | |
| 1.2.0 | 7 / 0 | |
| 1.1.2 | 7 / 0 | |
| 1.1.1 | 7 / 0 | |
| 1.1.0 | 7 / 0 | |
| 1.0.11 | 7 / 0 | |
| 1.0.10 | 7 / 0 | |
| 1.0.9 | 7 / 0 | |
| 1.0.8 | 7 / 0 | |
| 1.0.7 | 7 / 0 | |
| 1.0.6 | 7 / 0 | |
| 1.0.5 | 7 / 0 | |
| 1.0.4 | 7 / 0 | |
| 1.0.3 | 7 / 0 | |
| 1.0.2 | 7 / 0 | |
| 1.0.1 | 7 / 0 |
v1.3.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.