Buildkite
Buildkite keeps converting hand-rolled agent workarounds into first-class CI primitives.
A side-by-side editorial comparison of cofad and vimp — release velocity, themes, recent moves, and the top alternatives to consider.
Contrast analysis with a Shiny front end, shipping about one release a year
cofad performs contrast analyses for factorial designs in both between- and within-subject forms, and ships a Shiny GUI alongside the R interface. The 0.3.0 release in 2024 was the substantial one: a helper for calculating differences between two sets of lambdas for competing contrast analysis, improved summary output, removal of the plyr dependency, a rebuilt Shiny interface using standard elements after the sortable drag-and-drop proved unstable, and a change of maintainer to Johannes Titz. The most recent release is a one-line patch fixing degrees of freedom in the t-test table.
Algorithm-agnostic variable importance, settled since 2022 and now answering CRAN checks
vimp performs inference on variable importance measures that do not depend on the fitting algorithm, using sample-splitting so tests stay valid under the zero-importance null. The statistical design settled in 2022: predictiveness measures gained their own S3 class, point estimation was decoupled from inference through the final_point_estimate argument, and method and family moved to the outer functions so binary outcomes work. The two 2025 releases are a CRAN documentation fix and an edge-case correction for cutoff-based measures when every prediction is the same value.
cofad performs contrast analyses for factorial designs in both between- and within-subject forms, and ships a Shiny GUI alongside the R interface. The 0.3.0 release in 2024 was the substantial one: a helper for calculating differences between two sets of lambdas for competing contrast analysis, improved summary output, removal of the plyr dependency, a rebuilt Shiny interface using standard elements after the sortable drag-and-drop proved unstable, and a change of maintainer to Johannes Titz. The most recent release is a one-line patch fixing degrees of freedom in the t-test table.
Development is slow and correctness-led. The record runs from a JOSS publication in 2021 through a near three-year gap to a release that both extended the method and repaired the GUI, then a degrees-of-freedom fix. Maintainer and author order changed in 0.3.0, which typically marks a handover rather than a burst of new work, and the cadence since is consistent with that.
Expect low-frequency correctness releases; the competing contrast analysis helper added in 0.3.0 is the most likely thing to be extended if anything is.
vimp performs inference on variable importance measures that do not depend on the fitting algorithm, using sample-splitting so tests stay valid under the zero-importance null. The statistical design settled in 2022: predictiveness measures gained their own S3 class, point estimation was decoupled from inference through the final_point_estimate argument, and method and family moved to the outer functions so binary outcomes work. The two 2025 releases are a CRAN documentation fix and an edge-case correction for cutoff-based measures when every prediction is the same value.
Substantive development ended in 2022, followed by one narrow addition — a cluster bootstrap for correlated data in 2023 — and two housekeeping releases. What remains visible are careful decisions about the boundary between estimation and inference, including the warning that a Wald interval will not be centred on the point estimate when the full-data or averaged option is used. The maintainer is keeping the package correct and installable rather than extending it.
Expect maintenance releases keyed to CRAN check changes; new predictiveness measures are the plausible extension, since the S3 class added in 2.3.0 was introduced specifically to make adding them simpler.
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 cofad or vimp.
Buildkite keeps converting hand-rolled agent workarounds into first-class CI primitives.
Cursor's agents stop waiting to be asked - they subscribe, and they hold a goal until it's done.
Nexus does the diagnosis; the agent is now reaching into the status page too.
Warp turned its quarter of software-factory essays into infrastructure you can buy.
Okta's developer blog is a Cross App Access campaign, now diluted by advocacy-team storytelling.
A leaf-temperature model that finished its job in 2020 and has stayed finished
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — maintenance — within Infra & APIs. cofad and vimp are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. cofad and vimp are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top cofad alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "cofad alternatives" section above for the current picks, or visit /alternatives/cofad for the full list with editorial commentary on each.
Top vimp alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "vimp alternatives" section above for the current picks, or visit /alternatives/vimp for the full list with editorial commentary on each.