Oh Dear
Oh Dear's weekly changelogs have carried a security section five weeks running.
Comparison · Infra & APIs
Gitness vs Grype
A side-by-side editorial comparison of Gitness and Grype — release velocity, themes, recent moves, and the top alternatives to consider.
Gitness vs Grype: at a glance
What is Gitness?
Harness Open Source last shipped in August 2025, on this feed at least
The feed holds two releases of Harness Open Source, tracked here as Gitness. v3.2.0 in May 2025 added Git LFS, default reviewers through branch rules and a Revert PR option; v3.3.0 that August added tag rules, a PR dashboard upgrade with favourite repositories, and a fix for a Git LFS upload path flaw. Nothing newer appears here.
What is Grype?
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.
Gitness vs Grype: editorial side-by-side
Gitness
0.0INFRA · APIS
Harness Open Source last shipped in August 2025, on this feed at least
◆ Current state
The feed holds two releases of Harness Open Source, tracked here as Gitness. v3.2.0 in May 2025 added Git LFS, default reviewers through branch rules and a Revert PR option; v3.3.0 that August added tag rules, a PR dashboard upgrade with favourite repositories, and a fix for a Git LFS upload path flaw. Nothing newer appears here.
◆ Where it's heading
Both releases deepen code-hosting governance: branch rules, then tag rules, plus review routing through Code Owners. That is parity work against established Git hosts rather than a new direction. With entries more than a year old, the feed shows where the project was heading in 2025, not where it is now.
◆ Prediction
The entries do not support a confident call: there is no release in this feed after v3.3.0, so it is unclear whether the project slowed or the feed stopped tracking it.
Grype
5.0INFRA · APIS
Grype widens distro accuracy while each release clears its own dependency advisories.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to Gitness 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 Gitness or Grype.
Apache ShenYu
ShenYu's AI gateway plugins are back in motion, with 2.7.2 candidate tags in October.
TestingBot
TestingBot's autumn work is plumbing: a rebuilt tunnel and another bug-tracker link.
KubeArmor
KubeArmor ships fixes as release-candidate tags, and its feed misses the finals.
All Quiet
All Quiet moves from enterprise integrations to the on-call engineer's own day.
Robusta
Robusta's recent releases patch its runner image rather than add features.
See all Gitness alternatives → · See all Grype alternatives →
Recent activity from Gitness and Grype
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 13d agoGrypev0.121.0: AlmaLinux fix dates and Swift advisory matching
- 26d agoGrypev0.120.1: Windows handle leaks and table output fix
- 1mo agoGrypev0.120.0: NVD SSVC data, SLES coverage, HTML locations
- 1mo agoGrypev0.119.0: --show-suppressed exposes distro-fixed matches
- 2mo agoGrypeapk alias-aware matching; CVSSv4 and JVM comparison fixes
- 2mo agoGrypeCycloneDX output now includes vulnerable version ranges
- 1y agoGitnessHarness Open Source 3.3: tag rules, PR dashboard, LFS path fix
- 1y agoGitnessHarness Open Source 3.2: Git LFS, default reviewers, Revert PR
Frequently asked questions
What is the difference between Gitness and Grype?
They serve adjacent needs but don't currently overlap on shipped themes. Grype is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 Gitness better than Grype?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Grype is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 Gitness?
Top Gitness alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Gitness alternatives" section above for the current picks, or visit /alternatives/gitness 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.