Skip to content

Security: VincentJerico/taskflow-under-test

Security

SECURITY.md

Security Policy

Scope

TaskFlow is a portfolio/demo application, not a production service. It is intentionally simple; do not store real or sensitive data in it.

Reporting a vulnerability

If you find a security issue, please open a GitHub issue marked [SECURITY] or email vincentjericoalcuran@gmail.com. Please avoid sharing exploit details publicly until it's addressed.

Known, intentional limitations (demo scope)

  • Auth rate limiting is per client IP and kept in memory, so it resets on restart and isn't shared between processes. There is no per-account lockout. Behind a reverse proxy (e.g. Render), Express needs trust proxy set or every client shares the proxy's IP; this isn't configured yet.
  • Tokens are opaque DB-backed sessions without expiry.
  • HTTPS/security headers are the host's responsibility (see DEPLOY.md).

These are acceptable for a demo but would be hardened for production.

There aren't any published security advisories