@zendeskgarden/react-typography
Components relating to typography in the Garden Design System
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Zendesk Garden org package; missing provenance is consistent across all their releases. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 9.15.7 | 4 / 1 | |
| 9.15.6 | 4 / 1 | |
| 9.15.5 | 4 / 1 | |
| 9.15.4 | 4 / 1 | |
| 9.15.3 | 4 / 1 | |
| 9.15.2 | 4 / 1 | |
| 9.15.1 | 4 / 1 | |
| 9.15.0 | 4 / 1 | |
| 9.14.2 | 4 / 1 | |
| 9.14.1 | 4 / 1 | |
| 9.14.0 | 4 / 1 | |
| 9.13.0 | 4 / 1 | |
| 9.12.6 | 4 / 1 | |
| 9.12.5 | 4 / 1 | |
| 9.12.4 | 4 / 1 | |
| 9.12.3 | 4 / 1 | |
| 9.12.2 | 4 / 1 | |
| 9.12.1 | 4 / 1 | |
| 9.12.0 | 4 / 1 | |
| 9.11.3 | 4 / 1 | |
| 9.11.2 | 4 / 1 | |
| 9.11.1 | 4 / 1 | |
| 9.11.0 | 4 / 1 | |
| 9.10.1 | 4 / 1 | |
| 9.10.0 | 4 / 1 | |
| 9.9.0 | 4 / 1 | |
| 9.8.0 | 4 / 1 | |
| 9.7.2 | 4 / 1 | |
| 9.7.1 | 4 / 1 | |
| 9.7.0 | 4 / 1 | |
| 9.6.0 | 4 / 1 | |
| 9.5.4 | 4 / 1 | |
| 9.5.3 | 4 / 1 | |
| 9.5.2 | 4 / 1 | |
| 9.5.1 | 4 / 1 | |
| 9.5.0 | 4 / 1 | |
| 9.4.0 | 4 / 1 | |
| 9.3.0 | 4 / 1 | |
| 9.2.0 | 4 / 1 | |
| 9.1.2 | 4 / 1 | |
| 9.1.1 | 4 / 1 | |
| 9.1.0 | 4 / 1 | |
| 9.0.0 | 4 / 1 |
v9.15.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.