Orderly Ui Components
v1.0.0Build trading interfaces using pre-built React components - OrderEntry, Positions, TradingPage, WalletConnect, Sheets, Tables
⭐ 0· 208·0 current·0 all-time
byMario Reder@tarnadas
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The name/description match the SKILL.md: it documents how to build trading UIs with @orderly.network React components. However the skill has no source URL or homepage and the registry metadata offers no provenance, which reduces trust even though the requested capabilities themselves are appropriate.
Instruction Scope
SKILL.md only contains example React code and installation commands for the stated packages; it does not ask the agent to read unrelated files, environment variables, or exfiltrate data. It does include WalletConnect usage — which naturally enables wallet prompts and signing in the browser (user-side), so users should understand wallet actions can result in transaction signing.
Install Mechanism
This is instruction-only and directs the user to install packages via npm/yarn (standard). There is no automated download-from-URL or archive extraction in the skill itself.
Credentials
No environment variables, credentials, or config paths are required. The only sensitive interaction is via WalletConnect/WalletConnector which relies on user-controlled wallets rather than exposing secrets to the skill.
Persistence & Privilege
always is false, the skill is user-invocable and does not request persistent system-level privileges or modify other skills. It is an inert documentation/instruction asset.
Assessment
This skill appears to be a documentation/example bundle for @orderly.network UI packages and is coherent with that purpose, but take these precautions before using it: 1) Verify the npm packages (@orderly.network/*) on the npm registry or their official GitHub to confirm the publisher and source (the skill metadata lacks a homepage/repo). 2) Prefer pinned versions and inspect package maintainers and recent activity before installing into production. 3) Be cautious with WalletConnect/WalletConnector: wallet connections may prompt transaction signing — never paste private keys or approve transactions you don't understand. 4) Consider auditing the installed package code or running it in an isolated environment (container/VM) if provenance is uncertain. 5) If you require stronger assurance, ask the publisher for a repository or an official homepage before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk972cg5wj4b5wfdkmkrkejvv7s82ehkb
License
MIT-0
Free to use, modify, and redistribute. No attribution required.