@bolttech/molecules-calendar
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established @bolttech org package; no provenance is consistent across all versions of this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.29.6 | 6 / 0 | |
| 0.29.5 | 6 / 0 | |
| 0.29.4 | 6 / 0 | |
| 0.29.3 | 6 / 0 | |
| 0.29.2 | 6 / 0 | |
| 0.29.0 | 6 / 0 | |
| 0.27.3 | 6 / 0 | |
| 0.27.2 | 6 / 0 | |
| 0.27.1 | 6 / 0 | |
| 0.27.0 | 6 / 0 | |
| 0.26.0 | 8 / 0 | |
| 0.25.2 | 8 / 0 | |
| 0.25.1 | 8 / 0 | |
| 0.25.0 | 8 / 0 | |
| 0.24.0 | 8 / 0 |
v0.29.6
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (bruno.gomes) than the most recent previously approved version (silas.silva.bolttech) on 2026-07-02, but bruno.gomes 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.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.2
2 findings[Accepted risk] Package 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 2025-02-18, 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.25.1
2 findings[Accepted risk] Package 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-11-20, 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.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.