vcfR
A genomics workhorse whose visible release feed stops dead in mid-2020.
A side-by-side editorial comparison of Buildkite and crandep — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Buildkite | crandep |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 8.8 | 0.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | ci-cd, developer-tools, mcp, observability | cran, dependency-network, power-law, mcmc |
| Last editorial update | 23h ago | 1h ago |
| Website | — | Visit → |
Buildkite keeps converting hand-rolled agent workarounds into first-class CI primitives.
Buildkite is shipping on two fronts. For agents, the MCP server gained list_tests for suite-wide reliability and duration metrics, and the Test Engine API returns the same aggregates behind a version header. For humans, a native checkout block moved sparse clones, shallow depth and skip-checkout out of plugins and into pipeline YAML, agents can ship job logs to an OpenTelemetry collector, and an organization-wide banner now says when GitHub API rate limits - not Buildkite - are holding up pull request status.
Half CRAN dependency scraper, half extreme-value modelling kit — and the scraper half keeps finding bugs.
crandep does two jobs that rarely share a package: it harvests the CRAN dependency network, and it fits power-law and extreme-value mixture models to the resulting degree distributions. The 2024 releases were all model work — profile posteriors, wrappers, a constrained variant, a TZP-power-law mixture between the two- and three-component models. The 2025 releases are entirely the other half, fixing what the harvester was silently getting wrong.
Buildkite is shipping on two fronts. For agents, the MCP server gained list_tests for suite-wide reliability and duration metrics, and the Test Engine API returns the same aggregates behind a version header. For humans, a native checkout block moved sparse clones, shallow depth and skip-checkout out of plugins and into pipeline YAML, agents can ship job logs to an OpenTelemetry collector, and an organization-wide banner now says when GitHub API rate limits - not Buildkite - are holding up pull request status.
Buildkite is arguing that CI should be forge-independent, and backing it with coverage: GitHub, GitLab, Bitbucket, and now Cursor's Origin, where it shipped as a launch partner on day one. The agent-facing work follows one pattern - remove the workaround automation used to need, so aggregated test metrics replace assembling individual runs and a rate-limit banner replaces guessing why a status never arrived. Each release turns a behavior teams hand-rolled into a supported primitive.
The read side of the MCP server is now largely covered, so expect write-side tools next - retrying jobs, unblocking builds, editing pipelines from an agent - following the pattern the REST expansion established.
crandep does two jobs that rarely share a package: it harvests the CRAN dependency network, and it fits power-law and extreme-value mixture models to the resulting degree distributions. The 2024 releases were all model work — profile posteriors, wrappers, a constrained variant, a TZP-power-law mixture between the two- and three-component models. The 2025 releases are entirely the other half, fixing what the harvester was silently getting wrong.
The modelling side has settled into a family of mixtures with matching wrapper and profile-posterior functions, and has not gained a new component since mid-2024. Attention has shifted to data quality in the scraper, where two consecutive releases dealt with the same class of problem: rows that should not exist because of trailing commas in CRAN's own metadata, and rows that should exist but did not because orphan packages have no edges. For a package whose science is degree distributions, missing isolated nodes is a modelling error, not a formatting one.
Expect further hardening against CRAN metadata quirks in the harvesting functions; the mixture-model side looks feature-complete and is likely to stay quiet unless a new component model is published.
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 Buildkite or crandep.
A genomics workhorse whose visible release feed stops dead in mid-2020.
The R phone-number package stopped only parsing numbers and started asking them where they are.
A Venn diagram package whose public release notes say almost nothing — including about its copyright cleanup.
A Shiny app for choosing the right ordinal test reached CRAN in a single 90-minute burst of tags.
A new R localization package that reached CRAN and immediately downgraded itself to experimental.
An R client for HERE's location APIs, shaped almost entirely by what the vendor exposes next.
See all Buildkite alternatives → · See all crandep alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Buildkite is currently shipping more aggressively (velocity 8.8 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Buildkite is currently shipping more aggressively (velocity 8.8 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.
Top Buildkite alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Buildkite alternatives" section above for the current picks, or visit /alternatives/buildkite for the full list with editorial commentary on each.
Top crandep alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "crandep alternatives" section above for the current picks, or visit /alternatives/crandep for the full list with editorial commentary on each.