@xapp/arachne-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 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.10.7 | 1 / 14 | |
| 1.10.1 | 1 / 14 | |
| 1.10.0 | 1 / 14 | |
| 1.9.2 | 1 / 14 | |
| 1.9.1 | 1 / 14 | |
| 1.9.0 | 1 / 14 | |
| 1.8.13 | 1 / 14 | |
| 1.8.12 | 1 / 14 | |
| 1.8.7 | 1 / 14 | |
| 1.8.3 | 1 / 14 | |
| 1.8.2 | 1 / 14 | |
| 1.8.0 | 1 / 14 | |
| 1.7.5 | 1 / 14 | |
| 1.7.4 | 1 / 14 |
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.12
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.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. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.