Skip to content

Security: Pablo-aps/payments-engineering-skills

SECURITY.md

Security policy

Reporting a vulnerability

Do not open a public issue for a vulnerability that could cause unauthorized money movement, signature bypass, duplicate financial effects, sensitive-data exposure, or a practical exploit in the included examples.

Use GitHub's private vulnerability reporting for this repository: open the Security tab, choose Advisories, then Report a vulnerability.

Include the affected skill or asset, impact, reproduction steps, and a safe contact method. You should receive an acknowledgement within seven days. Disclosure timing will be coordinated after the issue is understood and a remediation is available.

Scope

The repository contains engineering guidance and adaptable contracts rather than a hosted payment service. Security reports should identify a concrete unsafe instruction, validation bypass, or exploitable example. General hardening suggestions can use a normal issue.

Never include live API keys, webhook secrets, cardholder data, private wallet material, or customer data in a report.

There aren't any published security advisories