| Version | Supported |
|---|---|
| Latest minor release | ✅ |
| Previous minor release | ✅ (security fixes only) |
| Older versions | ❌ |
Do NOT open a public issue for security vulnerabilities.
Instead, please report them via one of these channels:
- Email: security@thedataenginex.dev
- GitHub Security Advisories: Use the "Report a vulnerability" button on the relevant repo's Security tab
- Description of the vulnerability
- Steps to reproduce
- Potential impact assessment
- Suggested fix (if any)
| Stage | Timeline |
|---|---|
| Acknowledgment | Within 48 hours |
| Initial assessment | Within 5 business days |
| Fix development | Within 30 days (critical), 90 days (non-critical) |
| Public disclosure | After fix is released |
We follow coordinated disclosure. We will credit reporters in the security advisory unless they prefer to remain anonymous.
TheDataEngineX follows these security practices across all repos:
- No hardcoded secrets — all credentials via environment variables
- Parameterized queries — never SQL concatenation
- Input validation — Pydantic models at API boundaries
- Dependency auditing — automated via
uv run poe security - Container security — non-root users, minimal base images, no unnecessary packages
- HTTPS only — all production traffic encrypted
- Least privilege — minimal permissions for service accounts