webchem
Adding chemical databases with one hand while public ones close programmatic access with the other.
A side-by-side editorial comparison of cfr and lobstr — release velocity, themes, recent moves, and the top alternatives to consider.
cfr packaged delay-corrected severity estimation, then went quiet on maintenance.
The package estimates disease severity and case ascertainment while correcting for the delay between a case being reported and its outcome being known. After the 0.1.1 rework of the estimation internals and a maintainer handover to Adam Kucharski, activity dropped to a vignette and an R-devel compatibility patch in February 2025.
R's object inspector is losing its view of the internals as CRAN closes off the private C API.
lobstr exposes R's internal object representation — sizes, addresses, reference counts, abstract syntax trees. Its two most recent releases are both driven by R's move to a restricted public C API: 1.1.3 stopped reporting a vector's truelength and reworked the reference indicator into refs:n, and 1.2.0 changed what sxp(expand = "environment") shows in order to stay compliant. 1.2.0 also adds src() for exploring srcref objects.
The package estimates disease severity and case ascertainment while correcting for the delay between a case being reported and its outcome being known. After the 0.1.1 rework of the estimation internals and a maintainer handover to Adam Kucharski, activity dropped to a vignette and an R-devel compatibility patch in February 2025.
The methodological work is done and consolidated: likelihood approximation is now selected automatically from outbreak size and an initial severity estimate, and the internals were renamed with a dot prefix to close the public surface down to cfr_static(), cfr_rolling() and the data-preparation generic. Releases since have been documentation and compatibility only.
The 0.1.0 notes flagged time-varying ascertainment as future work and it has not appeared in the two releases since; nothing in these entries indicates when or whether it lands.
lobstr exposes R's internal object representation — sizes, addresses, reference counts, abstract syntax trees. Its two most recent releases are both driven by R's move to a restricted public C API: 1.1.3 stopped reporting a vector's truelength and reworked the reference indicator into refs:n, and 1.2.0 changed what sxp(expand = "environment") shows in order to stay compliant. 1.2.0 also adds src() for exploring srcref objects.
The package is being rebuilt inside a shrinking window of what R permits. Each release trades some introspection depth for API conformance while trying to keep the diagnostic value intact — showing promise expressions instead of internal frame structures, replacing named with a documented refs scale. Where the constraint does not bite, development continues normally: src() is genuinely new, and the environment-binding fixes remove long-standing errors on for-loop and immediate bindings.
Expect further conformance work, since the notes describe it as ongoing, with any remaining non-API-dependent readouts either reworked or dropped as R tightens further.
Other Analytics 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 cfr or lobstr.
Adding chemical databases with one hand while public ones close programmatic access with the other.
The spatiotemporal companion to sf, moving at the pace of the packages around it.
An interface to Europe's long-term ecosystem research network that went quiet after 2.0.
Spatial model assessment that spent the last year on cross-platform arithmetic and CRAN rules.
Stopped trusting the cloud to prepare its taxonomic databases and does the conversion locally.
Went from estimating felling dates to doing the crossdating that produces them.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. cfr and lobstr 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. cfr and lobstr 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 Analytics products to evaluate alongside.
Top cfr alternatives in Analytics are ranked by recent ship velocity. Browse the "cfr alternatives" section above for the current picks, or visit /alternatives/cfr for the full list with editorial commentary on each.
Top lobstr alternatives in Analytics are ranked by recent ship velocity. Browse the "lobstr alternatives" section above for the current picks, or visit /alternatives/lobstr for the full list with editorial commentary on each.