@or-sdk/apps
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 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 1.2.5 | 2 / 2 | |
| 1.2.4 | 2 / 2 | |
| 1.2.3 | 2 / 2 | |
| 1.2.2 | 2 / 2 | |
| 1.2.1 | 2 / 2 | |
| 1.2.0 | 2 / 2 | |
| 1.1.30 | 2 / 2 | |
| 1.1.29 | 2 / 2 | |
| 1.1.28 | 2 / 2 | |
| 1.1.27 | 2 / 2 | |
| 1.1.26 | 2 / 2 | |
| 1.1.25 | 2 / 2 | |
| 1.1.24 | 2 / 2 | |
| 1.1.23 | 2 / 2 | |
| 1.1.22 | 2 / 2 | |
| 1.1.21 | 2 / 2 | |
| 1.1.20 | 2 / 2 | |
| 1.1.19 | 2 / 2 | |
| 1.1.18 | 2 / 2 | |
| 1.1.17 | 2 / 2 | |
| 1.1.16 | 2 / 2 | |
| 1.1.15 | 2 / 2 | |
| 1.1.14 | 2 / 2 | |
| 1.1.13 | 2 / 2 | |
| 1.1.12 | 2 / 2 | |
| 1.1.11 | 2 / 2 | |
| 1.1.10 | 2 / 2 | |
| 1.1.9 | 2 / 2 | |
| 1.1.8 | 2 / 2 | |
| 1.1.7 | 2 / 2 | |
| 1.1.6 | 2 / 2 | |
| 1.1.5 | 2 / 2 | |
| 1.1.4 | 2 / 2 | |
| 1.1.3 | 2 / 2 | |
| 1.1.2 | 2 / 2 | |
| 1.1.1 | 2 / 2 |
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.