vcfR
A genomics workhorse whose visible release feed stops dead in mid-2020.
A side-by-side editorial comparison of multimark and powerly — release velocity, themes, recent moves, and the top alternatives to consider.
Five years of compiler and CRAN fixes on a capture-recapture package.
multimark fits capture-mark-recapture models for populations sampled with multiple non-invasive marks, including a spatial variant. Nothing in the visible history changes the models. Every recent release responds to something outside the package: a CRAN check, a compiler flag, or an upstream package that stopped exporting a function.
A dormant sample-size package woke up in 2025 with parallel backends and a three-release DOI farce.
powerly implements a simulation-based method for choosing sample sizes in psychological network models. It sat untouched from September 2022 until August 2025, then shipped five releases in two days. v1.10.0 is the substantive one: parabar parallel backends with progress tracking, validation restricted to specific sample sizes, and warnings when the user picks argument values the method cannot support.
multimark fits capture-mark-recapture models for populations sampled with multiple non-invasive marks, including a spatial variant. Nothing in the visible history changes the models. Every recent release responds to something outside the package: a CRAN check, a compiler flag, or an upstream package that stopped exporting a function.
This is preservation rather than development. The one substantive entry, in 2021, corrected an MCMC error in multimarkClosedSCR() serious enough that the author told users to revisit past analyses; everything since has been keeping the C code compiling across platforms. Release intervals now stretch to years.
Expect the pattern to hold, with a release whenever a toolchain or upstream dependency forces one and no change to the samplers.
powerly implements a simulation-based method for choosing sample sizes in psychological network models. It sat untouched from September 2022 until August 2025, then shipped five releases in two days. v1.10.0 is the substantive one: parabar parallel backends with progress tracking, validation restricted to specific sample sizes, and warnings when the user picks argument values the method cannot support.
The reawakening tracks the underlying manuscript reaching publication — v1.9.0 is largely citation, DOI, and website work around a published paper, with CI and documentation debt cleared at the same time. Feature work resumed only after that housekeeping, and it points at usability rather than method: better feedback, better progress reporting, the ability to validate one sample size instead of a whole grid. Three of the five 2025 releases exist only to fix a DOI in the package documentation, one of them undoing the previous one.
With the paper published and the parallel-backend request from issue #8 finally closed, further releases most likely continue the usability line — more guardrails on argument choice — rather than extending the statistical method itself.
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 multimark or powerly.
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 multimark alternatives → · See all powerly alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. multimark and powerly 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. multimark and powerly 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 multimark alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "multimark alternatives" section above for the current picks, or visit /alternatives/multimark for the full list with editorial commentary on each.
Top powerly alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "powerly alternatives" section above for the current picks, or visit /alternatives/powerly for the full list with editorial commentary on each.