@cloudscape-design/browser-test-tools
This package contains the source code for tools used for building and testing the React components for the [Cloudscape Design System](https://cloudscape.design/).
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@types/pngjs | AI (dependencies): Type-only dependency for pngjs; no runtime risk. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): chrome-launcher.js legitimately uses child_process to launch Chrome; expected for this browser test tool. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is used to parse PNG screenshots; benign image-processing pattern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Cloudscape Design is an established AWS UI library; README link dump signal is a false positive. | ai | |
| phantom-deps | phantom-dep:@types/pngjs | AI (phantom-deps): @types/pngjs is a type declaration package; not directly imported at runtime by convention. | ai | |
| phantom-deps | phantom-dep:@wdio/globals | AI (phantom-deps): @wdio/globals is loaded by the WebdriverIO framework via config, not direct import. | ai |
Versions (showing 40 of 140)
| Version | Deps | Published |
|---|---|---|
| 3.0.39 | 8 / 0 | |
| 3.0.38 | 8 / 0 | |
| 3.0.37 | 8 / 0 | |
| 3.0.36 | 8 / 0 | |
| 3.0.35 | 8 / 0 | |
| 3.0.34 | 8 / 0 | |
| 3.0.33 | 8 / 0 | |
| 3.0.32 | 8 / 0 | |
| 3.0.31 | 8 / 0 | |
| 3.0.30 | 8 / 0 | |
| 3.0.29 | 8 / 0 | |
| 3.0.28 | 8 / 0 | |
| 3.0.27 | 8 / 0 | |
| 3.0.26 | 8 / 0 | |
| 3.0.25 | 8 / 0 | |
| 3.0.24 | 8 / 0 | |
| 3.0.23 | 8 / 0 | |
| 3.0.22 | 8 / 0 | |
| 3.0.21 | 8 / 0 | |
| 3.0.20 | 8 / 0 | |
| 3.0.19 | 8 / 0 | |
| 3.0.18 | 8 / 0 | |
| 3.0.17 | 8 / 0 | |
| 3.0.16 | 8 / 0 | |
| 3.0.15 | 8 / 0 | |
| 3.0.14 | 8 / 0 | |
| 3.0.13 | 8 / 0 | |
| 3.0.12 | 8 / 0 | |
| 3.0.11 | 8 / 0 | |
| 3.0.10 | 8 / 0 | |
| 3.0.9 | 8 / 0 | |
| 3.0.8 | 8 / 0 | |
| 3.0.7 | 8 / 0 | |
| 3.0.6 | 8 / 0 | |
| 3.0.5 | 8 / 0 | |
| 3.0.4 | 8 / 0 | |
| 3.0.3 | 8 / 0 | |
| 3.0.2 | 8 / 0 | |
| 3.0.1 | 8 / 0 | |
| 3.0.0 | 8 / 0 |
v3.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.