@entur/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 |
|---|---|---|
| 0.13.6 | 1 / 9 | |
| 0.13.5 | 1 / 9 | |
| 0.13.4 | 1 / 9 | |
| 0.13.3 | 1 / 9 | |
| 0.13.2 | 1 / 10 | |
| 0.13.1 | 1 / 10 | |
| 0.13.0 | 1 / 10 | |
| 0.12.5 | 1 / 10 | |
| 0.12.4 | 1 / 10 | |
| 0.12.3 | 1 / 1 | |
| 0.12.2 | 1 / 1 | |
| 0.12.1 | 1 / 0 | |
| 0.12.0 | 1 / 0 | |
| 0.11.2 | 1 / 0 |
v0.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.