Orderly Sdk Debugging
PassAudited by ClawScan on May 1, 2026.
Overview
This is an instruction-only Orderly SDK troubleshooting guide with purpose-aligned setup and authentication-debugging examples, and no artifact-backed malicious or overbroad behavior was found.
This skill appears safe as a debugging reference. Before using its snippets, remember that console logs can expose wallet/account identifiers, and review any npm dependency before adding it to your project.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If copied into an app, the snippet may print wallet/account identifiers to the browser console, which could be sensitive if logs are shared.
The debugging example inspects account identifiers and whether an Orderly key exists. This is relevant to authentication troubleshooting, but it touches account/session-related state.
console.log('Account State:', { status: state.status, address: state.address, userId: state.userId, accountId: state.accountId, hasOrderlyKey: !!account?.keyStore?.getOrderlyKey(), });Use these logs only during local debugging, avoid printing actual secret keys, and remove or redact account identifiers before sharing logs.
Installing the suggested package changes the user's project dependencies.
The guide recommends installing an npm development dependency to fix browser polyfill issues. This is a normal, purpose-aligned setup step, but it adds third-party package supply-chain dependency to the user's project.
npm install -D vite-plugin-node-polyfills
Review the package source and version, pin dependency versions where appropriate, and install it only in projects that need the described Vite/browser polyfill fix.