paddle-billing-history
Pass
Audited by Gen Agent Trust Hub on Jun 15, 2026
Risk Level: SAFE
Full Analysis
- [DATA_EXPOSURE]: The skill explicitly instructs developers to use a mandatory
customerIdfilter when querying the Paddle API. This is a critical security control that prevents one authenticated user from accessing the transaction history of another customer. - [CREDENTIALS_UNSAFE]: Security best practices are followed for credential management. The skill correctly identifies that sensitive values like
PADDLE_API_KEYandSUPABASE_SERVICE_ROLE_KEYmust be stored in server-side environment variables and never exposed to the client browser. - [COMMAND_EXECUTION]: The provided Next.js Server Action logic performs authentication checks using Supabase before executing any business logic, ensuring that unauthorized or anonymous requests are rejected at the edge.
- [EXTERNAL_DOWNLOADS]: The documentation references the official
paddle-nextjs-starter-kiton GitHub and the official Paddle API documentation. These are legitimate resources provided by the vendor for integration support.
Audit Metadata