Until a maintainer contact is configured, do not disclose security issues in a public issue tracker. Contact the project maintainer privately and include a minimal reproduction, affected version, impact, and suggested mitigation.

Secrets, production data, authentication bypasses, authorization flaws, upload handling, payment integration, and socket authorization are in scope. Do not test against production systems without explicit written permission.

This repository preserves a historical source archive after the original service entered maintenance/closure. There are no actively supported versions, guaranteed security updates, or committed response times. Fixes and contributions may be considered at the maintainer's discretion. Anyone running a fork is responsible for its configuration, dependencies, and security maintenance.