@hebcal/rest-api
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 mjradwin to GitHub Actions CI is consistent with automation; SLSA attestation confirms legitimate CI publish. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI-attested publish with no code/dep changes; no malicious indicators present. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 139 published versions; lack of provenance is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 6.4.9 | 3 / 12 | |
| 6.4.8 | 3 / 12 | |
| 6.4.7 | 3 / 12 | |
| 6.4.6 | 3 / 12 | |
| 6.4.5 | 3 / 12 | |
| 6.4.3 | 3 / 12 | |
| 6.4.2 | 3 / 12 | |
| 6.4.1 | 3 / 12 | |
| 6.4.0 | 3 / 12 | |
| 6.3.0 | 3 / 12 | |
| 6.2.0 | 3 / 11 | |
| 6.1.7 | 3 / 11 | |
| 6.1.6 | 3 / 11 | |
| 6.1.5 | 3 / 11 | |
| 6.1.4 | 3 / 12 |
v6.4.9
2 findingsThis version was published by a different npm account than previous versions on 2026-05-26. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.