TAF
TAF keeps turning ICES stock assessments into reproducible, dependency-pinned projects.
A side-by-side editorial comparison of epikit and Fluent Bit — release velocity, themes, recent moves, and the top alternatives to consider.
epikit narrows to field-epidemiology helpers, handing proportions to a sibling package
epikit is a set of small helpers for applied epidemiology in R — age categorisation, date reconstruction from partial records, and related field-data chores, developed in the R4Epis orbit. Version 0.2.0 moved the proportion functions out to epitabulate, improved how find_date_cause(), find_start_date() and find_end_date() handle dates falling outside the period, and added a floor argument to age_categories() so the lowest band reads as under one rather than zero to zero.
Fluent Bit keeps two lines alive while the 5.x branch quietly opens 5.1.
Three release lines are visible at once. The 4.2 branch takes backported fixes — Stackdriver payload over-reads, Avro empty-map handling, Windows event-log enrichment. The 5.0 line carries the forward work. And a 5.1 line has appeared with two tags whose titles are raw commit messages about test changes, which is what this repository produces when a tag is cut off a routine commit rather than a prepared release.
epikit is a set of small helpers for applied epidemiology in R — age categorisation, date reconstruction from partial records, and related field-data chores, developed in the R4Epis orbit. Version 0.2.0 moved the proportion functions out to epitabulate, improved how find_date_cause(), find_start_date() and find_end_date() handle dates falling outside the period, and added a floor argument to age_categories() so the lowest band reads as under one rather than zero to zero.
The package is being scoped down rather than built out. The 0.1.3 restructuring and the 0.2.0 handover of proportions to epitabulate are the same move made twice: push functionality into the package where it belongs and keep epikit to the toolkit that field epidemiologists reach for directly. The rest of the history is dependency compatibility work against dplyr and tibble.
With proportions gone and dependencies trimmed, the remaining functions cluster tightly around dates and age bands, so further refinement of the date-reconstruction helpers is more likely than new capability areas.
Three release lines are visible at once. The 4.2 branch takes backported fixes — Stackdriver payload over-reads, Avro empty-map handling, Windows event-log enrichment. The 5.0 line carries the forward work. And a 5.1 line has appeared with two tags whose titles are raw commit messages about test changes, which is what this repository produces when a tag is cut off a routine commit rather than a prepared release.
The engineering emphasis on the maintained branches is memory safety and protocol correctness in the input and output plugins: use-after-free in in_forward, over-reads in out_stackdriver, endian-safe gzip magic reads, oauth2 token parsing hardening. That is the profile of a project whose failure mode is a crash in someone else's log pipeline, and it is being worked systematically rather than opportunistically.
Expect the 4.2 backport stream to continue at roughly monthly cadence and the 5.1 line to keep accumulating commit-titled tags until a prepared announcement release appears with real notes.
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 epikit or Fluent Bit.
TAF keeps turning ICES stock assessments into reproducible, dependency-pinned projects.
parallelDist is in pure preservation mode — one build fix every few years.
Cairo finally catches R's graphics engine, all the way to GE API 16.
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
SimInf 10.0 turns an epidemic simulator into a tool that fits models to real time series
A young package porting Stata's egen row-wise helpers to the tidyverse, one function per release
See all epikit alternatives → · See all Fluent Bit alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Fluent Bit 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Fluent Bit 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 Analytics products to evaluate alongside.
Top epikit alternatives in Analytics are ranked by recent ship velocity. Browse the "epikit alternatives" section above for the current picks, or visit /alternatives/epikit-r for the full list with editorial commentary on each.
Top Fluent Bit alternatives in Analytics are ranked by recent ship velocity. Browse the "Fluent Bit alternatives" section above for the current picks, or visit /alternatives/fluent-bit for the full list with editorial commentary on each.