Happy Hadada is in private beta. Here is what works today and what
is on the roadmap.
Live
Real-time CVE matching
New and updated advisories from OSV.dev (which includes the GitHub Advisory Database, npm, PyPI, Go, RustSec and more) are matched against the packages of every connected repo. Our target is an alert within 15 minutes of an advisory being published.
Live
Every push checked
Each push to your main branch refreshes the list of packages and exact versions your repo uses, and checks it against all known advisories.
Live
Fewer, better alerts
Dev-only dependencies, low-severity issues and duplicates across lockfiles are held back, unless CISA lists the vulnerability as actively exploited. Every alert we hold back is logged with a reason, so we can measure the noise we filter.
Live
Plain-language alerts
Email and Slack alerts name the affected package and repo, the smallest version that fixes it and the exploit probability (EPSS).
Live
Malicious package detection
Packages reported as malware by the OpenSSF malicious packages project are always treated as critical, with advice to remove the package and rotate secrets.
Planned
Fix suggestions
A plain-language explanation and a proposed fix, delivered as a diff plus a prompt you can paste into your AI coding tool.
Planned
Verified fix PRs
Fixes are applied in an isolated sandbox, then the project is built, its tests are run and it is re-scanned. A pull request is opened only if all checks pass.
Planned
Checks for vibe-coded apps
Supabase row-level security turned off, service keys in frontend code, open Firebase rules and unauthenticated API routes.
Planned
Code and secret scanning
Code pattern rules and secret detection on every change, plus scheduled deep scans of all your repos.
Planned
GitLab, Azure DevOps and Bitbucket
GitHub comes first. Other git platforms follow later.