← Home

@zendeskgarden/react-pagination

npm Repository Homepage

Components relating to pagination in the Garden Design System

42
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

zendesk-garden

Keywords

componentsgardenreactzendesk

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Zendesk Garden org consistently publishes without Sigstore provenance; stable pattern across all versions. ai

Versions (showing 42 of 42)

Version Deps Published
9.15.6 3 / 2
9.15.5 3 / 2
9.15.4 3 / 2
9.15.3 3 / 2
9.15.2 3 / 2
9.15.1 3 / 2
9.15.0 3 / 2
9.14.2 3 / 2
9.14.1 3 / 2
9.14.0 3 / 2
9.13.0 3 / 2
9.12.6 3 / 2
9.12.5 3 / 2
9.12.4 3 / 2
9.12.3 3 / 2
9.12.2 3 / 2
9.12.1 3 / 2
9.12.0 3 / 2
9.11.3 3 / 2
9.11.2 3 / 2
9.11.1 3 / 2
9.11.0 3 / 2
9.10.1 3 / 2
9.10.0 3 / 2
9.9.0 3 / 2
9.8.0 3 / 2
9.7.2 3 / 2
9.7.1 3 / 2
9.7.0 3 / 2
9.6.0 3 / 2
9.5.4 3 / 2
9.5.3 3 / 2
9.5.2 3 / 2
9.5.1 3 / 2
9.5.0 3 / 2
9.4.0 3 / 2
9.3.0 3 / 2
9.2.0 3 / 2
9.1.2 3 / 2
9.1.1 3 / 2
9.1.0 3 / 2
9.0.0 3 / 2

v9.5.4

1 finding
INFO No provenance attestation provenance

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

v9.5.3

1 finding
INFO No provenance attestation provenance

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

v9.5.2

1 finding
INFO No provenance attestation provenance

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

v9.5.1

1 finding
INFO No provenance attestation provenance

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

v9.5.0

1 finding
INFO No provenance attestation provenance

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

v9.4.0

1 finding
INFO No provenance attestation provenance

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

v9.3.0

1 finding
INFO No provenance attestation provenance

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

v9.2.0

1 finding
INFO No provenance attestation provenance

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

v9.1.2

1 finding
INFO No provenance attestation provenance

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

v9.1.1

1 finding
INFO No provenance attestation provenance

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

v9.1.0

1 finding
INFO No provenance attestation provenance

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

v9.0.0

1 finding
INFO No provenance attestation provenance

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