@zendeskgarden/react-avatars
Components relating to avatars 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 — 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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Zendesk Garden monorepo packages consistently lack provenance; stable false positive for this publisher. | ai | |
| dependencies | unvetted-dep:@zendeskgarden/react-typography | AI (dependencies): Same-org monorepo sibling dependency; not an external unvetted package. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 9.15.4 | 3 / 3 | |
| 9.15.3 | 3 / 3 | |
| 9.15.2 | 3 / 3 | |
| 9.15.1 | 3 / 3 | |
| 9.15.0 | 3 / 3 | |
| 9.14.2 | 3 / 3 | |
| 9.14.1 | 3 / 3 | |
| 9.14.0 | 3 / 3 | |
| 9.13.0 | 3 / 3 | |
| 9.12.6 | 3 / 3 | |
| 9.12.5 | 3 / 3 | |
| 9.12.4 | 3 / 3 | |
| 9.12.3 | 3 / 3 | |
| 9.12.2 | 3 / 3 | |
| 9.12.1 | 3 / 3 | |
| 9.12.0 | 3 / 3 | |
| 9.11.3 | 3 / 3 | |
| 9.11.2 | 3 / 3 | |
| 9.11.1 | 3 / 3 | |
| 9.11.0 | 3 / 3 | |
| 9.10.1 | 3 / 3 | |
| 9.10.0 | 3 / 3 | |
| 9.9.0 | 3 / 3 | |
| 9.8.0 | 3 / 3 | |
| 9.7.2 | 3 / 3 | |
| 9.7.1 | 3 / 3 | |
| 9.7.0 | 2 / 3 | |
| 9.6.0 | 2 / 3 |
v9.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.