@hebcal/icalendar
Jewish holidays and Hebrew calendar as iCalendar RFC 2445
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit TypeScript runtime dep; stable false positive for this package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 7.0.0 | 4 / 6 | |
| 6.3.8 | 5 / 8 | |
| 6.3.7 | 5 / 8 | |
| 6.3.6 | 5 / 8 | |
| 6.3.5 | 5 / 8 | |
| 6.3.4 | 5 / 8 | |
| 6.3.3 | 5 / 8 | |
| 6.3.2 | 5 / 8 | |
| 6.3.1 | 5 / 8 | |
| 6.3.0 | 5 / 9 | |
| 6.2.1 | 5 / 9 | |
| 6.2.0 | 5 / 9 | |
| 6.1.4 | 5 / 9 | |
| 6.1.3 | 5 / 9 | |
| 6.1.2 | 5 / 9 | |
| 6.1.1 | 5 / 12 | |
| 6.1.0 | 5 / 12 | |
| 6.0.2 | 4 / 13 | |
| 6.0.1 | 5 / 13 |
v7.0.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (mjradwin) on 2026-07-27, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v6.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.