Traefik
Traefik's 2.11 line spends August fixing the names it generates for Kubernetes resources.
A side-by-side editorial comparison of JointFPM and vcfR — release velocity, themes, recent moves, and the top alternatives to consider.
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.
A genomics workhorse whose visible release feed stops dead in mid-2020.
vcfR reads, manipulates and visualises VCF files, the standard format for genomic variant calls, and bridges them into R population-genetics classes such as genind, genlight and DNAbin. The three entries available here all come from the first half of 2020 and stop there, so the feed shows the state of the package six years ago rather than today.
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.
vcfR reads, manipulates and visualises VCF files, the standard format for genomic variant calls, and bridges them into R population-genetics classes such as genind, genlight and DNAbin. The three entries available here all come from the first half of 2020 and stop there, so the feed shows the state of the package six years ago rather than today.
Within that window the direction is unmistakably consolidation, not growth. 1.9.0 pushed error handling down into the C++ layer that actually reads the VCF so failures surface earlier and shared files stop tripping a readability pre-check, tightened class checks, and added conversion options. The two releases after it exist only to keep pace with R 4.0.0 and dplyr 1.0.0. Any development after June 2020 is not visible in this feed, so the current trajectory cannot be read from it.
No prediction can be grounded in these entries — the feed has been silent for six years, which points at a stale or broken source rather than at a package that stopped.
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 JointFPM or vcfR.
Traefik's 2.11 line spends August fixing the names it generates for Kubernetes resources.
nginx returns to feature work with PROXY v2 upstream writes, and quietly adds JSON to core.
ESPHome closes the 2026.8 cycle, but the release body is a bare link to the real notes.
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.
See all JointFPM alternatives → · See all vcfR alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. JointFPM and vcfR 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. JointFPM and vcfR 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 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.
Top vcfR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "vcfR alternatives" section above for the current picks, or visit /alternatives/vcfr for the full list with editorial commentary on each.