logzen
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.7.7 | 1 / 9 | |
| 0.7.6 | 1 / 9 | |
| 0.7.5 | 1 / 9 | |
| 0.7.1 | 1 / 9 | |
| 0.7.0 | 1 / 9 | |
| 0.6.2 | 1 / 9 | |
| 0.6.1 | 1 / 9 | |
| 0.6.0 | 1 / 9 | |
| 0.5.0 | 1 / 9 | |
| 0.4.1 | 1 / 9 | |
| 0.4.0 | 1 / 9 | |
| 0.3.10 | 1 / 9 | |
| 0.3.9 | 1 / 12 |
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.