@alfalab/hooks
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package; no provenance is consistent across all versions and is not a risk indicator here. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.17.0 | 2 / 7 | |
| 1.16.0 | 2 / 8 | |
| 1.15.5 | 2 / 8 | |
| 1.15.2 | 2 / 8 | |
| 1.15.1 | 2 / 8 | |
| 1.15.0 | 2 / 8 | |
| 1.14.0 | 2 / 8 | |
| 1.13.1 | 2 / 8 | |
| 1.12.13 | 2 / 8 | |
| 1.12.12 | 2 / 9 |
v1.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (praiz90) than the most recent previously approved version (heymdall) on 2025-02-18, but praiz90 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.13.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (heymdall) than the most recent previously approved version (praiz90) on 2024-12-16, but heymdall is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.12.13
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (heymdall) than the most recent previously approved version (praiz90) on 2024-12-16, but heymdall is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.12.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.