@websolutespa/bom-mixer-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
Keywords
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 0 / 14 | |
| 3.0.0 | 0 / 14 | |
| 2.0.0 | 0 / 17 | |
| 1.9.4 | 0 / 17 | |
| 1.9.3 | 0 / 17 | |
| 1.9.2 | 0 / 17 | |
| 1.9.1 | 0 / 17 | |
| 1.9.0 | 0 / 17 | |
| 1.8.11 | 0 / 15 | |
| 1.8.10 | 0 / 15 | |
| 1.8.9 | 0 / 15 | |
| 1.8.8 | 0 / 15 | |
| 1.8.7 | 0 / 15 | |
| 1.8.6 | 0 / 15 | |
| 1.8.5 | 0 / 15 | |
| 1.8.4 | 0 / 15 | |
| 1.8.3 | 0 / 15 | |
| 1.8.2 | 0 / 15 | |
| 1.8.1 | 0 / 15 |
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.