privy-integration
Fail
Audited by Socket on Mar 8, 2026
1 alert found:
Obfuscated FileObfuscated FileSKILL.md
HIGHObfuscated FileHIGH
SKILL.md
The Privy integration skill appears coherent and aligned with its described purpose. It relies on official Privy packages and standard client/server authentication/workflow patterns. The footprint is proportionate to the goals (auth, embedded wallets, token verification, and transaction signing) and does not exhibit evident credential harvesting, rogue data exfiltration, or arbitrary code execution risks. Key security practices to emphasize: secure handling of app secrets (server-side only), HTTPS for token verification, proper scoping of permissions, and explicit user consent for wallet-related actions. Overall risk is low-to-moderate (benign with recommended safeguards).
Confidence: 98%
Audit Metadata