@cloudscape-design/collection-hooks
This package contains the source code of the React collection hooks for the [Cloudscape Design System](https://cloudscape.design/).
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | url-dep:@cloudscape-design/build-tools | AI (npm-metadata): GitHub URL is for an internal dev/build tool only; does not affect published runtime package contents. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a first-party @cloudscape-design package from the same AWS UI org; not a supply-chain risk. | ai | |
| provenance | no-provenance | AI (provenance): AWS Cloudscape CI-published package; lack of Sigstore attestation is consistent across all versions and not a risk indicator for this org. | ai | |
| dependencies | unvetted-dep:@cloudscape-design/component-toolkit | AI (dependencies): Same-org sibling dependency from cloudscape-design; stable pattern across all versions of this package. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.0.96 | 1 / 24 | |
| 1.0.94 | 1 / 24 | |
| 1.0.92 | 1 / 24 | |
| 1.0.91 | 1 / 24 | |
| 1.0.90 | 1 / 24 | |
| 1.0.89 | 1 / 24 | |
| 1.0.88 | 1 / 24 | |
| 1.0.86 | 1 / 24 | |
| 1.0.84 | 1 / 24 | |
| 1.0.83 | 1 / 24 | |
| 1.0.82 | 1 / 24 | |
| 1.0.81 | 0 / 23 | |
| 1.0.80 | 0 / 23 | |
| 1.0.79 | 0 / 23 | |
| 1.0.78 | 0 / 23 | |
| 1.0.77 | 0 / 23 | |
| 1.0.76 | 0 / 23 | |
| 1.0.75 | 0 / 23 | |
| 1.0.74 | 0 / 23 | |
| 1.0.73 | 0 / 23 |
v1.0.96
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.