metatools
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
A side-by-side editorial comparison of nanonext and sivirep — release velocity, themes, recent moves, and the top alternatives to consider.
nanonext keeps shrinking its build requirements while adding messaging primitives.
The R binding to NNG ships roughly monthly. Since February the package added an HTTP server that can run synchronously or through the later event loop, a zero-copy device forwarder for building brokers and proxies, and support for pthread-enabled WebAssembly targets. Send operations now move the buffer straight into the NNG message, halving peak memory on serialized sends.
sivirep turned Colombia's SIVIGILA surveillance data into a one-call reporting package.
The 1.0.0 release of December 2024 is the substance of this feed: incidence calculation and plotting for the country, departments and municipalities, ethnicity and case-classification breakdowns, multi-year retrospectives, and a Reporte Evento template that assembles them. It was shaped by usability testing and expert review with Colombia's National Institute of Health. The two patches since are fixes, warnings and documentation.
The R binding to NNG ships roughly monthly. Since February the package added an HTTP server that can run synchronously or through the later event loop, a zero-copy device forwarder for building brokers and proxies, and support for pthread-enabled WebAssembly targets. Send operations now move the buffer straight into the NNG message, halving peak memory on serialized sends.
Two directions run in parallel. One is making the package installable anywhere — the build-time cmake dependency is gone, so compiling bundled NNG and Mbed TLS needs only a C compiler, and WebAssembly targets are supported. The other is raising the ceiling on what can be built on top: device_aio() for message forwarding, an HTTP and WebSocket server with a content map, and stream buffer control. Bug fixes in recent releases concentrate on memory safety in the bundled C sources.
Given the pace and the tight coupling declared in each release, expect the next version to track a mirai requirement and continue hardening the HTTP server paths that the last two releases have been leaking memory in.
The 1.0.0 release of December 2024 is the substance of this feed: incidence calculation and plotting for the country, departments and municipalities, ethnicity and case-classification breakdowns, multi-year retrospectives, and a Reporte Evento template that assembles them. It was shaped by usability testing and expert review with Colombia's National Institute of Health. The two patches since are fixes, warnings and documentation.
Work after 1.0.0 has gone into making the report template survive bad input rather than adding analyses — warnings when a municipality or department has no data, handlers that surface import and geo-filter errors during rendering, and an explicit note that first use of any import function needs an internet connection. English-language articles were added alongside the Spanish function interface.
Spanish-named functions paired with new English articles point at a widening audience; more translation of the guides looks likelier than new epidemiological methods.
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 nanonext or sivirep.
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.
R's object inspector is losing its view of the internals as CRAN closes off the private C API.
A weather-station data client that broke one return type to hand back distances instead of bare IDs.
giscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.
See all nanonext alternatives → · See all sivirep alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. nanonext is currently shipping more aggressively (velocity 2.5 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. nanonext is currently shipping more aggressively (velocity 2.5 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 nanonext alternatives in Analytics are ranked by recent ship velocity. Browse the "nanonext alternatives" section above for the current picks, or visit /alternatives/nanonext for the full list with editorial commentary on each.
Top sivirep alternatives in Analytics are ranked by recent ship velocity. Browse the "sivirep alternatives" section above for the current picks, or visit /alternatives/sivirep for the full list with editorial commentary on each.