// the take
Dawnscanner is a Ruby gem that scans Sinatra, Padrino, and Rails codebases for known-vulnerable gem versions and a set of pattern-based security checks, driven by a separately-distributed knowledge base pulled from NVD data. It's aimed at Ruby web shops that want a quick dependency/pattern security pass without standing up a full SAST pipeline.
The knowledge base is decoupled from the gem itself and versioned/signed (kb.yaml.sig) with per-release checksums, so CVE data can in theory be refreshed independently of a tool release. The CLI is cleanly split between `scan` and `kb` subcommands, with the latter letting you query, lint, and check the status of the knowledge base directly rather than only running full scans. The core gem-version matching against Gemfile.lock has a long real-world track record, with the project and its checksummed releases going back to 2013.
No commits since March 2024 — for a tool whose entire pitch is a weekly-updated CVE knowledge base, a dormant project means that data is now roughly two and a half years stale, so recent CVEs simply won't be flagged. The README itself says taint-tracking for XSS/SQLi sinks is still 'in the project roadmap,' meaning the interesting static-analysis capability was never shipped; what you actually get is gem-version matching plus pattern checks, functionally closer to bundler-audit than a real SAST tool. The knowledge base is a manual download-and-unpack step from a separate repo rather than bundled or auto-updating, which is easy to forget and introduces a second artifact that can drift out of sync. Output is plain text written to a timestamped directory only, with no JSON or SARIF, so CI integration for gating or PR annotations requires writing your own parser.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →