hydromancer-hyperliquid@1.0.0
CAUTION· static onlyPublisher claims: "Hyperliquid market and account data through the Hydromancer API: REST (POST /info) for positions, fills, funding, liquidations, oracle prices, candles, vaults, staking, builder-code fills and HIP-3 / HIP-4 markets; WebSocket streams for trades, fills, liquidations, BBO, L2 and L4 order books with session replay; and Reservoir, a requester-pays S3 archive of historical Hyperliquid data in Parquet. Use when building Hyperliquid trading apps, bots, dashboards, copy-trading, tax tools, backtests or research, or when the task mentions Hyperliquid, HyperCore, HIP-3, HIP-4, builder codes, whale tracking, order book data, liquidations, funding history, wallet trade history, or Hydromancer." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-12 and scored it 66/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
… zstd-compressed MessagePack (`zstandard` and `msgpack`, pinned in [requirements.txt](requirements.txt)) and have their own limit of 5 requests per 10 minutes. One market: send `Accept-Encoding: zstd` and the body comes back with `Content-…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.No other findings across 1,095 lines in 13 files.
Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
14 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim joshavenue: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.