nuggets
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
A side-by-side editorial comparison of crane and Tailscale — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | crane | Tailscale |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 0.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | clinical-tables, mmrm, survival-analysis, gtsummary | networking, zero-trust, kubernetes, multi-tenancy |
| Last editorial update | 5d ago | 16h ago |
| Website | Visit → | — |
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.
Tailscale is turning the tailnet itself into something a script provisions and pages through.
Two threads run in this window. The client and operator releases are maintenance-grade — a Funnel regression fix, library-only container updates, Kubernetes operator work on PeerRelays, workload identity federation and IPv6 egress. The more consequential thread is the tailnet management API: creation landed in alpha at the end of July, and the list endpoint has now been paginated, with a hard 100-result default for organizations holding more.
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.
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.
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.
Two threads run in this window. The client and operator releases are maintenance-grade — a Funnel regression fix, library-only container updates, Kubernetes operator work on PeerRelays, workload identity federation and IPv6 egress. The more consequential thread is the tailnet management API: creation landed in alpha at the end of July, and the list endpoint has now been paginated, with a hard 100-result default for organizations holding more.
Tailscale has spent this period on two different customers at once. The operator work serves platform teams running Tailscale inside Kubernetes, where the gaps being closed are reconciliation loops, stale DNS ConfigMaps and cert-renewal backoff. The tailnet API work serves a different shape entirely: organizations holding enough tailnets that a hundred is a page boundary, which only happens when tailnets are allocated per customer or per environment rather than per company. The second thread is the one that changes what Tailscale is for.
Pagination on list implies the creation API is being used at volume, so expect the alpha to gain the management operations a fleet needs — policy templating or bulk configuration across tailnets. The client release line looks settled on 1.102.x maintenance in the near term.
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 Tailscale.
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.
dqcheckr adds drift analysis, then removes the YAML a user had to hand-write.
An actuarial mainstay spends its releases on CI plumbing, not on new mathematics.
EDAForge is a data-quality auditor renamed mid-flight, still finding its CRAN footing.
See all crane alternatives → · See all Tailscale alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Tailscale 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Tailscale 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.
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.
Top Tailscale alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Tailscale alternatives" section above for the current picks, or visit /alternatives/tailscale for the full list with editorial commentary on each.