@or-sdk/library-source
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 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.4.3 | 2 / 2 | |
| 0.4.2 | 2 / 2 | |
| 0.4.1 | 2 / 2 | |
| 0.4.0 | 2 / 2 | |
| 0.3.10 | 2 / 2 | |
| 0.3.9 | 2 / 2 | |
| 0.3.8 | 2 / 2 | |
| 0.3.7 | 2 / 2 | |
| 0.3.6 | 2 / 2 | |
| 0.3.5 | 2 / 2 | |
| 0.3.4 | 2 / 2 | |
| 0.3.3 | 2 / 2 | |
| 0.3.2 | 2 / 2 | |
| 0.3.1 | 2 / 2 | |
| 0.3.0 | 2 / 2 | |
| 0.2.19 | 2 / 2 | |
| 0.2.18 | 2 / 2 | |
| 0.2.17 | 2 / 2 | |
| 0.2.16 | 2 / 2 | |
| 0.2.15 | 2 / 2 | |
| 0.2.14 | 2 / 2 | |
| 0.2.13 | 2 / 2 |
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.