@bolttech/atoms-checkbox
A simple React checkbox 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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.24.0 | 4 / 0 | |
| 0.23.5 | 4 / 0 | |
| 0.23.4 | 4 / 0 | |
| 0.23.3 | 4 / 0 | |
| 0.23.1 | 4 / 0 | |
| 0.23.0 | 4 / 0 | |
| 0.22.1 | 4 / 0 | |
| 0.22.0 | 4 / 0 | |
| 0.21.3 | 4 / 0 | |
| 0.21.2 | 4 / 0 | |
| 0.21.1 | 4 / 0 | |
| 0.21.0 | 6 / 0 | |
| 0.20.3 | 6 / 0 | |
| 0.20.2 | 6 / 0 | |
| 0.20.1 | 6 / 0 | |
| 0.20.0 | 6 / 0 | |
| 0.19.0 | 6 / 0 | |
| 0.18.0 | 6 / 0 | |
| 0.17.1 | 6 / 0 |
v0.24.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andsfranbolt) than the most recent previously approved version (silas.silva.bolttech) on 2026-06-30, but andsfranbolt 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.
v0.21.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andsfranbolt) than the most recent previously approved version (lukaspiccinibt) on 2024-12-30, but andsfranbolt 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.
v0.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (lukaspiccinibt) than the most recent previously approved version (danielkhalebbatista) on 2024-09-04, but lukaspiccinibt 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.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (lukaspiccinibt) than the most recent previously approved version (danielkhalebbatista) on 2024-07-24, but lukaspiccinibt 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.
v0.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.