hyperliquid
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): dotenv is a declared runtime dep used in config; phantom-dep heuristic is a false positive here. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Husky install gated on .git existence; only runs in dev checkout, not in consumer installs. | ai | |
| semgrep | semgrep:shady-links-tlds | AI (semgrep): hyperliquid.xyz and hyperliquid-testnet.xyz are the official Hyperliquid exchange API endpoints, not C2 infrastructure. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.7.7 | 5 / 8 | |
| 1.7.6 | 5 / 8 | |
| 1.5.8 | 6 / 5 | |
| 1.5.7 | 6 / 5 | |
| 1.5.6 | 6 / 5 | |
| 1.5.5 | 6 / 5 | |
| 1.5.4 | 6 / 5 | |
| 1.5.2 | 6 / 4 | |
| 1.5.0 | 6 / 4 | |
| 1.4.1 | 6 / 1 | |
| 1.3.6 | 6 / 1 | |
| 1.3.5 | 6 / 1 | |
| 1.3.2 | 6 / 1 | |
| 1.3.1 | 6 / 1 | |
| 1.2.2 | 6 / 0 | |
| 1.1.2 | 6 / 0 | |
| 1.1.1 | 6 / 0 | |
| 1.1.0 | 6 / 3 | |
| 1.0.1 | 6 / 0 | |
| 1.0.0 | 6 / 0 |
v1.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.