@orderly.network/ui-transfer
deposit & withdraw
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 17 / 9 | |
| 3.0.4 | 17 / 9 | |
| 3.0.3 | 17 / 9 | |
| 3.0.2 | 17 / 9 | |
| 3.0.1 | 17 / 9 | |
| 3.0.0 | 17 / 9 | |
| 2.12.4 | 16 / 9 | |
| 2.12.3 | 16 / 9 | |
| 2.12.2 | 16 / 9 | |
| 2.12.1 | 16 / 9 | |
| 2.12.0 | 16 / 9 | |
| 2.11.2 | 15 / 9 | |
| 2.11.1 | 15 / 9 | |
| 2.11.0 | 15 / 9 | |
| 2.10.2 | 15 / 9 | |
| 2.10.1 | 15 / 9 | |
| 2.10.0 | 15 / 9 | |
| 2.9.1 | 15 / 9 | |
| 2.9.0 | 15 / 9 | |
| 2.8.14 | 15 / 9 | |
| 2.8.13 | 15 / 9 | |
| 2.8.12 | 15 / 9 | |
| 2.8.11 | 15 / 9 | |
| 2.8.10 | 15 / 9 | |
| 2.8.9 | 15 / 9 | |
| 2.8.8 | 15 / 9 | |
| 2.8.7 | 15 / 9 | |
| 2.8.6 | 15 / 9 | |
| 2.8.5 | 15 / 9 | |
| 2.8.4 | 15 / 9 | |
| 2.8.3 | 15 / 9 | |
| 2.8.2 | 15 / 9 |
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.