@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, so a manually published version cannot be tied back to a reviewed commit.
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): Normal CI release cadence for this trusted AWS publisher. | ai | |
| 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 95 of 95)
| Version | Deps | Published |
|---|---|---|
| 3.0.209 | 4 / 56 | |
| 3.0.208 | 4 / 56 | |
| 3.0.204 | 4 / 56 | |
| 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 | |
| 3.0.67 | 4 / 0 | |
| 3.0.60 | 4 / 0 | |
| 3.0.59 | 4 / 0 | |
| 3.0.58 | 4 / 0 | |
| 3.0.57 | 4 / 0 | |
| 3.0.56 | 4 / 0 | |
| 3.0.55 | 4 / 0 | |
| 3.0.54 | 4 / 0 | |
| 3.0.53 | 4 / 0 | |
| 3.0.52 | 4 / 0 | |
| 3.0.51 | 4 / 0 | |
| 3.0.50 | 4 / 0 | |
| 3.0.49 | 4 / 0 | |
| 3.0.48 | 4 / 0 | |
| 3.0.47 | 4 / 0 | |
| 3.0.46 | 4 / 0 | |
| 3.0.45 | 4 / 0 | |
| 3.0.44 | 4 / 0 | |
| 3.0.43 | 4 / 0 | |
| 3.0.42 | 4 / 0 | |
| 3.0.41 | 4 / 0 | |
| 3.0.40 | 4 / 0 | |
| 3.0.39 | 4 / 0 | |
| 3.0.38 | 4 / 0 | |
| 3.0.37 | 4 / 0 | |
| 3.0.36 | 4 / 0 | |
| 3.0.35 | 4 / 0 | |
| 3.0.34 | 4 / 0 | |
| 3.0.33 | 4 / 0 | |
| 3.0.32 | 4 / 0 | |
| 3.0.31 | 4 / 0 | |
| 3.0.30 | 4 / 0 | |
| 3.0.29 | 4 / 0 | |
| 3.0.28 | 4 / 0 | |
| 3.0.27 | 4 / 0 | |
| 3.0.26 | 4 / 0 | |
| 3.0.25 | 4 / 0 | |
| 3.0.24 | 4 / 0 | |
| 3.0.23 | 4 / 0 | |
| 3.0.22 | 4 / 0 | |
| 3.0.21 | 4 / 0 | |
| 3.0.20 | 4 / 0 | |
| 3.0.19 | 4 / 0 | |
| 3.0.18 | 4 / 0 | |
| 3.0.17 | 4 / 0 | |
| 3.0.16 | 4 / 0 | |
| 3.0.15 | 4 / 0 | |
| 3.0.14 | 4 / 0 | |
| 3.0.13 | 4 / 0 | |
| 3.0.12 | 4 / 0 | |
| 3.0.11 | 4 / 0 | |
| 3.0.10 | 4 / 0 | |
| 3.0.9 | 4 / 0 | |
| 3.0.8 | 4 / 0 | |
| 3.0.7 | 4 / 0 | |
| 3.0.6 | 4 / 0 | |
| 3.0.5 | 4 / 0 | |
| 3.0.4 | 4 / 0 | |
| 3.0.3 | 4 / 0 | |
| 3.0.2 | 4 / 0 | |
| 3.0.1 | 4 / 0 | |
| 3.0.0 | 4 / 0 |
v3.0.209
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.208
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.204
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.67
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.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.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.
v3.0.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.