react-copy-to-clipboard
Copy-to-clipboard React component
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Long-established package predating provenance tooling; published by original author consistently for ~11 years. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 5.1.1 | 2 / 23 | |
| 5.1.0 | 2 / 29 | |
| 5.0.4 | 2 / 29 | |
| 5.0.3 | 2 / 29 | |
| 5.0.2 | 2 / 29 | |
| 5.0.1 | 2 / 33 | |
| 5.0.0 | 2 / 2 | |
| 4.3.1 | 3 / 1 | |
| 4.3.0 | 1 / 2 | |
| 4.2.3 | 1 / 2 | |
| 4.2.2 | 1 / 1 | |
| 4.2.1 | 1 / 30 | |
| 4.2.0 | 1 / 30 | |
| 4.1.1 | 1 / 30 | |
| 4.1.0 | 1 / 31 | |
| 4.0.2 | 1 / 34 | |
| 4.0.1 | 1 / 34 | |
| 4.0.0 | 1 / 34 | |
| 3.0.4 | 1 / 32 | |
| 3.0.3 | 1 / 32 | |
| 3.0.2 | 1 / 31 | |
| 3.0.1 | 1 / 30 | |
| 3.0.0 | 1 / 30 | |
| 2.0.1 | 1 / 28 | |
| 2.0.0 | 1 / 28 | |
| 1.0.4 | 1 / 26 | |
| 1.0.3 | 1 / 26 | |
| 1.0.2 | 1 / 26 | |
| 1.0.1 | 2 / 23 | |
| 1.0.0 | 2 / 23 |
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nkbt.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nkbt.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.