@hot-labs/omni-sdk
A fast and cheap bridge protocol over HOT Protocol that uses the NEAR Intents engine for exchange
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is used for blockchain address/hash encoding in a bridge SDK — expected pattern, not obfuscation. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding used for Cosmos bridge utility data — standard cross-chain encoding, not malicious. | ai | |
| phantom-deps | phantom-dep:@ton/ton | AI (phantom-deps): Listed as direct dependency in package.json; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ton/crypto | AI (phantom-deps): Listed as direct dependency in package.json; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@near-js/crypto | AI (phantom-deps): Listed as direct dependency in package.json; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 67 of 67)
| Version | Deps | Published |
|---|---|---|
| 2.25.5 | 14 / 4 | |
| 2.25.4 | 14 / 4 | |
| 2.25.3 | 14 / 4 | |
| 2.25.1 | 14 / 4 | |
| 2.25.0 | 14 / 4 | |
| 2.24.8 | 14 / 4 | |
| 2.24.7 | 14 / 4 | |
| 2.24.6 | 14 / 4 | |
| 2.24.5 | 15 / 4 | |
| 2.24.4 | 15 / 4 | |
| 2.24.3 | 14 / 4 | |
| 2.24.2 | 14 / 3 | |
| 2.24.1 | 14 / 3 | |
| 2.24.0 | 14 / 3 | |
| 2.23.6 | 14 / 2 | |
| 2.23.4 | 14 / 2 | |
| 2.23.3 | 14 / 2 | |
| 2.23.2 | 14 / 2 | |
| 2.23.1 | 14 / 2 | |
| 2.23.0 | 14 / 2 | |
| 2.21.3 | 13 / 2 | |
| 2.21.2 | 13 / 2 | |
| 2.21.1 | 13 / 2 | |
| 2.21.0 | 13 / 2 | |
| 2.20.18 | 13 / 2 | |
| 2.20.17 | 13 / 2 | |
| 2.20.16 | 13 / 2 | |
| 2.20.15 | 13 / 2 | |
| 2.20.14 | 13 / 2 | |
| 2.20.13 | 13 / 2 | |
| 2.20.12 | 13 / 2 | |
| 2.20.11 | 13 / 2 | |
| 2.20.10 | 13 / 2 | |
| 2.20.9 | 13 / 2 | |
| 2.20.8 | 13 / 2 | |
| 2.20.7 | 13 / 2 | |
| 2.20.6 | 13 / 2 | |
| 2.20.5 | 13 / 2 | |
| 2.20.4 | 13 / 2 | |
| 2.20.3 | 13 / 2 | |
| 2.20.2 | 13 / 2 | |
| 2.20.1 | 13 / 2 | |
| 2.19.4 | 13 / 2 | |
| 2.19.3 | 13 / 2 | |
| 2.19.2 | 13 / 2 | |
| 2.19.1 | 13 / 2 | |
| 2.19.0 | 13 / 2 | |
| 2.18.10 | 16 / 2 | |
| 2.18.9 | 16 / 2 | |
| 2.18.8 | 16 / 2 | |
| 2.18.7 | 16 / 2 | |
| 2.18.6 | 16 / 2 | |
| 2.18.5 | 16 / 2 | |
| 2.18.4 | 16 / 2 | |
| 2.11.0 | 16 / 2 | |
| 2.9.0 | 15 / 2 | |
| 2.8.3 | 15 / 2 | |
| 2.8.2 | 15 / 2 | |
| 2.8.1 | 15 / 2 | |
| 2.8.0 | 15 / 2 | |
| 2.7.1 | 15 / 2 | |
| 2.7.0 | 15 / 2 | |
| 2.6.0 | 15 / 2 | |
| 2.5.1 | 15 / 2 | |
| 2.5.0 | 15 / 2 | |
| 2.4.0 | 15 / 2 | |
| 2.3.5 | 15 / 2 |
v2.25.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.