@zendeskgarden/react-dropdowns
Components related to dropdowns 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): Long-established Zendesk Garden package; no provenance is consistent across all versions of this monorepo. | ai | |
| dependencies | unvetted-dep:@zendeskgarden/react-forms | AI (dependencies): First-party sibling package from the same Zendesk Garden monorepo; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@zendeskgarden/react-buttons | AI (dependencies): First-party sibling package from the same Zendesk Garden monorepo; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@zendeskgarden/container-menu | AI (dependencies): First-party sibling package from the same Zendesk Garden monorepo; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@zendeskgarden/react-tags | AI (dependencies): First-party sibling package from the same Zendesk Garden monorepo; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@zendeskgarden/container-combobox | AI (dependencies): First-party sibling package from the same Zendesk Garden monorepo; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@zendeskgarden/container-utilities | AI (dependencies): First-party sibling package from the same Zendesk Garden monorepo; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@zendeskgarden/react-tooltips | AI (dependencies): First-party sibling package from the same Zendesk Garden monorepo; not a third-party risk. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 9.15.4 | 11 / 2 | |
| 9.15.3 | 11 / 2 | |
| 9.15.2 | 11 / 2 | |
| 9.15.1 | 11 / 2 | |
| 9.15.0 | 11 / 2 | |
| 9.14.2 | 11 / 2 | |
| 9.14.1 | 11 / 2 | |
| 9.14.0 | 11 / 2 | |
| 9.13.0 | 11 / 2 | |
| 9.12.6 | 11 / 2 | |
| 9.12.5 | 11 / 2 | |
| 9.12.4 | 11 / 2 | |
| 9.12.3 | 11 / 2 | |
| 9.12.2 | 11 / 2 | |
| 9.12.1 | 11 / 2 | |
| 9.12.0 | 11 / 2 | |
| 9.11.3 | 11 / 2 | |
| 9.11.2 | 11 / 2 | |
| 9.11.1 | 11 / 2 | |
| 9.11.0 | 11 / 2 | |
| 9.10.1 | 11 / 2 | |
| 9.10.0 | 11 / 2 | |
| 9.9.0 | 11 / 2 | |
| 9.8.0 | 11 / 2 | |
| 9.7.2 | 11 / 2 | |
| 9.7.1 | 11 / 2 | |
| 9.7.0 | 11 / 2 | |
| 9.6.0 | 11 / 2 |
v9.15.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.14.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.12.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.7.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.
v9.7.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.
v9.6.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.