@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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/esm/en.po.js | AI (source-diff): Generated i18n data file (long line of JSON strings), not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/esm/he.po.js | AI (source-diff): Generated i18n data file (long line of JSON strings), not obfuscated code. | ai | |
| 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 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 7.0.0 | 3 / 8 | |
| 6.5.1 | 3 / 13 | |
| 6.5.0 | 3 / 13 | |
| 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 | |
| 6.0.3 | 3 / 14 | |
| 6.0.2 | 3 / 15 | |
| 6.0.1 | 3 / 15 | |
| 6.0.0 | 4 / 15 |
v7.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.5.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.5.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.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.