PackageFlashyFinancial
@flashyfinancial/wdk-capability-audit
A capability audit for wallets built on Tether’s WDK: scans a project’s node_modules for every installed @tetherto/wdk-* package, reads what each declares about the chains it supports, and classifies each chain as mainnet, testnet or unknown — against a small hand-maintained registry, never a guess.
version 0.2.0 · measured 2026-10-30 from a checkout · source: github.com/AgenteLabs/wdk-capability-audit
npm i -D @flashyfinancial/wdk-capability-auditThe boring, load-bearing pre-production question — which of the WDK modules we installed point at mainnet, and which are still wired to a testnet somebody forgot to swap out — answered the same way every run, and refusing rather than guessing when it is not sure. The third of the WDK kits, beside wdk-policy-guard and wdk-staking-kit, and the first of the three to publish under the FlashyFinancial scope.
Edge cases — each one paid for once
unrecognized-shape with 0 chains is a refusal, not a clean bill of health
inspectModule() reads a package’s chains at wdk.chains in its own package.json, and that convention has not been observed in any published @tetherto/wdk-* release: six real WDK packages were inspected and none declares it, taking chain configuration from the integrating application at runtime instead. Against today’s real packages the tool therefore reports unrecognized-shape and zero chains for every one — the tool saying it could not recognise the shape, which the README puts in a warning box above the install line so nobody reads it as “no testnet exposure”.