Timely
Timely is grinding down the friction between tracked time and the tools it has to reconcile with.
Comparison · Infra & APIs
Grype vs Skipper
A side-by-side editorial comparison of Grype and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.
Grype vs Skipper: at a glance
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.
What is Skipper?
Skipper tags a release per commit — nine in eight days, and none of them change routing.
Skipper is Zalando's HTTP router and reverse proxy, cut as a GitHub tag on essentially every merged commit: v0.27.42 through v0.27.50 landed inside eight days. The content of that stream is maintenance — dependency group bumps, CI action upgrades, test corrections, and one internal refactor pulling the Valkey Del command and ratelimit ring client injection apart. The single change with user-visible effect in this window is a fix to the proxy listener binding on an insecure address.
Grype vs Skipper: editorial side-by-side
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.
Skipper
5.0INFRA · APIS
Skipper tags a release per commit — nine in eight days, and none of them change routing.
◆ Current state
Skipper is Zalando's HTTP router and reverse proxy, cut as a GitHub tag on essentially every merged commit: v0.27.42 through v0.27.50 landed inside eight days. The content of that stream is maintenance — dependency group bumps, CI action upgrades, test corrections, and one internal refactor pulling the Valkey Del command and ratelimit ring client injection apart. The single change with user-visible effect in this window is a fix to the proxy listener binding on an insecure address.
◆ Where it's heading
Nothing in these entries points to a direction change; the 0.27 line is in steady maintenance with supply-chain hygiene as the visible priority — oras-go pinned to a released version so osv-scanner stops flagging it, the CodeQL action upgraded, an OPA test hardened to deny requests with truncated bodies. The documentation change is the most revealing item: jwtValidation's behavior was unclear enough to prompt a proposed advisory, and the response was to clarify the docs rather than alter the code.
◆ Prediction
The tag stream will most likely continue at several releases a week with the same composition of dependency bumps and test fixes. These entries show no feature work in flight, so the next notable change is more likely another security-adjacent clarification than a new routing capability.
Alternatives to Grype and Skipper
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 Skipper.
Unleash
Unleash is publishing more positioning than product, with 8.1 the only actual release.
Sonarr
Sonarr is in pure maintenance mode — six releases, not one feature.
Auth0
Auth0 is rebuilding identity around actors that operate on someone else's behalf.
ToolJet
ToolJet's beta line is stacking AI datasource connectors while LTS takes the security work.
GravityKit
GravityKit is quietly turning Gravity Forms entries into a cross-form data layer.
See all Grype alternatives → · See all Skipper alternatives →
Recent activity from Grype and Skipper
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 9h agoSkipperPin oras-go to a released version to satisfy osv-scanner
- 16h agoGrypeCycloneDX output now includes vulnerable version ranges
- 18h agoSkipperClarify jwtValidation behavior after a proposed advisory
- 23h agoSkipperRefactor Valkey Del and ratelimit ring client injection
- 23h agoSkipperBump the CodeQL upload-sarif action to 4.37.6
- 23h agoSkipperBump 14 Go modules, including OpenTelemetry and go-redis
- 4d agoSkipperFix the proxy listener binding on an insecure address
- 13d agoGrypeFalse-positive and distro parsing fixes across Go and RHEL
- 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 Grype and Skipper?
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 Grype better than Skipper?
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 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.
What are the best alternatives to Skipper?
Top Skipper alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Skipper alternatives" section above for the current picks, or visit /alternatives/skipper for the full list with editorial commentary on each.