@cloudscape-design/browser-test-tools Apache-2.0 39 versions

@cloudscape-design/browser-test-tools

npm Repository Homepage

This package contains the source code for tools used for building and testing the React components for the [Cloudscape Design System](https://cloudscape.design/).

39

Versions

Apache-2.0

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

awsui-ci

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	2026/05/03
semgrep	semgrep:child-process-import	AI (semgrep): chrome-launcher.js legitimately uses child_process to launch Chrome; expected for this browser test tool.	ai	2026/04/29
semgrep	semgrep:base64-decode	AI (semgrep): Base64 decode is used to parse PNG screenshots; benign image-processing pattern for this package.	ai	2026/04/29
bogus-package	bogus-package	AI (bogus-package): Cloudscape Design is an established AWS UI library; README link dump signal is a false positive.	ai	2026/04/29
phantom-deps	phantom-dep:@types/pngjs	AI (phantom-deps): @types/pngjs is a type declaration package; not directly imported at runtime by convention.	ai	2026/04/29
phantom-deps	phantom-dep:@wdio/globals	AI (phantom-deps): @wdio/globals is loaded by the WebdriverIO framework via config, not direct import.	ai	2026/04/29

Versions (showing 39 of 39)

Version	Deps	Published
3.0.129	11 / 21	2026-06-05
3.0.128	11 / 21	2026-06-04
3.0.127	11 / 21	2026-05-22
3.0.126	11 / 21	2026-05-22
3.0.125	11 / 21	2026-05-14
3.0.124	11 / 21	2026-05-12
3.0.123	11 / 21	2026-05-11
3.0.122	11 / 21	2026-04-27
3.0.121	11 / 21	2026-04-16
3.0.120	11 / 21	2026-04-14
3.0.119	11 / 21	2026-04-10
3.0.118	11 / 21	2026-04-08
3.0.117	11 / 21	2026-04-01
3.0.116	11 / 21	2026-03-26
3.0.115	11 / 21	2026-03-26
3.0.114	11 / 21	2026-03-25
3.0.113	11 / 21	2026-03-25
3.0.112	11 / 21	2026-03-05
3.0.111	11 / 21	2026-03-04
3.0.110	11 / 21	2026-03-03
3.0.109	11 / 21	2026-03-01
3.0.108	11 / 21	2026-02-24
3.0.107	11 / 21	2026-02-21
3.0.106	11 / 21	2026-02-14
3.0.105	11 / 21	2026-01-23
3.0.104	11 / 20	2026-01-13
3.0.103	11 / 20	2025-12-10
3.0.102	11 / 19	2025-11-18
3.0.101	11 / 19	2025-11-04
3.0.100	11 / 19	2025-10-23
3.0.99	11 / 19	2025-09-11
3.0.98	11 / 19	2025-07-28
3.0.97	11 / 19	2025-07-24
3.0.96	11 / 19	2025-06-18
3.0.95	11 / 19	2025-06-10
3.0.94	11 / 19	2025-05-31
3.0.93	11 / 19	2025-05-15
3.0.92	11 / 19	2025-05-13
3.0.91	11 / 19	2025-05-07

v3.0.129

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.128

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.127

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.126

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.125

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.124

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.123

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.121

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.120

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.119

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.117

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.115

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.114

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.113

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.112

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.111

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.110

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.109

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.108

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.107

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.106

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.105

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.104

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.103

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.102

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.101

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.100

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.99

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.98

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.97

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.96

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.93

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.91

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.