@clipboard-health/eslint-config
Our ESLint configuration.
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): clipboard_engineering is a ClipboardHealth org account with strong approval history; transition appears legitimate. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer is a ClipboardHealth org account; consistent with internal team account consolidation. | ai |
Versions (showing 51 of 323)
| Version | Deps | Published |
|---|---|---|
| 7.7.24 | 0 / 0 | |
| 7.7.23 | 0 / 0 | |
| 7.7.22 | 0 / 0 | |
| 7.7.21 | 0 / 0 | |
| 7.7.20 | 0 / 0 | |
| 7.7.19 | 0 / 0 | |
| 7.7.18 | 0 / 0 | |
| 7.7.17 | 0 / 0 | |
| 7.7.16 | 0 / 0 | |
| 7.7.15 | 0 / 0 | |
| 7.7.14 | 0 / 0 | |
| 7.7.13 | 0 / 0 | |
| 7.7.12 | 0 / 0 | |
| 7.7.11 | 0 / 0 | |
| 7.7.10 | 0 / 0 | |
| 7.7.9 | 0 / 0 | |
| 7.7.8 | 0 / 0 | |
| 7.7.7 | 0 / 0 | |
| 7.7.6 | 0 / 0 | |
| 7.7.5 | 0 / 0 | |
| 7.7.4 | 0 / 0 | |
| 7.7.3 | 0 / 0 | |
| 7.7.2 | 0 / 0 | |
| 7.7.1 | 0 / 0 | |
| 7.7.0 | 0 / 0 | |
| 7.6.4 | 0 / 0 | |
| 7.6.3 | 0 / 0 | |
| 7.6.2 | 0 / 0 | |
| 7.6.1 | 0 / 0 | |
| 7.5.0 | 0 / 0 | |
| 7.4.1 | 0 / 0 | |
| 7.4.0 | 0 / 0 | |
| 7.3.39 | 0 / 0 | |
| 7.3.38 | 0 / 0 | |
| 7.3.37 | 0 / 0 | |
| 7.3.36 | 0 / 0 | |
| 7.3.35 | 0 / 0 | |
| 7.3.34 | 0 / 0 | |
| 7.3.33 | 0 / 0 | |
| 7.3.32 | 0 / 0 | |
| 7.3.31 | 0 / 0 | |
| 7.3.30 | 0 / 0 | |
| 7.3.29 | 0 / 0 | |
| 7.3.28 | 0 / 0 | |
| 7.3.27 | 0 / 0 | |
| 7.3.26 | 0 / 0 | |
| 7.3.25 | 0 / 0 | |
| 7.3.24 | 0 / 0 | |
| 7.3.23 | 0 / 0 | |
| 7.3.22 | 0 / 0 | |
| 7.3.21 | 0 / 0 |
v7.7.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.4
2 findingsThis version was published by a different npm account than previous versions on 2026-05-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.