@hebcal/leyning
Torah Reading API for Parashat HaShavua and holidays
Supply chain provenance
Status for the latest visible version.
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): Transition from manual publish (mjradwin) to GitHub Actions CI with SLSA provenance; expected and documented by attestation. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 9.6.0 | 2 / 17 | |
| 9.5.6 | 2 / 17 | |
| 9.5.5 | 2 / 16 | |
| 9.5.4 | 2 / 16 | |
| 9.5.3 | 2 / 16 | |
| 9.5.2 | 2 / 16 | |
| 9.5.1 | 2 / 15 | |
| 9.5.0 | 2 / 15 | |
| 9.4.1 | 2 / 15 | |
| 9.4.0 | 3 / 14 | |
| 9.3.0 | 3 / 14 | |
| 9.2.7 | 3 / 14 | |
| 9.2.5 | 3 / 14 | |
| 9.2.4 | 3 / 14 | |
| 9.2.3 | 3 / 14 | |
| 9.2.2 | 3 / 14 | |
| 9.2.1 | 3 / 15 | |
| 9.2.0 | 3 / 15 | |
| 9.1.1 | 3 / 15 | |
| 9.1.0 | 3 / 15 | |
| 9.0.6 | 3 / 15 | |
| 9.0.5 | 3 / 15 | |
| 9.0.4 | 3 / 15 | |
| 9.0.3 | 3 / 17 | |
| 9.0.2 | 3 / 19 | |
| 9.0.1 | 3 / 19 | |
| 9.0.0 | 3 / 20 |
v9.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.5.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.