@clipboard-health/config
Type-safe static configuration management: a pure function to resolve, validate against a Zod schema, and freeze configuration values.
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 the consolidated ClipboardHealth engineering account with 193 approved packages; transition appears legitimate. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same org account consolidation; stable pattern for this package going forward. | ai |
Versions (showing 35 of 335)
| Version | Deps | Published |
|---|---|---|
| 1.4.3 | 4 / 2 | |
| 1.4.2 | 4 / 2 | |
| 1.4.1 | 4 / 2 | |
| 1.4.0 | 4 / 2 | |
| 1.3.11 | 4 / 2 | |
| 1.3.10 | 4 / 2 | |
| 1.3.9 | 4 / 2 | |
| 1.3.8 | 4 / 2 | |
| 1.3.7 | 4 / 2 | |
| 1.3.6 | 4 / 2 | |
| 1.3.5 | 4 / 2 | |
| 1.3.4 | 4 / 2 | |
| 1.3.3 | 4 / 2 | |
| 1.3.2 | 4 / 2 | |
| 1.3.1 | 4 / 2 | |
| 1.3.0 | 4 / 2 | |
| 1.2.29 | 4 / 2 | |
| 1.2.28 | 4 / 2 | |
| 1.2.27 | 4 / 2 | |
| 1.2.26 | 4 / 2 | |
| 1.2.25 | 4 / 2 | |
| 1.2.24 | 4 / 2 | |
| 1.2.23 | 4 / 2 | |
| 1.2.22 | 4 / 2 | |
| 1.2.21 | 4 / 2 | |
| 1.2.20 | 4 / 2 | |
| 1.2.19 | 4 / 2 | |
| 1.2.18 | 4 / 2 | |
| 1.2.17 | 4 / 2 | |
| 1.2.16 | 4 / 2 | |
| 1.2.15 | 4 / 2 | |
| 1.2.14 | 4 / 2 | |
| 1.2.13 | 4 / 2 | |
| 1.2.12 | 4 / 2 | |
| 1.2.11 | 4 / 2 |
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.