pr2database
The protist reference database keeps widening past the rRNA gene it was built on.
A side-by-side editorial comparison of goat and JointFPM — release velocity, themes, recent moves, and the top alternatives to consider.
A gene-set enrichment package that outgrew its human-only origins, then went quiet.
GOAT is a CRAN-published R package for gene set enrichment testing, now at 1.1.4. The visible arc runs from a 2024 beta through a first public CRAN release to a 1.1 line that broadened the package past human gene sets and added persistence for completed analyses. Recent releases are small: the newest ships an igraph handle on plot_network() plus bug fixes.
Recurrent-event modelling settles, with mean_no() promoted to stable.
JointFPM fits joint flexible parametric models for a recurrent event process alongside a competing terminal event, and predicts the mean number of events. The visible history runs from bug fixes on the earliest CRAN releases through standardization, integration options and a summary method, ending with mean_no() declared stable. Several changes arrived through outside pull requests.
GOAT is a CRAN-published R package for gene set enrichment testing, now at 1.1.4. The visible arc runs from a 2024 beta through a first public CRAN release to a 1.1 line that broadened the package past human gene sets and added persistence for completed analyses. Recent releases are small: the newest ships an igraph handle on plot_network() plus bug fixes.
The substantive expansion happened in the 1.1 cycle; everything since has been maintenance and plotting ergonomics. Each release since 1.1 touches one function and returns something callers previously had to reconstruct, which reads as a package settling into a stable API and responding to individual user requests rather than pursuing new scope. The 13-month gap between 1.1.2 and 1.1.4 puts it firmly in low-cadence maintenance.
Expect continued point releases that expose internals from the plotting functions or refresh the bundled GO release, not new analysis capability. The entries give no signal of a planned 1.2.
JointFPM fits joint flexible parametric models for a recurrent event process alongside a competing terminal event, and predicts the mean number of events. The visible history runs from bug fixes on the earliest CRAN releases through standardization, integration options and a summary method, ending with mean_no() declared stable. Several changes arrived through outside pull requests.
The arc runs from a working estimator toward a usable one: input validation and error messages first, then control over the numerical integration, then a summary method and pass-through arguments to the underlying rstpm2 fit. The latest release adds no code so much as a stability commitment to a function users were already calling.
With mean_no() stable, the next work most likely targets the prediction and standardization paths rather than the model fit 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 goat or JointFPM.
The protist reference database keeps widening past the rRNA gene it was built on.
Composable aligned layouts, rebuilt on S7 while ggplot2 4.0 lands underneath.
Conservation planning absorbs the literature's target-setting rules as code.
Joint species distribution models in Gibbs-sampled C++, quiet since 2023.
An ecosystem model starts tracking carbon isotopes and land-use change.
Ten years in, US mapping splits its data out and finally adds Puerto Rico.
See all goat alternatives → · See all JointFPM alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. goat and JointFPM 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. goat and JointFPM 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 goat alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "goat alternatives" section above for the current picks, or visit /alternatives/goat for the full list with editorial commentary on each.
Top JointFPM alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "JointFPM alternatives" section above for the current picks, or visit /alternatives/jointfpm for the full list with editorial commentary on each.