copy-to-clipboard
Copy stuff into clipboard using JS with fallbacks
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Version 0.0.0 is the legitimate original seed release from ~11 years ago by the established maintainer sudodoki; not a malicious throwaway package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Signals reflect an early stub release from 2014-era npm practices. Package has 27 versions, 6 approved dependents, and a clean publisher history — not spam or low-value. | ai | |
| provenance | no-provenance | AI (provenance): Established package with a known GitHub repo; lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 4.0.2 | 0 / 9 | |
| 4.0.1 | 0 / 9 | |
| 4.0.0 | 0 / 9 | |
| 3.3.3 | 1 / 7 | |
| 3.3.2 | 1 / 7 | |
| 3.3.1 | 1 / 5 | |
| 3.3.0 | 1 / 5 | |
| 3.2.1 | 1 / 5 | |
| 3.2.0 | 1 / 5 | |
| 3.1.0 | 1 / 5 | |
| 3.0.9 | 1 / 4 | |
| 3.0.8 | 1 / 4 | |
| 3.0.7 | 1 / 4 | |
| 3.0.6 | 1 / 4 | |
| 3.0.5 | 1 / 4 | |
| 3.0.4 | 1 / 4 | |
| 3.0.3 | 1 / 4 | |
| 3.0.2 | 1 / 0 | |
| 3.0.1 | 1 / 0 | |
| 3.0.0 | 1 / 0 | |
| 2.1.0 | 1 / 0 | |
| 2.0.0 | 1 / 0 | |
| 1.1.1 | 1 / 0 | |
| 1.1.0 | 1 / 0 | |
| 1.0.4 | 1 / 0 | |
| 1.0.2 | 0 / 0 | |
| 1.0.1 | 0 / 0 | |
| 1.0.0 | 0 / 0 | |
| 0.0.0 | 0 / 0 |
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.