Skip to content

Security: keylorpineda/ColonQuest

Security

SECURITY.md

README The situation in Costa Rica, with sources Run and build, for the judges

How to report a vulnerability in ColonQuest and how its secrets are handled. The full content of this card is available as text in the section below.

Read this page as text

Security Policy

Reporting a vulnerability

Please do not open a public issue for security problems. Use GitHub private vulnerability reporting or email keylorpineda729@gmail.com.

We aim to acknowledge reports within 48 hours during the hackathon.

Secrets

  • API keys and database URLs are read from environment variables on the backend only.
  • .env files are ignored by git. Use server/.env.example as the reference.
  • If a secret is ever committed, rotate it immediately; removing it from history is not enough.

There aren't any published security advisories