← Home

clipboard

npm Repository Homepage

Modern copy to clipboard. No Flash. Just 2kb

12
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

zenorochaobetomunizvitormalencar

Keywords

clipboardcopycut

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:select AI (dependencies): select is a long-standing, well-known utility dependency of clipboard.js; stable and expected for this package. ai
dependencies unvetted-dep:tiny-emitter AI (dependencies): tiny-emitter is a long-standing, well-known utility dependency of clipboard.js; stable and expected for this package. ai
dependencies unvetted-dep:good-listener AI (dependencies): good-listener is a long-standing, well-known utility dependency of clipboard.js; stable and expected for this package. ai

Versions (showing 12 of 12)

Version Deps Published
2.0.11 3 / 25
2.0.10 3 / 25
2.0.9 3 / 25
2.0.8 3 / 25
2.0.7 3 / 25
2.0.6 3 / 16
2.0.5 3 / 16
2.0.4 3 / 18
2.0.3 3 / 18
2.0.2 3 / 18
2.0.1 3 / 17
2.0.0 3 / 17

v2.0.10

1 finding
LOW No provenance attestation provenance

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

v2.0.9

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: vitormalencar → obetomuniz (on 2022-01-28, known maintainer) provenance

This version was published by a different npm account (obetomuniz) than the most recent previously approved version (vitormalencar) on 2022-01-28, but obetomuniz is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.0.7

2 findings
MEDIUM Publisher changed: zenorocha → vitormalencar (on 2021-03-06, unremoved on npm for 1961d) provenance

This version was published by a different npm account (vitormalencar) than the most recent previously approved version (zenorocha) on 2021-03-06. It has since remained available on npm for 1961 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v2.0.6

1 finding
LOW No provenance attestation provenance

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

v2.0.5

1 finding
LOW No provenance attestation provenance

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

v2.0.4

1 finding
LOW No provenance attestation provenance

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

v2.0.3

1 finding
LOW No provenance attestation provenance

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

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.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.