@cloudscape-design/chart-components
This package contains the source code of chart components in the [Cloudscape Design System](https://cloudscape.design/). For more information about chart components, see [the documentation](https://cloudscape.design/components/charts/).
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 |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): Automated CI publishing pipeline for AWS Cloudscape; rapid successive publishes are expected across this package suite. | ai | |
| npm-metadata | url-dep:@cloudscape-design/build-tools | AI (npm-metadata): Dev-only GitHub URL dep for internal build tooling; consistent pattern across Cloudscape org packages. | ai | |
| dependencies | unvetted-dep:@cloudscape-design/component-toolkit | AI (dependencies): Sibling Cloudscape Design System package from the same AWS org; expected internal dependency. | ai | |
| provenance | no-provenance | AI (provenance): AWS Cloudscape packages consistently lack Sigstore provenance; stable false positive for this package family. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 1.0.100 | 3 / 56 | |
| 1.0.95 | 3 / 56 | |
| 1.0.94 | 3 / 56 | |
| 1.0.91 | 3 / 56 | |
| 1.0.90 | 3 / 56 | |
| 1.0.89 | 3 / 56 | |
| 1.0.88 | 3 / 56 | |
| 1.0.87 | 3 / 56 | |
| 1.0.86 | 3 / 56 | |
| 1.0.85 | 3 / 56 | |
| 1.0.84 | 3 / 56 | |
| 1.0.82 | 3 / 56 | |
| 1.0.81 | 3 / 56 | |
| 1.0.80 | 3 / 56 | |
| 1.0.79 | 3 / 56 | |
| 1.0.76 | 3 / 56 | |
| 1.0.75 | 3 / 56 | |
| 1.0.74 | 3 / 56 | |
| 1.0.73 | 3 / 56 | |
| 1.0.72 | 3 / 56 | |
| 1.0.71 | 3 / 56 | |
| 1.0.70 | 3 / 56 | |
| 1.0.63 | 3 / 56 | |
| 1.0.59 | 3 / 56 | |
| 1.0.57 | 3 / 56 | |
| 1.0.55 | 3 / 56 | |
| 1.0.53 | 3 / 56 | |
| 1.0.52 | 3 / 56 | |
| 1.0.48 | 3 / 56 | |
| 1.0.47 | 3 / 56 | |
| 1.0.42 | 3 / 56 | |
| 1.0.41 | 3 / 56 | |
| 1.0.36 | 3 / 56 | |
| 1.0.34 | 3 / 56 | |
| 1.0.27 | 3 / 55 | |
| 1.0.26 | 3 / 55 | |
| 1.0.23 | 3 / 55 | |
| 1.0.17 | 3 / 55 | |
| 1.0.16 | 3 / 55 | |
| 1.0.15 | 3 / 55 | |
| 1.0.14 | 3 / 55 | |
| 1.0.13 | 3 / 55 | |
| 1.0.11 | 3 / 55 | |
| 1.0.2 | 3 / 55 |
v1.0.100
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.95
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.91
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. Consider requesting the maintainer enable provenance via CI/CD.
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.87
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. 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.84
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.82
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.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.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.
v1.0.72
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.71
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.70
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.63
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.59
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.57
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.55
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.53
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.52
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.48
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.47
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.42
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.41
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.36
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.34
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.27
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.26
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.16
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.15
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.14
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.13
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.11
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.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.