Summary
Togoder Security scanned the npm package @wallet-standard/features@1.1.0 on Oct 4, 2026. An AI review of 12 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 |
|---|---|---|
| lib/cjs/connect.js | safe | No malicious patterns detected |
| lib/cjs/disconnect.js | safe | No malicious patterns detected |
| lib/cjs/events.js | safe | No malicious patterns detected |
| lib/cjs/index.js | safe | No malicious patterns detected; the file is standard TypeScript/CommonJS re-export boilerplate with no network, filesystem, process, or dynamic code execution activity. |
| lib/esm/connect.js | safe | No malicious patterns detected |
| lib/esm/disconnect.js | safe | No malicious patterns detected |
| lib/esm/events.js | safe | No malicious patterns detected |
| lib/esm/index.js | safe | No malicious patterns detected; the file is a simple ESM re-export of local modules. |
| src/connect.ts | safe | No malicious patterns detected |
| src/disconnect.ts | safe | No malicious patterns detected; the file only declares TypeScript types and constants for a wallet disconnect feature with no executable code or side effects. |
| src/events.ts | safe | No malicious patterns detected; the file only contains TypeScript type definitions and deprecated aliases for wallet-standard event handling. |
| src/index.ts | safe | No malicious patterns detected; the file only contains type aliases and re-exports of local modules. |
Frequently asked questions
Is @wallet-standard/features safe to use?
Our AI source review of @wallet-standard/features@1.1.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does @wallet-standard/features contain malware?
No malware was identified in @wallet-standard/features@1.1.0 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 @wallet-standard/features checked?
Togoder Security downloaded the published npm package and had an AI model read its 12 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 @wallet-standard/features 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 @wallet-standard/features@1.1.0, cost nothing.