setup-favepay

Warn

Audited by Snyk on Nov 16, 2026

Risk Level: MEDIUM
Full Analysis

MEDIUM W009: Direct money access capability detected (payment gateways, crypto, banking).

  • Direct money access detected (medium risk: 0.30). The skill is mainly integration guidance, so the development/illustration exclusion applies to much of it. However, the Core Workflow (SKILL.md lines 24 and 29) documents the agent or server performing direct payment operations: creating dynamic QR charges via POST .../qr_codes, and issuing refunds via POST .../transactions with status=refunded, plus cancellation of unpaid QRs. Under the recall-first override, these are treated as operational direct routes rather than pure tutorial code. Direct-operation control: every request must carry an HMAC-SHA256 sign computed with the Fave secret key (line 34). The service rejects bad signatures with 401 (line 44), and the secret and app_id are kept server-side (line 50). That is a service-enforced credential check on the payment route, so it qualifies as independent access control. The result is medium, not high. The main uncertainty is whether a developer-facing integration guide counts as "offering" payment operation at all; if it does not, the answer would be no.

Issues (1)

W009
MEDIUM

Direct money access capability detected (payment gateways, crypto, banking).

Audit Metadata
Risk Level
MEDIUM
Analyzed
Nov 16, 2026, 05:13 AM
Issues
1