@bimetal/calendar-data
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@bimetal/calendar-core | AI (dependencies): Sibling package in same monorepo/scope, not third-party. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Internal refactor splitting core into calendar-core within trusted org. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.35.0 | 2 / 1 | |
| 0.34.0 | 2 / 1 | |
| 0.32.0 | 2 / 1 | |
| 0.30.0 | 2 / 1 | |
| 0.29.0 | 2 / 1 | |
| 0.17.0 | 2 / 1 | |
| 0.16.7 | 2 / 1 | |
| 0.16.1 | 2 / 1 | |
| 0.15.10 | 2 / 1 | |
| 0.15.3 | 2 / 1 | |
| 0.14.1 | 2 / 1 | |
| 0.13.6 | 2 / 1 | |
| 0.13.5 | 2 / 1 | |
| 0.13.4 | 2 / 1 | |
| 0.13.3 | 2 / 1 | |
| 0.13.2 | 2 / 1 | |
| 0.13.0 | 2 / 1 |
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.