vcfR
A genomics workhorse whose visible release feed stops dead in mid-2020.
A side-by-side editorial comparison of multimark and plume — 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 niche R package for author bylines that keeps sanding down the edges of academic metadata.
plume builds author lists, affiliations, and CRediT contribution statements for R Markdown and Quarto documents. After a long stretch of small correctness releases through 2024, 0.3.0 in September 2025 broke the pattern with the largest feature batch since 0.2.0 — plain-function constructors, configurable symbols, and finer control over initials. The package covers one narrow job and covers it thoroughly.
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.
plume builds author lists, affiliations, and CRediT contribution statements for R Markdown and Quarto documents. After a long stretch of small correctness releases through 2024, 0.3.0 in September 2025 broke the pattern with the largest feature batch since 0.2.0 — plain-function constructors, configurable symbols, and finer control over initials. The package covers one narrow job and covers it thoroughly.
The release history reads as a slow campaign against edge cases in a domain full of them: authors with no roles, non-cased scripts, duplicate family names, YAML headers containing comments the writer must not destroy. Over 2024 nearly every release was a fix or a small parameter refinement, with PlumeQuarto steadily catching up to Quarto's own author schema. 0.3.0 shows the maintainer beginning to smooth the API itself rather than only its behaviour — aliases for the R6 constructors, deprecations moved to where they belong.
Expect continued tracking of Quarto's author-metadata schema as it changes upstream, and more API smoothing of the kind 0.3.0 started; the ORCID icon regression caused by Quarto's path resolution suggests upstream churn will keep setting the agenda.
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 plume.
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 plume 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 plume 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 plume 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 plume alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "plume alternatives" section above for the current picks, or visit /alternatives/plume for the full list with editorial commentary on each.