Whatagraph
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
A side-by-side editorial comparison of Holistics and maplegend — release velocity, themes, recent moves, and the top alternatives to consider.
Holistics keeps fencing in the AI layer it spent the summer building.
Holistics ships small, frequent notes - often one or two sentences - across three strands: AI features in Explore and Chat, as-code control of presentation through AML, and workspace hygiene like file history and dark mode. The August entries are entirely about the AI layer's edges rather than its capabilities: an AI user attribute for restricting what the assistant can reach, and now redaction of the data it is allowed to see. Bodies are frequently a single line, so scope has to be read from the headline and the release-note URL.
The legend engine mapsf spun out, now covering legend types the parent map package can draw.
maplegend draws the legends for base-R thematic maps, extracted from mapsf so both packages could evolve the legend vocabulary independently. It has been catching up to the map types it has to serve: 0.6.0 added choro_point, choro_line, and choro_symb for choropleth legends rendered on circles, lines, and symbols, following the histogram legend type in 0.4.0. Considerable effort has gone into behaving correctly when the plot aspect ratio is not 1, which required refactoring most of the package in 0.4.0 and still produced a proportional-symbol segment sizing fix in 0.6.3.
Holistics ships small, frequent notes - often one or two sentences - across three strands: AI features in Explore and Chat, as-code control of presentation through AML, and workspace hygiene like file history and dark mode. The August entries are entirely about the AI layer's edges rather than its capabilities: an AI user attribute for restricting what the assistant can reach, and now redaction of the data it is allowed to see. Bodies are frequently a single line, so scope has to be read from the headline and the release-note URL.
The AI work has moved through a recognizable sequence: capability first with chart suggestions, then observability with AI Chat Insights for admins, then access control with an AI-specific user attribute, and now field-level redaction. Access control decides which rows the assistant can reach; redaction decides what it may see inside them - the same governance thread at finer grain. Alongside it, Holistics keeps pulling presentation into AML - custom charts, theme palettes, currency formats - so what analysts used to click is versioned as code.
With reach and visibility both now constrained, the remaining gap is accountability - logging what the assistant answered against which data - though the one-line release notes rarely signal scope far enough ahead to read the next step confidently.
maplegend draws the legends for base-R thematic maps, extracted from mapsf so both packages could evolve the legend vocabulary independently. It has been catching up to the map types it has to serve: 0.6.0 added choro_point, choro_line, and choro_symb for choropleth legends rendered on circles, lines, and symbols, following the histogram legend type in 0.4.0. Considerable effort has gone into behaving correctly when the plot aspect ratio is not 1, which required refactoring most of the package in 0.4.0 and still produced a proportional-symbol segment sizing fix in 0.6.3.
This is a support library whose backlog is defined by its caller. Every legend type mapsf can produce needs a matching legend renderer, and the release notes are dominated by spacing, offset, and border details — box_cex for symbol spacing, NA box placement in horizontal choropleth legends, text overflow when no_data is set. The shared vocabulary with mapsf is being maintained deliberately, with val_rnd, val_big, and val_dec propagating through legend types release by release. Version numbering is not monotonic in this feed, with 0.4.0 published seconds after 0.5.0.
Expect the remaining combined map types to acquire matching legends and the val_* formatting arguments to reach the types that still lack them.
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 Holistics or maplegend.
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
Lightdash keeps handing authoring to outside agents and keeping the governed layer for itself.
A 4.4.0 tag appears, but the feed carries only its release plumbing
distributions3 0.3.0 adds sample-based distributions and likelihood derivatives
Basedash keeps pushing its data out of the workspace — now to people without accounts
RStudio ships through release branches, and the notes are commit messages
See all Holistics alternatives → · See all maplegend alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Holistics 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. Holistics 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 Holistics alternatives in Analytics are ranked by recent ship velocity. Browse the "Holistics alternatives" section above for the current picks, or visit /alternatives/holistics for the full list with editorial commentary on each.
Top maplegend alternatives in Analytics are ranked by recent ship velocity. Browse the "maplegend alternatives" section above for the current picks, or visit /alternatives/maplegend for the full list with editorial commentary on each.