Skip to content

Security: koagonzalo11/elparadisogonzalo-monorepo

SECURITY.md

πŸ”’ Security Policy

πŸ“Œ Supported Versions

We maintain the latest main and develop branches. Only the latest release is actively supported with security updates.

Version Supported
main βœ… Yes (latest)
develop ⚠️ Yes (pre-release)
others ❌ No

πŸ§‘β€πŸ’» Reporting a Vulnerability

If you discover a vulnerability in any part of the Elparadisogonzalo ecosystem:

  1. DO NOT open a public issue.
  2. Please report it privately and responsibly via email:
  3. Include:
    • Reproduction steps (if any)
    • Affected component (e.g., smart contract, API endpoint, frontend)
    • Severity level

We aim to respond within 48 hours.


πŸ” Security Practices

  • βœ… Smart contracts are verified and deployed with transparent ABIs.
  • βœ… MetaMask integration uses secure Web3 injection only on user interaction.
  • βœ… Wallet private keys are never exposed in code or logs.
  • βœ… CI/CD pipelines include static code scanning and test coverage checks.
  • βœ… IPFS content hashes (CIDs) are validated before domain updates.
  • βœ… Domain ownership is verified through openai-domain-verification.

πŸ§ͺ Audits & Tooling

  • πŸ” Static analysis via slither, mythx, and solhint
  • βœ… CI check using hardhat test, solc, and dependabot.yml
  • 🧰 Linting: ESLint + Prettier for JS/TS; Solidity formatting via prettier-plugin-solidity
  • πŸ§ͺ GitHub Actions run automated test & build checks on PRs
  • πŸ” OpenZeppelin libraries are used for trusted smart contract patterns

πŸ”„ Responsible Disclosure Timeline

  • Acknowledge report (within 48h)
  • Investigate and reproduce
  • Patch vulnerability
  • Publish CVE advisory or changelog note
  • Credit researcher (if desired)

πŸ™ Thanks

We appreciate ethical hackers and researchers who help secure the Elparadisogonzalo ecosystem.


There aren’t any published security advisories