abacatepay
Pass
Audited by Gen Agent Trust Hub on May 9, 2026
Risk Level: SAFE
Full Analysis
- [SAFE]: The skill uses a Bearer token for authentication, which is stored in a local configuration file with restricted permissions (0600), preventing other users on the system from reading it.
- [SAFE]: All network communication is directed to the official AbacatePay API domain (api.abacatepay.com) using secure HTTPS.
- [SAFE]: The implementation uses only the Ruby standard library (json, net/http, uri, fileutils), which eliminates risks associated with third-party package supply chain attacks.
- [SAFE]: Setup and sensitive operations (like creating charges or withdrawals) are explicitly designed to require user confirmation according to the instructions in SKILL.md.
- [SAFE]: No obfuscation, prompt injection attempts, or malicious persistence mechanisms were detected in the codebase or metadata.
Audit Metadata