@clipboard-health/eslint-plugin
Clipboard's ESLint Plugin
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 | publisher-changed | AI (provenance): New publisher clipboard_engineering is the org-level account for ClipboardHealth; legitimate maintainer consolidation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): clipboard_engineering is the canonical ClipboardHealth engineering account; stable org-level transition. | ai |
Versions (showing 22 of 325)
| Version | Deps | Published |
|---|---|---|
| 1.3.2 | 2 / 1 | |
| 1.3.1 | 2 / 1 | |
| 1.3.0 | 2 / 1 | |
| 1.2.29 | 2 / 1 | |
| 1.2.28 | 2 / 1 | |
| 1.2.27 | 2 / 1 | |
| 1.2.26 | 2 / 1 | |
| 1.2.25 | 2 / 1 | |
| 1.2.24 | 2 / 1 | |
| 1.2.23 | 2 / 1 | |
| 1.2.22 | 2 / 1 | |
| 1.2.21 | 2 / 1 | |
| 1.2.20 | 2 / 1 | |
| 1.2.19 | 2 / 1 | |
| 1.2.18 | 2 / 1 | |
| 1.2.17 | 2 / 1 | |
| 1.2.16 | 2 / 1 | |
| 1.2.15 | 2 / 1 | |
| 1.2.14 | 2 / 1 | |
| 1.2.13 | 2 / 1 | |
| 1.2.12 | 2 / 1 | |
| 1.2.11 | 2 / 1 |
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.