@alfalab/utils
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
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.20.0 | 2 / 1 | |
| 1.18.2 | 2 / 1 | |
| 1.18.1 | 2 / 1 | |
| 1.18.0 | 2 / 1 | |
| 1.17.1 | 2 / 1 | |
| 1.16.1 | 2 / 1 | |
| 1.16.0 | 2 / 3 |
v1.18.0
2 findingsPackage 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.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
2 findingsPackage 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.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.