finnts
Microsoft's automated forecasting framework, still mostly a one-maintainer effort.
Comparison · Infra & APIs
adjustedCurves vs Biome
A side-by-side editorial comparison of adjustedCurves and Biome — release velocity, themes, recent moves, and the top alternatives to consider.
adjustedCurves vs Biome: at a glance
What is adjustedCurves?
A survival curve package spending release after release correcting its own estimates
adjustedCurves computes confounder-adjusted survival and cumulative incidence curves across a range of estimators - IPTW, AIPTW, Aalen-Johansen, direct standardisation - with support for multiple imputation and bootstrapping. The recent releases are dominated by corrections to numbers the package already reported. Version 0.11.4 fixed cumulative incidence estimates under method="aalen_johansen" that were being read one time step early, which the maintainer notes could differ substantially when events are few, and added risk and event counts to the ggsurvplot conversion including correctly pooled values under multiple imputation.
What is Biome?
Biome's weekly patches keep widening past JavaScript, with Tailwind the deepest thread.
Biome ships a 2.5.x patch roughly weekly, each carrying a handful of nursery rules and a long tail of formatter and parser fixes. The rule set now reaches well past JavaScript — CSS, HTML, Svelte, Vue, Astro and Tailwind all get attention inside a single release. Type-aware rules remain the expensive part, and their performance is tuned in nearly every patch.
adjustedCurves vs Biome: editorial side-by-side
adjustedCurves
0.0INFRA · APIS
A survival curve package spending release after release correcting its own estimates
◆ Current state
adjustedCurves computes confounder-adjusted survival and cumulative incidence curves across a range of estimators - IPTW, AIPTW, Aalen-Johansen, direct standardisation - with support for multiple imputation and bootstrapping. The recent releases are dominated by corrections to numbers the package already reported. Version 0.11.4 fixed cumulative incidence estimates under method="aalen_johansen" that were being read one time step early, which the maintainer notes could differ substantially when events are few, and added risk and event counts to the ggsurvplot conversion including correctly pooled values under multiple imputation.
◆ Where it's heading
Multiple imputation is the recurring fault line. The standard error pooling formula was implemented incorrectly until 0.11.2, then fixed again in 0.11.3 for the bootstrapping-plus-imputation combination, and 0.11.4 added the pooled risk table values that had previously been omitted entirely. A separate thread quietly removed capability: tmle and ostmle methods went in 0.10.0, and tmle support was pulled again in 0.11.1 after the concrete package left CRAN. Feature work does happen - risk tables, contrast arguments, the extend_to_last control on IPTW curves - but it is outweighed by correction.
◆ Prediction
Expect continued estimator-level corrections rather than new methods, and a possible return of tmle support if its upstream dependency returns to CRAN, since the removal was described as temporary.
Biome
5.0INFRA · APIS
Biome's weekly patches keep widening past JavaScript, with Tailwind the deepest thread.
◆ Current state
Biome ships a 2.5.x patch roughly weekly, each carrying a handful of nursery rules and a long tail of formatter and parser fixes. The rule set now reaches well past JavaScript — CSS, HTML, Svelte, Vue, Astro and Tailwind all get attention inside a single release. Type-aware rules remain the expensive part, and their performance is tuned in nearly every patch.
◆ Where it's heading
Two expansions run at once: the languages Biome understands, and the depth of its Tailwind class parser, which has gone from flagging arbitrary values to parsing container-query variants, combinator selectors, bare-utility modifiers and the legacy important marker. Nursery is the staging area, and rules are accumulating there faster than they graduate. The HTML formatter is still absorbing whitespace edge cases, which is where a formatter earns the trust to be run on write.
◆ Prediction
The Tailwind parser work is close to supporting a coherent class sorting and linting story rather than isolated rules, and the nursery backlog will need a graduation pass before the next minor.
Alternatives to adjustedCurves and Biome
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 adjustedCurves or Biome.
BayLum
Bayesian luminescence dating that finally replaced its folder-structure input format.
daedalus
An epidemic-economic model teaching its interventions to react to the outbreak itself.
bkmrhat
A parallel-chain helper for bkmr that has settled into pure upkeep.
driveR
A cancer driver prioritization package that ships rarely and mostly to stay installable
metR
A meteorology ggplot2 extension where the netCDF reader became the main event
See all adjustedCurves alternatives → · See all Biome alternatives →
Recent activity from adjustedCurves and Biome
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 16h agoBiomeTailwind parser deepens; five nursery rules land
- 7d agoBiomeReact Compiler rule lands; HTML style attributes lint as CSS
- 14d agoBiomeTailwind arbitrary values and noExtendNative join the rule set
- 21d agoBiomenoMisusedPromises performance regression fixed
- 28d agoBiomeBigint switch cases fixed; partial-type diagnostics suppressed
- 1mo agoBiomeAccessibility fixes; noCommentText autofix no longer hangs
- 6mo agoadjustedCurvesOff-by-one-step error corrected in cumulative incidence estimates
- 1y agoadjustedCurvesIPTW curves can now extend to the last observed time
- 2y agoadjustedCurvesDropped arguments and a wrong multiple-imputation pooling formula
- 2y agoadjustedCurvesRisk tables, contrast consolidation and faster bootstrapping
- 3y agoadjustedCurvestmle and ostmle methods dropped
- 3y agoadjustedCurvesDependency compatibility and installation documentation
Frequently asked questions
What is the difference between adjustedCurves and Biome?
They serve adjacent needs but don't currently overlap on shipped themes. Biome is currently shipping more aggressively (velocity 5.0 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 adjustedCurves better than Biome?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Biome is currently shipping more aggressively (velocity 5.0 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 adjustedCurves?
Top adjustedCurves alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "adjustedCurves alternatives" section above for the current picks, or visit /alternatives/adjustedcurves for the full list with editorial commentary on each.
What are the best alternatives to Biome?
Top Biome alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Biome alternatives" section above for the current picks, or visit /alternatives/biome for the full list with editorial commentary on each.