evaluate
The engine under every knitted R document reached 1.0 by making evaluation behave like the console.
A side-by-side editorial comparison of Depot and gh — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Depot | gh |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 2.5 |
| Sparks · 30d | 1 | 0 |
| Top themes | ci-cd, build-acceleration, test-intelligence, git-hosting | github-api, http-client, pagination, token-handling |
| Last editorial update | 13h ago | 1h ago |
| Website | — | Visit → |
Depot keeps absorbing the CI stack — tests, networking, runners, now its own git host.
Depot has moved well past build caching. Test results reached general availability in July with org-wide flaky, slow, and recurring failure analytics plus timing-based shard splitting; Sherlock's AI analysis became available on any run rather than only failed ones; and CI jobs can join a Tailscale tailnet to reach private services. The runner fleet now defaults to macOS 26 on M4 hardware, Depot CI understands GitHub stacked pull requests, and Depot Code — a diskless git server backed by blob storage — entered private beta.
gh spent its last two releases making failures and interruptions recoverable.
The GitHub API client rebuilt on httr2 in 1.4.0, then took a security-driven breaking change in 1.5.0: response headers are no longer stored in returned objects, because they can carry sensitive information. The 1.6.0 release made interrupted pagination recoverable and downgraded personal access token format validation from an error to a warning.
Depot has moved well past build caching. Test results reached general availability in July with org-wide flaky, slow, and recurring failure analytics plus timing-based shard splitting; Sherlock's AI analysis became available on any run rather than only failed ones; and CI jobs can join a Tailscale tailnet to reach private services. The runner fleet now defaults to macOS 26 on M4 hardware, Depot CI understands GitHub stacked pull requests, and Depot Code — a diskless git server backed by blob storage — entered private beta.
The pattern is absorbing each adjacent piece of the pipeline that Depot's position already gives it data about. It runs the builds, so it owns test timing, so it can balance shards; it runs the jobs, so it can diagnose them; it hosts the runners, so it can wire private networking into them. Depot Code extends the same logic upstream to source hosting, which would close the loop between repository and runner. A quieter parallel thread keeps moving SDK- and dashboard-only settings into the CLI, stated explicitly as making projects configurable by agents and scripts.
Depot Code widening past private beta and binding more tightly to CI is the move the rest of the window sets up. The test work is also positioned to go from reporting to selection — skipping tests a change cannot affect — since Depot now holds the timing and failure history that would require, though the entries stop short of saying so.
The GitHub API client rebuilt on httr2 in 1.4.0, then took a security-driven breaking change in 1.5.0: response headers are no longer stored in returned objects, because they can carry sensitive information. The 1.6.0 release made interrupted pagination recoverable and downgraded personal access token format validation from an error to a warning.
The direction is tolerance for partial and unusual outcomes rather than new endpoint coverage. Interrupting a paginated call now raises a classed condition carrying the records already fetched; a 304 Not Modified returns an empty response with headers intact instead of erroring; an unrecognised token format warns and proceeds. A fake_github_app() built on webfakes ships for testing, and is offered to other package authors.
Token format handling is now configurable rather than fixed, so the next likely work is following GitHub's credential formats as they change, not expanding the client surface.
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 Depot or gh.
The engine under every knitted R document reached 1.0 by making evaluation behave like the console.
carrier's 0.3.0 quietly rewrites how crated functions see each other — and breaks code that relied on the old rules.
watcher is a thin filesystem-events binding whose releases are mostly build work.
checkhelper grew from a check wrapper into a CRAN pre-submission auditor.
dockerfiler's 1.0.0 changes what its generated Dockerfiles actually contain.
Crane is turning into the table-and-plot layer for Roche's clinical output stack.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Depot is currently shipping more aggressively (velocity 6.3 vs 2.5), 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Depot is currently shipping more aggressively (velocity 6.3 vs 2.5), 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.
Top Depot alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Depot alternatives" section above for the current picks, or visit /alternatives/depot for the full list with editorial commentary on each.
Top gh alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "gh alternatives" section above for the current picks, or visit /alternatives/gh for the full list with editorial commentary on each.