@cloudscape-design/chat-components
This package contains the source code of conversation-oriented components in the [Cloudscape Design System](https://cloudscape.design/). For more information about chat components, see [the documentation](https://cloudscape.design/components/chat-componen
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): Dev-only GitHub URL dep for AWS internal build tooling; stable pattern across this package family, no runtime impact. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size growth is from added generated theming/token files, not injected payloads; consistent with Cloudscape build output. | ai | |
| dependencies | unvetted-dep:@cloudscape-design/test-utils-core | AI (dependencies): First-party AWS Cloudscape dependency; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@cloudscape-design/component-toolkit | AI (dependencies): First-party AWS Cloudscape dependency; stable false positive for this package family. | ai | |
| provenance | no-provenance | AI (provenance): AWS Cloudscape org packages consistently lack Sigstore provenance; stable false positive for this package family. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 1.0.130 | 3 / 56 | |
| 1.0.126 | 3 / 56 | |
| 1.0.124 | 3 / 56 | |
| 1.0.123 | 3 / 56 | |
| 1.0.121 | 3 / 56 | |
| 1.0.120 | 3 / 56 | |
| 1.0.118 | 3 / 56 | |
| 1.0.117 | 3 / 56 | |
| 1.0.116 | 3 / 56 | |
| 1.0.115 | 3 / 56 | |
| 1.0.113 | 3 / 56 | |
| 1.0.112 | 3 / 56 | |
| 1.0.110 | 3 / 56 | |
| 1.0.108 | 3 / 56 | |
| 1.0.85 | 3 / 56 | |
| 1.0.73 | 3 / 55 | |
| 1.0.72 | 3 / 55 | |
| 1.0.70 | 3 / 55 | |
| 1.0.66 | 3 / 55 | |
| 1.0.62 | 3 / 55 | |
| 1.0.52 | 3 / 54 | |
| 1.0.46 | 3 / 54 | |
| 1.0.45 | 3 / 54 | |
| 1.0.44 | 3 / 54 | |
| 1.0.43 | 3 / 54 | |
| 1.0.40 | 3 / 0 |
v1.0.130
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.126
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.124
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.120
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.118
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.117
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.116
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.115
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.113
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.112
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.110
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.108
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.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v1.0.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.