Summary
Togoder Security scanned the npm package @walletconnect/jsonrpc-types@1.0.4 on Oct 4, 2026. An AI review of 3 source files produced no findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings
No findings. The reviewer saw nothing malicious or risky in this version.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| dist/index.cjs.js | safe | No malicious patterns detected; the file only defines empty class stubs for JSON-RPC provider interfaces. |
| dist/index.es.js | safe | No malicious patterns detected; the file contains only simple class definitions and exports with no external calls, I/O, or dynamic execution. |
| dist/index.umd.js | safe | No malicious patterns detected |
Frequently asked questions
Is @walletconnect/jsonrpc-types safe to use?
Our AI source review of @walletconnect/jsonrpc-types@1.0.4 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does @walletconnect/jsonrpc-types contain malware?
No malware was identified in @walletconnect/jsonrpc-types@1.0.4 when Togoder Security scanned it on Oct 4, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was @walletconnect/jsonrpc-types checked?
Togoder Security downloaded the published npm package and had an AI model read its 3 source files, looking for install scripts, credential access, network exfiltration, obfuscation, backdoors and crypto-wallet theft. The results are cached by file hash and shown here.
How do I scan @walletconnect/jsonrpc-types together with the rest of my dependencies?
Upload your lockfile at https://security.togoder.click/scan or call the API documented at https://security.togoder.click/api-docs. Files that have already been scanned, like the ones in @walletconnect/jsonrpc-types@1.0.4, cost nothing.