@or-sdk/adapters
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 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 0.3.5 | 3 / 2 | |
| 0.3.4 | 3 / 2 | |
| 0.3.3 | 3 / 2 | |
| 0.3.2 | 3 / 2 | |
| 0.3.1 | 3 / 2 | |
| 0.3.0 | 3 / 2 | |
| 0.2.51 | 3 / 2 | |
| 0.2.50 | 3 / 2 | |
| 0.2.49 | 3 / 2 | |
| 0.2.48 | 3 / 2 | |
| 0.2.47 | 3 / 2 | |
| 0.2.46 | 3 / 2 | |
| 0.2.45 | 3 / 2 | |
| 0.2.44 | 3 / 2 | |
| 0.2.43 | 3 / 2 | |
| 0.2.42 | 3 / 2 | |
| 0.2.41 | 3 / 2 | |
| 0.2.40 | 3 / 2 | |
| 0.2.39 | 3 / 2 | |
| 0.2.38 | 3 / 2 | |
| 0.2.37 | 3 / 2 | |
| 0.2.36 | 3 / 2 | |
| 0.2.35 | 3 / 2 | |
| 0.2.34 | 3 / 2 | |
| 0.2.33 | 3 / 2 | |
| 0.2.32 | 3 / 2 | |
| 0.2.31 | 3 / 2 | |
| 0.2.30 | 3 / 2 | |
| 0.2.29 | 3 / 2 | |
| 0.2.28 | 3 / 2 | |
| 0.2.27 | 3 / 2 | |
| 0.2.26 | 3 / 2 | |
| 0.2.25 | 3 / 2 | |
| 0.2.24 | 3 / 2 | |
| 0.2.23 | 3 / 2 |
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.