@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, 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 | 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 100 of 135)
| Version | Deps | Published |
|---|---|---|
| 1.0.134 | 13 / 0 | |
| 1.0.133 | 13 / 0 | |
| 1.0.132 | 13 / 0 | |
| 1.0.131 | 13 / 0 | |
| 1.0.130 | 13 / 0 | |
| 1.0.129 | 13 / 0 | |
| 1.0.128 | 13 / 0 | |
| 1.0.127 | 13 / 0 | |
| 1.0.126 | 13 / 0 | |
| 1.0.125 | 13 / 0 | |
| 1.0.124 | 13 / 0 | |
| 1.0.123 | 13 / 0 | |
| 1.0.122 | 13 / 0 | |
| 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 | |
| 1.0.83 | 12 / 0 | |
| 1.0.82 | 12 / 0 | |
| 1.0.81 | 12 / 0 | |
| 1.0.80 | 12 / 0 | |
| 1.0.79 | 12 / 0 | |
| 1.0.78 | 12 / 0 | |
| 1.0.77 | 12 / 0 | |
| 1.0.76 | 12 / 0 | |
| 1.0.75 | 12 / 0 | |
| 1.0.74 | 12 / 0 | |
| 1.0.73 | 12 / 0 | |
| 1.0.72 | 12 / 0 | |
| 1.0.71 | 12 / 0 | |
| 1.0.70 | 12 / 0 | |
| 1.0.69 | 12 / 0 | |
| 1.0.68 | 12 / 0 | |
| 1.0.67 | 12 / 0 | |
| 1.0.66 | 12 / 0 | |
| 1.0.65 | 12 / 0 | |
| 1.0.64 | 12 / 0 | |
| 1.0.63 | 12 / 0 | |
| 1.0.62 | 12 / 0 | |
| 1.0.61 | 12 / 0 | |
| 1.0.60 | 12 / 0 | |
| 1.0.59 | 12 / 0 | |
| 1.0.58 | 12 / 0 | |
| 1.0.57 | 12 / 0 | |
| 1.0.56 | 12 / 0 | |
| 1.0.55 | 12 / 0 | |
| 1.0.54 | 12 / 0 | |
| 1.0.53 | 12 / 0 | |
| 1.0.52 | 12 / 0 | |
| 1.0.51 | 12 / 0 | |
| 1.0.50 | 12 / 0 | |
| 1.0.49 | 12 / 0 | |
| 1.0.48 | 13 / 0 | |
| 1.0.47 | 13 / 0 | |
| 1.0.46 | 13 / 0 | |
| 1.0.45 | 13 / 0 | |
| 1.0.44 | 13 / 0 | |
| 1.0.43 | 13 / 0 | |
| 1.0.42 | 13 / 0 | |
| 1.0.41 | 13 / 0 | |
| 1.0.40 | 13 / 0 | |
| 1.0.39 | 13 / 0 | |
| 1.0.38 | 13 / 0 | |
| 1.0.37 | 13 / 0 | |
| 1.0.36 | 13 / 0 | |
| 1.0.35 | 13 / 0 |
v1.0.134
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.133
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.132
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.131
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.130
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.129
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.128
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.127
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.126
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.125
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.124
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.123
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.