@leather.io/models
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 66 of 66)
| Version | Deps | Published |
|---|---|---|
| 0.56.0 | 3 / 5 | |
| 0.55.0 | 3 / 5 | |
| 0.54.0 | 3 / 5 | |
| 0.53.0 | 3 / 5 | |
| 0.52.0 | 3 / 5 | |
| 0.51.0 | 3 / 5 | |
| 0.50.2 | 3 / 5 | |
| 0.50.1 | 3 / 5 | |
| 0.50.0 | 3 / 5 | |
| 0.49.0 | 3 / 5 | |
| 0.48.0 | 3 / 5 | |
| 0.47.0 | 3 / 5 | |
| 0.46.0 | 3 / 5 | |
| 0.45.0 | 3 / 5 | |
| 0.44.1 | 3 / 5 | |
| 0.44.0 | 3 / 5 | |
| 0.43.0 | 3 / 5 | |
| 0.42.0 | 3 / 5 | |
| 0.41.0 | 3 / 5 | |
| 0.40.0 | 3 / 5 | |
| 0.39.1 | 3 / 5 | |
| 0.39.0 | 3 / 5 | |
| 0.37.0 | 3 / 5 | |
| 0.36.0 | 3 / 5 | |
| 0.35.0 | 3 / 5 | |
| 0.34.0 | 3 / 5 | |
| 0.33.0 | 3 / 5 | |
| 0.32.1 | 3 / 5 | |
| 0.32.0 | 3 / 5 | |
| 0.31.0 | 3 / 5 | |
| 0.30.0 | 3 / 5 | |
| 0.29.0 | 3 / 5 | |
| 0.28.0 | 3 / 5 | |
| 0.27.0 | 3 / 5 | |
| 0.26.3 | 3 / 5 | |
| 0.26.2 | 3 / 5 | |
| 0.26.1 | 3 / 5 | |
| 0.26.0 | 3 / 5 | |
| 0.25.1 | 3 / 5 | |
| 0.25.0 | 3 / 5 | |
| 0.24.3 | 3 / 5 | |
| 0.24.2 | 3 / 7 | |
| 0.24.1 | 3 / 7 | |
| 0.24.0 | 3 / 7 | |
| 0.23.0 | 3 / 7 | |
| 0.22.0 | 3 / 7 | |
| 0.21.0 | 3 / 7 | |
| 0.20.0 | 3 / 7 | |
| 0.19.1 | 3 / 7 | |
| 0.19.0 | 3 / 7 | |
| 0.18.3 | 3 / 7 | |
| 0.18.2 | 3 / 7 | |
| 0.18.1 | 3 / 7 | |
| 0.18.0 | 3 / 7 | |
| 0.17.0 | 3 / 7 | |
| 0.16.0 | 3 / 7 | |
| 0.15.0 | 3 / 7 | |
| 0.14.0 | 3 / 7 | |
| 0.13.0 | 3 / 7 | |
| 0.12.1 | 3 / 7 | |
| 0.12.0 | 3 / 7 | |
| 0.11.1 | 3 / 7 | |
| 0.11.0 | 3 / 7 | |
| 0.10.2 | 2 / 7 | |
| 0.10.1 | 2 / 7 | |
| 0.10.0 | 2 / 7 |
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.