vcfR
A genomics workhorse whose visible release feed stops dead in mid-2020.
Comparison · Infra & APIs
inlabru vs plume
A side-by-side editorial comparison of inlabru and plume — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
inlabru vs plume: at a glance
What is inlabru?
A Bayesian spatial modelling package rebuilding its foundations one breaking release at a time
inlabru wraps INLA for spatial, point-process and latent-Gaussian models in R. It is mid-modernisation: since 2.12.0 cut the sp stack, each release has renamed part of the public surface, standardised how external packages attach custom mappers, or replaced internal machinery. 2.15.0 is the latest step, pairing a new predictor evaluation and linearisation implementation with broom's tidy(), glance() and augment() methods and four non-zero-truncated observation families.
What is plume?
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.
inlabru vs plume: editorial side-by-side
inlabru
2.5INFRA · APIS
A Bayesian spatial modelling package rebuilding its foundations one breaking release at a time
◆ Current state
inlabru wraps INLA for spatial, point-process and latent-Gaussian models in R. It is mid-modernisation: since 2.12.0 cut the sp stack, each release has renamed part of the public surface, standardised how external packages attach custom mappers, or replaced internal machinery. 2.15.0 is the latest step, pairing a new predictor evaluation and linearisation implementation with broom's tidy(), glance() and augment() methods and four non-zero-truncated observation families.
◆ Where it's heading
The arc is consolidation of the extension surface rather than expansion of the model catalogue. Every release adds mappers or families with one hand and removes a dependency, a re-export or a deprecated path with the other — plyr in 2.15.0, fmesher's Depends entry in 2.14.1, sp and ggmap in 2.12.0. The compatibility flag bru_compat_pre_2_14_enable and the temporary fm_int/fm_pixels re-exports show a maintainer sequencing breaks across releases instead of landing them together.
◆ Prediction
The 2.14 compatibility flag is still defaulting to TRUE and the fmesher re-exports are described in the entries as temporary, so the next obvious move is a release that flips bru_compat_pre_2_14_enable off and drops those re-exports.
plume
0.0INFRA · APIS
A niche R package for author bylines that keeps sanding down the edges of academic metadata.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to inlabru and plume
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 inlabru or plume.
dialr
The R phone-number package stopped only parsing numbers and started asking them where they are.
ggVennDiagram
A Venn diagram package whose public release notes say almost nothing — including about its copyright cleanup.
ordinalsimr
A Shiny app for choosing the right ordinal test reached CRAN in a single 90-minute burst of tags.
transltr
A new R localization package that reached CRAN and immediately downgraded itself to experimental.
hereR
An R client for HERE's location APIs, shaped almost entirely by what the vendor exposes next.
See all inlabru alternatives → · See all plume alternatives →
Recent activity from inlabru and plume
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 23d agoinlabruPredictor linearisation rewritten; broom tidiers, truncated families
- 3mo agoinlabruBugfix release: factor contrasts, raster extraction, error classes
- 5mo agoinlabruNew mappers, standardised cgeneric support, bru_obs storage refactor
- 10mo agoplumeFunction constructors, configurable symbols, and disambiguated initials
- 1y agoinlabruMapper classes shortened to bm_*, experimental predictor aggregation
- 1y agoinlabruDrops sp and ggmap for an sf-native spatial stack ⚡
- 1y agoplumeQuarto author schema coverage: degrees, group affiliations, .yaml files
- 2y agoplumeVignette expansion and a selection-helper import fix
- 2y agoplumeRole propagation in set_main_contributors, plus script-aware initials
- 2y agoplumeto_yaml stops clobbering headers with comments and custom tags
- 2y agoplumeCRediT author ordering fixed; format deprecated for suffix
Frequently asked questions
What is the difference between inlabru and plume?
Both compete on the same themes — r-package — within Infra & APIs. inlabru is currently shipping more aggressively (velocity 2.5 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.
Is inlabru better than plume?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. inlabru is currently shipping more aggressively (velocity 2.5 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.
What are the best alternatives to inlabru?
Top inlabru alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "inlabru alternatives" section above for the current picks, or visit /alternatives/inlabru for the full list with editorial commentary on each.
What are the best alternatives to plume?
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.