@cloudscape-design/code-view
This package contains the source code of the Code View component in the [Cloudscape Design System](https://cloudscape.design/). For more information about the code view component, see [the documentation](https://cloudscape.design/components/code-view/).
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; no runtime impact, consistent pattern across Cloudscape packages. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): AWS CI publisher with strong track record; dormancy reflects normal release cadence for this design system component. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is from generated theming/token build artifacts, consistent with Cloudscape design-system release patterns. | ai | |
| dependencies | unvetted-dep:ace-code | AI (dependencies): ace-code is the expected syntax highlighting engine for a code-view component; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@cloudscape-design/component-toolkit | AI (dependencies): First-party AWS Cloudscape toolkit dependency; expected across all Cloudscape packages. | ai | |
| provenance | no-provenance | AI (provenance): AWS Cloudscape org package; no provenance is consistent across all their releases. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 3.0.134 | 3 / 57 | |
| 3.0.132 | 3 / 57 | |
| 3.0.129 | 3 / 57 | |
| 3.0.128 | 3 / 57 | |
| 3.0.127 | 3 / 57 | |
| 3.0.126 | 3 / 57 | |
| 3.0.125 | 3 / 57 | |
| 3.0.124 | 3 / 57 | |
| 3.0.122 | 3 / 57 | |
| 3.0.121 | 3 / 57 | |
| 3.0.120 | 3 / 57 | |
| 3.0.119 | 3 / 57 | |
| 3.0.118 | 3 / 57 | |
| 3.0.117 | 3 / 57 | |
| 3.0.116 | 3 / 57 | |
| 3.0.114 | 3 / 57 | |
| 3.0.113 | 3 / 57 | |
| 3.0.112 | 3 / 57 | |
| 3.0.111 | 3 / 57 | |
| 3.0.109 | 3 / 57 | |
| 3.0.105 | 3 / 57 | |
| 3.0.104 | 3 / 57 | |
| 3.0.100 | 3 / 57 | |
| 3.0.95 | 3 / 57 | |
| 3.0.94 | 3 / 57 | |
| 3.0.92 | 3 / 57 | |
| 3.0.89 | 3 / 57 | |
| 3.0.87 | 3 / 57 | |
| 3.0.86 | 3 / 57 | |
| 3.0.84 | 3 / 57 | |
| 3.0.82 | 3 / 57 | |
| 3.0.81 | 3 / 57 | |
| 3.0.80 | 3 / 57 | |
| 3.0.79 | 3 / 57 | |
| 3.0.78 | 3 / 57 | |
| 3.0.77 | 3 / 57 | |
| 3.0.76 | 3 / 57 | |
| 3.0.71 | 3 / 57 | |
| 3.0.70 | 3 / 57 | |
| 3.0.66 | 3 / 55 | |
| 3.0.65 | 3 / 55 | |
| 3.0.62 | 3 / 55 | |
| 3.0.61 | 3 / 55 | |
| 3.0.56 | 3 / 55 | |
| 3.0.55 | 3 / 55 | |
| 3.0.54 | 3 / 0 | |
| 3.0.53 | 3 / 0 |
v3.0.134
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.129
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. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.126
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.125
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.122
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.121
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.120
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.119
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.118
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.117
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.116
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.114
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.113
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.112
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.111
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.105
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.104
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.100
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.95
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.94
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.92
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.89
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.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.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.
v3.0.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.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.
v3.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.
v3.0.78
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.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.61
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. Only ~12% of npm packages have provenance, so this is common but not ideal.