← Home

@hizzlewp/components

npm Repository Homepage

Reusable React UI components for WordPress plugins

36
Versions
GPL-2.0-or-later
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

picocode

Keywords

wordpresshizzle

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI/CD publishing is confirmed by SLSA provenance attestation; stable pattern for this package going forward. ai

Versions (showing 36 of 36)

Version Deps Published
1.5.13 3 / 0
1.5.12 3 / 0
1.5.11 3 / 0
1.5.10 3 / 0
1.5.9 3 / 0
1.5.8 3 / 0
1.5.7 3 / 0
1.5.6 3 / 0
1.5.5 3 / 0
1.5.4 3 / 0
1.5.3 3 / 0
1.5.2 3 / 0
1.5.1 3 / 0
1.5.0 3 / 0
1.4.0 3 / 0
1.3.2 3 / 0
1.3.1 3 / 0
1.3.0 3 / 0
1.2.14 3 / 0
1.2.13 3 / 0
1.2.12 3 / 0
1.2.11 3 / 0
1.2.10 3 / 0
1.2.9 3 / 0
1.2.8 3 / 0
1.2.7 3 / 0
1.2.6 3 / 0
1.2.5 3 / 0
1.2.4 3 / 0
1.2.3 3 / 0
1.2.2 3 / 0
1.2.1 3 / 0
1.2.0 3 / 1
1.1.1 3 / 1
1.1.0 3 / 1
1.0.1 3 / 1

v1.5.13

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.2.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.