Binance Alpha Explorer
v1.0.6Binance Alpha new coin launch detector. Uses WebSocket to monitor !miniTicker@arr stream and detects new trading pairs immediately when they appear. Maintain...
⭐ 0· 1.6k·5 current·5 all-time
bymanifold@manifoldor
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (Binance new-coin monitor) match the code and SKILL.md: it connects to Binance WebSocket (!miniTicker@arr), validates prices via Binance REST API, and persists known symbols and alert history. No unrelated binaries or credentials are requested.
Instruction Scope
Runtime instructions and code only access Binance public endpoints (stream.binance.com and api.binance.com) and local state files (~/.config/alpha). There are no directives to read unrelated system files, environment secrets, or to send data to third-party endpoints. A commented hook hints where a user could add notifications (webhook/email), but that is not enabled by default.
Install Mechanism
This is an instruction-only skill with a Python script; SKILL.md asks the user to pip3 install websocket-client --user. There is no automated install spec that downloads arbitrary code. The only dependency is a common PyPI package; users should install dependencies from their package manager and verify sources.
Credentials
No environment variables, API keys, or unrelated credentials are requested. Public Binance APIs are used and require no auth, so requested access is proportional to the stated functionality.
Persistence & Privilege
The script persistently stores known_symbols.json and alerts_history.json under ~/.config/alpha, which is consistent with the described feature 'state persistence'. always:false and no elevated privileges are requested. Users should know these files will be created/updated on disk.
Assessment
This skill appears coherent and implements exactly what it claims: listening to Binance public WebSocket and storing alerts locally. Before installing or running: (1) review the script if you plan to add notification hooks — that is where external webhooks or credentials could be introduced; (2) run it in a controlled environment or sandbox if you are cautious (it opens network connections to Binance and writes to ~/.config/alpha); (3) install the websocket-client dependency from PyPI via your normal trusted channel; (4) back up or inspect ~/.config/alpha if you care about persistent alert history; and (5) if you do add automated notifications, avoid embedding secrets in the script — use your system's secret manager or environment variables and review their scope.Like a lobster shell, security has layers — review code before you run it.
binance alphavk973mne9gy19s6b2838nww6fp980f5y2latestvk97fftm26sb933s64d02y8bmhd834m8b
License
MIT-0
Free to use, modify, and redistribute. No attribution required.