Oh Dear
Oh Dear's weekly changelogs have carried a security section five weeks running.
A side-by-side editorial comparison of Grype and KubeArmor — release velocity, themes, recent moves, and the top alternatives to consider.
Grype widens distro accuracy while each release clears its own dependency advisories.
Grype's autumn releases stay on matching accuracy. v0.121.0 carries AlmaLinux fix dates onto replaced RHEL matches and finds GitHub Swift advisories it previously missed, v0.120.0 marks SLES as a comprehensive distro and stores NVD SSVC decision points, and v0.119.0 exposes distro-fixed dropped matches through --show-suppressed. Each minor also carries a large dependency sweep, with v0.121.0 remediating five golang.org/x/net advisories.
KubeArmor ships fixes as release-candidate tags, and its feed misses the finals.
KubeArmor's feed shows five release-candidate tags and one merge-commit entry from October for 1.7.6 and 1.7.7, each carrying one or two commits: a relay-channel memory leak fix with pprof added, a snitch fix, removed limits and an AppArmor alert-throttling fix. GitHub shows 1.7.6 went final on 23 October, which the feed missed; it replaced the execve kprobe with a tracepoint, fixed pods not terminating on AppArmor nodes, added audit alerts from the BPF-LSM enforcer and expanded arm64 eBPF testing.
Grype's autumn releases stay on matching accuracy. v0.121.0 carries AlmaLinux fix dates onto replaced RHEL matches and finds GitHub Swift advisories it previously missed, v0.120.0 marks SLES as a comprehensive distro and stores NVD SSVC decision points, and v0.119.0 exposes distro-fixed dropped matches through --show-suppressed. Each minor also carries a large dependency sweep, with v0.121.0 remediating five golang.org/x/net advisories.
Accuracy remains the roadmap, and the work is increasingly about distro-specific truth: fix dates, extended support and comprehensive coverage. SSVC data in the database is the one new kind of signal, since it adds decision guidance beyond severity. Reachability has still not moved past Go in these notes.
SSVC decision points are stored but not yet described as a user-facing output, so surfacing them in results is the natural next step. These notes give no signal on a second reachability ecosystem.
KubeArmor's feed shows five release-candidate tags and one merge-commit entry from October for 1.7.6 and 1.7.7, each carrying one or two commits: a relay-channel memory leak fix with pprof added, a snitch fix, removed limits and an AppArmor alert-throttling fix. GitHub shows 1.7.6 went final on 23 October, which the feed missed; it replaced the execve kprobe with a tracepoint, fixed pods not terminating on AppArmor nodes, added audit alerts from the BPF-LSM enforcer and expanded arm64 eBPF testing.
The project is mid-way through stabilising its eBPF enforcement across architectures: arm64 syscall matching, multi-arch image tests and the move from kprobes to tracepoints all reduce kernel-specific breakage. The release process remains RC-heavy, with near-identical tags cut minutes apart, which makes the feed a poor guide to what users actually get.
Expect 1.7.7 final soon after rc1, carrying the AppArmor throttling fix. The arm64 work in 1.7.6 suggests further multi-architecture fixes rather than new policy features next.
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 Grype or KubeArmor.
Oh Dear's weekly changelogs have carried a security section five weeks running.
ShenYu's AI gateway plugins are back in motion, with 2.7.2 candidate tags in October.
TestingBot's autumn work is plumbing: a rebuilt tunnel and another bug-tracker link.
All Quiet moves from enterprise integrations to the on-call engineer's own day.
Robusta's recent releases patch its runner image rather than add features.
Uptrends spent October on account plumbing: vault credentials, bulk edits and a free trial path.
See all Grype alternatives → · See all KubeArmor alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Grype and KubeArmor are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Grype and KubeArmor are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
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.
Top KubeArmor alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "KubeArmor alternatives" section above for the current picks, or visit /alternatives/kubearmor for the full list with editorial commentary on each.