Documentation Index
Fetch the complete documentation index at: https://docs.sonicverse.eu/llms.txt
Use this file to discover all available pages before exploring further.
Reporting a vulnerability
Do not open a public GitHub issue for security vulnerabilities. You can report a vulnerability through any of the following channels:Web form
Submit a report through the dedicated security page on sonicverse.eu.
Send details directly to security@sonicverse.eu.
GitHub
Use GitHub’s private vulnerability reporting.
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Affected version, environment, or commit (if known)
- Any suggested fix or mitigation
Scope
In scope:- Command injection via the status panel API
- Authentication bypass in the Appwrite integration
- Container escape via Docker socket exposure
- Secrets leakage through API responses
- CORS misconfigurations allowing unauthorized cross-origin access
- Issues requiring physical access to the server
- Denial of service attacks against a specific deployment
- Social engineering
- Vulnerabilities in third-party dependencies (report those upstream)
Container hardening
All service containers (Status API, Nginx, Analytics, and Icecast) run as non-root users (UID 1000) by default. This limits the impact of a container escape: processes inside the container do not have root privileges on the host.Automated code analysis
SonarQube Cloud automatically analyzes pull requests and pushes tomain for code quality, security vulnerabilities, and coverage reporting.
Secret scanning
This repository uses TruffleHog to detect accidentally committed secrets and sensitive data. A configuration file is provided attrufflehog.toml in the repository root.
Running TruffleHog locally
Install TruffleHog:Running in CI
Add TruffleHog to your GitHub Actions workflow:Supported versions
| Version | Supported |
|---|---|
| Latest | Yes |