@uiw/copy-to-clipboard MIT 20 versions

@uiw/copy-to-clipboard

npm Repository Homepage

Copy to clipboard.

20

Versions

MIT

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

wcjianguiwjs

Keywords

copytextclipboardbrowserclipboard-copyclipboard.js

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/lcov-report/prettify.js	AI (source-diff): Known google-code-prettify library bundled in lcov coverage report, not malicious obfuscation.	ai	2026/07/24
source-diff	source-size-tripled	AI (source-diff): Size increase explained by vendored lcov-report/prettify.js addition.	ai	2026/07/24

Versions (showing 20 of 20)

Version	Deps	Published
1.0.21	0 / 0	2026-05-21
1.0.20	0 / 0	2026-01-24
1.0.19	0 / 0	2025-12-12
1.0.18	0 / 0	2025-12-12
1.0.17	0 / 0	2024-03-26
1.0.16	0 / 0	2023-10-04
1.0.15	0 / 5	2023-07-07
1.0.14	0 / 5	2023-04-12
1.0.13	0 / 5	2023-04-12
1.0.12	0 / 5	2021-08-29
1.0.11	0 / 4	2020-06-28
1.0.10	0 / 4	2019-05-20
1.0.8	0 / 4	2019-05-20
1.0.7	0 / 4	2019-01-24
1.0.6	0 / 4	2019-01-10
1.0.5	0 / 4	2018-09-06
1.0.4	0 / 4	2018-09-06
1.0.3	0 / 3	2018-09-06
1.0.1	0 / 3	2018-09-06
1.0.0	0 / 5	2018-09-05

v1.0.17

2 findings

HIGH New obfuscated file: dist/lcov-report/prettify.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.0.16

2 findings

HIGH New obfuscated file: dist/lcov-report/prettify.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.0.15

1 finding

LOW No provenance attestation provenance

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

v1.0.14

1 finding

LOW No provenance attestation provenance

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

v1.0.13

1 finding

LOW No provenance attestation provenance

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

v1.0.12

1 finding

LOW No provenance attestation provenance

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

v1.0.11

1 finding

LOW No provenance attestation provenance

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

v1.0.10

1 finding

LOW No provenance attestation provenance

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

v1.0.8

1 finding

LOW No provenance attestation provenance

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

v1.0.7

1 finding

LOW No provenance attestation provenance

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

v1.0.6

1 finding

LOW No provenance attestation provenance

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

v1.0.5

1 finding

LOW No provenance attestation provenance

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

v1.0.4

1 finding

LOW No provenance attestation provenance

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

v1.0.3

1 finding

LOW No provenance attestation provenance

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

v1.0.1

1 finding

LOW No provenance attestation provenance

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

v1.0.0

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.