Fission
Fission's release feed carries only RC tags, and none of them say what shipped
Comparison · Infra & APIs
DNSControl vs Grype
A side-by-side editorial comparison of DNSControl and Grype — release velocity, themes, recent moves, and the top alternatives to consider.
DNSControl vs Grype: at a glance
What is DNSControl?
DNSControl is rewriting its record internals in public, one release candidate at a time
DNSControl is mid-way through a v5 refactor being shipped as a visible candidate series — rc1 through rc4 in roughly two weeks, all of them explicitly promising zero user-facing change. The work replaces how DNS record fields are stored internally with a dnsv2.RDATA type, with legacy structs converted bidirectionally so existing providers keep working untouched. Two other threads run alongside: migrating the miekg/dns dependency from GitHub to Codeberg, now complete and no longer dual-imported, and removing old fields to cut memory use. The release notes read as direct appeals to users — naming nine providers nobody has tested and asking for volunteers, and inviting anyone to a monthly community call.
What is Grype?
Grype's entire roadmap is false positives — and it just went code-aware to cut them.
Almost every release in this window targets match accuracy rather than coverage. Go has taken the brunt of it: merging govulndb GO-* records with their GHSA aliases, scoping GHSA twins by shared CVE, disabling stdlib CPE matching by default, and ignoring compiler CVEs when an image contains only a compiled binary. Coverage still widens at the edges — Zarf packages, Ubuntu ESM, Chainguard OSV data, CycloneDX 1.7 input — but it is not where the effort sits.
DNSControl vs Grype: editorial side-by-side
DNSControl
5.0INFRA · APIS
DNSControl is rewriting its record internals in public, one release candidate at a time
◆ Current state
DNSControl is mid-way through a v5 refactor being shipped as a visible candidate series — rc1 through rc4 in roughly two weeks, all of them explicitly promising zero user-facing change. The work replaces how DNS record fields are stored internally with a dnsv2.RDATA type, with legacy structs converted bidirectionally so existing providers keep working untouched. Two other threads run alongside: migrating the miekg/dns dependency from GitHub to Codeberg, now complete and no longer dual-imported, and removing old fields to cut memory use. The release notes read as direct appeals to users — naming nine providers nobody has tested and asking for volunteers, and inviting anyone to a monthly community call.
◆ Where it's heading
The stated goals are about future velocity rather than present features: making new DNS record types faster to adopt and custom record types easier to implement. That is a bet that the bottleneck on supporting new record types was the internal representation, and it is being paid for with a long candidate series rather than a big-bang release. The provider conversion finished during this window — rc3 declares all providers converted with long-tail work remaining — so the refactor is past its riskiest stretch.
◆ Prediction
The maintainer states v5.x is on schedule to ship before September, and the untested-provider list is the visible blocker; expect further candidates focused on provider coverage rather than new goals.
Grype
6.3INFRA · APIS
Grype's entire roadmap is false positives — and it just went code-aware to cut them.
◆ Current state
Almost every release in this window targets match accuracy rather than coverage. Go has taken the brunt of it: merging govulndb GO-* records with their GHSA aliases, scoping GHSA twins by shared CVE, disabling stdlib CPE matching by default, and ignoring compiler CVEs when an image contains only a compiled binary. Coverage still widens at the edges — Zarf packages, Ubuntu ESM, Chainguard OSV data, CycloneDX 1.7 input — but it is not where the effort sits.
◆ Where it's heading
The arc runs from naive SBOM-to-CVE matching toward evidence-based matching. Reachability analysis is the clearest marker: grype is beginning to reason about whether vulnerable code is actually reachable rather than merely present. The parallel stream of ecosystem-specific correctness work — RHEL minor version streams, RHSA duplication, distro version parsing — suggests the same per-ecosystem treatment is being worked through one package manager at a time.
◆ Prediction
Reachability shipped for Go only. Extending it to a second ecosystem is the obvious next step, and Java or JavaScript are the likeliest targets given where SBOM false positives concentrate.
Alternatives to DNSControl and Grype
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either DNSControl or Grype.
Kaniko
Kaniko's release feed stops dead in June 2024 after a patch that undid its own change
mod_auth_openidc
mod_auth_openidc audited itself, found eight holes, and broke every session on the way out
Antrea
Kubernetes CNI maintaining four release branches at once, mostly to carry CVE fixes back.
KeeWeb
KeePass-compatible password manager frozen mid-patch-run since 2021.
Nebula
Overlay network that rewrote its certificate format, then spent a year fixing what it exposed.
See all DNSControl alternatives → · See all Grype alternatives →
Recent activity from DNSControl and Grype
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 23h agoGrypeCycloneDX output now includes vulnerable version ranges
- 8d agoDNSControlDNSControl v5 rc4 completes the move to Codeberg-hosted miekg/dns
- 9d agoDNSControlDNSControl v5 rc3 finishes converting every provider
- 13d agoGrypeFalse-positive and distro parsing fixes across Go and RHEL
- 19d agoDNSControlDNSControl v5 rc2 continues the internal rewrite
- 21d agoDNSControlDNSControl v5 rc1 lays out the dnsv2.RDATA refactor
- 25d agoGrypeReachability analysis lands to cut Go false positives ⚡
- 1mo agoGrypeGo matching merges govulndb and GHSA records
- 2mo agoGrypeGrype can now scan Zarf packages
- 2mo agoGrypeVersion comparison and platform CPE matching corrections
Frequently asked questions
What is the difference between DNSControl and Grype?
They serve adjacent needs but don't currently overlap on shipped themes. Grype is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is DNSControl better than Grype?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Grype is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to DNSControl?
Top DNSControl alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "DNSControl alternatives" section above for the current picks, or visit /alternatives/dnscontrol for the full list with editorial commentary on each.
What are the best alternatives to Grype?
Top Grype alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Grype alternatives" section above for the current picks, or visit /alternatives/grype for the full list with editorial commentary on each.