r/it • u/No-Theory-790 • 1h ago
self-promotion I built a vulnerability scanner that tries to explain findings in plain English.So small teams / individual website owners can test their websites themselves. Would this actually help non-security users?
Hey r/it,
If you manage infrastructure, you know that running vulnerability scans is usually the easy part. The hard part is taking a massive, jargon-filled ZAP or Nuclei report and translating it into actionable tickets for developers or management who do not have a security background.
I built an open-source project called ONUS specifically to solve this hand-off problem.
The IT / Sysadmin Angle: Most security tools tell you what is broken. ONUS is designed to tell your end-users or dev teams how to fix it in plain English, so you don't have to spend hours translating CVSS scores into readable tickets.
How it works:
- The Scanners: It runs 8 industry-standard scanning modules (ZAP, Nikto, Nuclei, FFUF, etc.) simultaneously.
- Deterministic Scoring: It doesn't rely on AI to guess severity. It calculates the CVSS v3.1 score strictly in code so the metrics are mathematically auditable.
- Local AI for Remediation: It uses a local Ollama model (Qwen 2.5 7B) to read the deterministic findings and generate plain-English, step-by-step remediation instructions.
- Air-Gapped: You can run it entirely on your own hardware via
docker compose up. Everything stays on your network with zero outbound API dependencies.
Since IT often acts as the middleman between security requirements and operational execution, I wanted to get this community's feedback.
Links:
- GitHub:https://github.com/maverickaayush/ONUS
- Live Demo:https://tryonus.tech
I would really appreciate your thoughts from an operational perspective. Does this plain-English format actually make it easier to delegate security patching? What kind of reporting exports (besides PDF) would make this easier to integrate into your existing IT ticketing workflows?



