@cloudscape-design/theming-build
This package contains theming-related dependencies for the [Cloudscape Design System](https://cloudscape.design/) React components.
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 | dormant-publish | AI (publish-pattern): Legitimate AWS Cloudscape org package; dormancy likely reflects release cadence, not account takeover. | ai | |
| dependencies | unvetted-dep:postcss-inline-svg | AI (dependencies): postcss-inline-svg is a legitimate PostCSS plugin; stable dependency for this theming build package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Cloudscape Design System library; link-heavy README pointing to official docs is expected, not a phishing indicator. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is declared in dependencies; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 1.0.121 | 13 / 0 | |
| 1.0.120 | 13 / 0 | |
| 1.0.119 | 13 / 0 | |
| 1.0.118 | 13 / 0 | |
| 1.0.117 | 13 / 0 | |
| 1.0.116 | 13 / 0 | |
| 1.0.115 | 13 / 0 | |
| 1.0.114 | 13 / 0 | |
| 1.0.113 | 13 / 0 | |
| 1.0.112 | 13 / 0 | |
| 1.0.111 | 13 / 0 | |
| 1.0.110 | 13 / 0 | |
| 1.0.109 | 13 / 0 | |
| 1.0.108 | 13 / 0 | |
| 1.0.107 | 13 / 0 | |
| 1.0.106 | 13 / 0 | |
| 1.0.105 | 13 / 0 | |
| 1.0.104 | 13 / 0 | |
| 1.0.103 | 13 / 0 | |
| 1.0.102 | 13 / 0 | |
| 1.0.101 | 13 / 0 | |
| 1.0.100 | 13 / 0 | |
| 1.0.99 | 13 / 0 | |
| 1.0.98 | 13 / 0 | |
| 1.0.97 | 13 / 0 | |
| 1.0.96 | 13 / 0 | |
| 1.0.95 | 12 / 0 | |
| 1.0.94 | 12 / 0 | |
| 1.0.93 | 12 / 0 | |
| 1.0.92 | 12 / 0 | |
| 1.0.91 | 12 / 0 | |
| 1.0.90 | 12 / 0 | |
| 1.0.89 | 12 / 0 | |
| 1.0.88 | 12 / 0 | |
| 1.0.87 | 12 / 0 | |
| 1.0.86 | 12 / 0 | |
| 1.0.85 | 12 / 0 | |
| 1.0.84 | 12 / 0 |
v1.0.121
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.120
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.119
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.118
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.117
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.115
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.114
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.113
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.111
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.110
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.108
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.107
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.