evaluate
The engine under every knitted R document reached 1.0 by making evaluation behave like the console.
Comparison · Infra & APIs
crane vs Depot
A side-by-side editorial comparison of crane and Depot — release velocity, themes, recent moves, and the top alternatives to consider.
crane vs Depot: at a glance
| Feature | crane | Depot |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 0.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | clinical-tables, mmrm, survival-analysis, gtsummary | ci-cd, build-acceleration, test-intelligence, git-hosting |
| Last editorial update | 1h ago | 13h ago |
| Website | Visit → | — |
What is crane?
Crane is turning into the table-and-plot layer for Roche's clinical output stack.
Crane publishes release candidates rather than finals, and the whole of 0.3.2 is carried by a single rc2 body — its two sibling tags are one-line styling commits, one of them tagged with an unsubstituted vX.Y.Z placeholder. The rc2 notes run to dozens of additions across regression tables, line plots and hierarchical rate tables.
What is Depot?
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.
crane vs Depot: editorial side-by-side
crane
0.0INFRA · APIS
Crane is turning into the table-and-plot layer for Roche's clinical output stack.
◆ Current state
Crane publishes release candidates rather than finals, and the whole of 0.3.2 is carried by a single rc2 body — its two sibling tags are one-line styling commits, one of them tagged with an unsubstituted vX.Y.Z placeholder. The rc2 notes run to dozens of additions across regression tables, line plots and hierarchical rate tables.
◆ Where it's heading
The package is moving from plotting helpers to a full analysis-output layer: mixed models for repeated measures, pairwise Cox results, risk-management-plan tables and adverse-event incidence rates all arrive in one cycle, and the annotation machinery underneath was rebuilt for reliable table-to-axis alignment. Defaults are being pulled toward SAS and rtables output — the log-rank test now uses survival::survdiff instead of coin, and survfit confidence intervals default to plain rather than log.
◆ Prediction
Expect a 0.3.2 final close behind rc2, and the deprecated g_lineplot() family to be removed once gg_lineplot() and annotate_gg() have settled.
Depot
6.3INFRA · APIS
Depot keeps absorbing the CI stack — tests, networking, runners, now its own git host.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to crane and Depot
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 crane or Depot.
carrier
carrier's 0.3.0 quietly rewrites how crated functions see each other — and breaks code that relied on the old rules.
watcher
watcher is a thin filesystem-events binding whose releases are mostly build work.
gh
gh spent its last two releases making failures and interruptions recoverable.
checkhelper
checkhelper grew from a check wrapper into a CRAN pre-submission auditor.
dockerfiler
dockerfiler's 1.0.0 changes what its generated Dockerfiles actually contain.
Recent activity from crane and Depot
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4d agoDepotmacOS 26 is now the default macOS version for GitHub Actions runners
- 11d agoDepotDepot CI now supports native GitHub stacked pull requests
- 14d agoDepotSet cache retention when creating a project with --cache-policy-keep-days
- 15d agoDepotView and edit project details from the Depot CLI
- 16d agoDepotTest results are now generally available ⚡
- 24d agoDepotAI analysis available for all Depot CI workflows and jobs
- 2mo agocraneMMRM, Cox and incidence-rate tables land in one release ⚡
- 2mo agocraneExample styling and runtime cleanup
- 2mo agocranePlaceholder release tag from the same styling commit
Frequently asked questions
What is the difference between crane and Depot?
They serve adjacent needs but don't currently overlap on shipped themes. Depot is currently shipping more aggressively (velocity 6.3 vs 0.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 crane better than Depot?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Depot is currently shipping more aggressively (velocity 6.3 vs 0.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 crane?
Top crane alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "crane alternatives" section above for the current picks, or visit /alternatives/crane for the full list with editorial commentary on each.
What are the best alternatives to Depot?
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.