@cloudscape-design/board-components
This package contains the source code of dashboard-oriented components in the [Cloudscape Design System](https://cloudscape.design/). For more information about board components, see [the documentation](https://cloudscape.design/components/board-component
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 internal build tooling from the same cloudscape-design org; no runtime impact, stable pattern across versions. | ai | |
| source-diff | source-size-tripled | AI (source-diff): AWS Cloudscape package; size growth consistent with bundled assets/test utils, no malicious indicators. | ai | |
| dependencies | unvetted-dep:@cloudscape-design/test-utils-core | AI (dependencies): First-party @cloudscape-design org dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@cloudscape-design/component-toolkit | AI (dependencies): First-party @cloudscape-design org dependency; stable pattern across all versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): Established AWS Cloudscape package; provenance not yet adopted by this publisher across the ecosystem. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 3.0.184 | 4 / 56 | |
| 3.0.175 | 4 / 56 | |
| 3.0.174 | 4 / 56 | |
| 3.0.173 | 4 / 56 | |
| 3.0.172 | 4 / 56 | |
| 3.0.171 | 4 / 56 | |
| 3.0.170 | 4 / 52 | |
| 3.0.169 | 4 / 56 | |
| 3.0.168 | 4 / 52 | |
| 3.0.167 | 4 / 52 | |
| 3.0.166 | 4 / 52 | |
| 3.0.165 | 4 / 52 | |
| 3.0.164 | 4 / 52 | |
| 3.0.163 | 4 / 52 | |
| 3.0.162 | 4 / 52 | |
| 3.0.161 | 4 / 52 | |
| 3.0.160 | 4 / 52 | |
| 3.0.156 | 4 / 52 | |
| 3.0.144 | 4 / 52 | |
| 3.0.132 | 4 / 52 | |
| 3.0.128 | 4 / 52 | |
| 3.0.114 | 4 / 52 | |
| 3.0.113 | 4 / 52 | |
| 3.0.110 | 4 / 52 | |
| 3.0.109 | 4 / 52 | |
| 3.0.107 | 4 / 52 | |
| 3.0.105 | 4 / 52 | |
| 3.0.104 | 4 / 52 | |
| 3.0.103 | 4 / 52 | |
| 3.0.102 | 4 / 52 |
v3.0.184
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.174
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.173
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.172
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.171
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.170
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.169
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.168
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.167
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.166
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.165
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.164
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.163
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.162
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.161
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.160
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.156
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.144
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.132
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.128
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.114
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.113
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.110
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.109
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.107
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.105
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.104
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.103
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.102
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.