fillpattern
Pattern fills for ggplot2, hardened against the ways users write sizes
A side-by-side editorial comparison of brglm2 and palettecore — release velocity, themes, recent moves, and the top alternatives to consider.
A bias-reduction package reaches 1.0 by adding an estimator built for high-dimensional logistic regression
brglm2 fits generalized linear models using mean and median bias reduction rather than plain maximum likelihood, which matters most when ML estimates are infinite or badly biased. The 0.7-0.9 line broadened coverage — negative binomial via brnb(), ordinal superiority measures, the expo() method for exponentiated parameters, add1()/drop1() so step() stops silently producing nonsense. Version 1.0.0 in August 2025 added mdyplFit(), estimating logistic regression by maximum Diaconis-Ylvisaker prior penalized likelihood with optional high-dimensional corrections. The two releases since have tuned that new path.
Accessible palettes generated from one seed, with every audit number computed on the hex you actually get
palettecore generates sequential, diverging and categorical colour palettes from a single seed using CIEDE2000 arc-length spacing in OKLCH, and audits each one for colour-vision-deficiency separation, greyscale survival, gamut and WCAG contrast. It exists as a numpy-only Python core and an R mirror validated hex-exact against shared parity fixtures, plus a CLI the project describes as its agent-friendly entry point. Four releases landed inside 24 hours in late July.
brglm2 fits generalized linear models using mean and median bias reduction rather than plain maximum likelihood, which matters most when ML estimates are infinite or badly biased. The 0.7-0.9 line broadened coverage — negative binomial via brnb(), ordinal superiority measures, the expo() method for exponentiated parameters, add1()/drop1() so step() stops silently producing nonsense. Version 1.0.0 in August 2025 added mdyplFit(), estimating logistic regression by maximum Diaconis-Ylvisaker prior penalized likelihood with optional high-dimensional corrections. The two releases since have tuned that new path.
The package's older work assumed the classical regime where observations comfortably outnumber parameters. mdyplFit() and its hd_correction argument target the opposite case, and the follow-up releases are almost entirely about it — Pearson residuals on original responses, aliased parameter handling, the sloe() signal-strength estimator ignoring leverage-one observations. Meanwhile the older surface gets graceful-failure work: brglm_fit() now returns its latest estimates with warnings rather than aborting.
Given that 1.0.1 and 1.1.0 are both dominated by mdyplFit follow-ups while the classical path receives only robustness fixes, further work on high-dimensional corrections is the likeliest direction.
palettecore generates sequential, diverging and categorical colour palettes from a single seed using CIEDE2000 arc-length spacing in OKLCH, and audits each one for colour-vision-deficiency separation, greyscale survival, gamut and WCAG contrast. It exists as a numpy-only Python core and an R mirror validated hex-exact against shared parity fixtures, plus a CLI the project describes as its agent-friendly entry point. Four releases landed inside 24 hours in late July.
The arc is about making the audit honest rather than making the palettes prettier. The 0.2.2 release, prompted by an external review, moved every diagnostic to compute on the 8-bit quantised hex codes actually returned rather than on internal floats — a change that flips results near thresholds and had been quietly overstating one deuteranopia score. The 0.4.0 helix kind and the vividness control extend the generator, but the same release also tightens its own claims, reframing helix as checked rather than assumed CVD-safe.
Given the pattern of auditing its own assertions, expect the next release to extend the cvd_luminance_monotonic diagnostic beyond helix to the other palette kinds.
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 brglm2 or palettecore.
Pattern fills for ggplot2, hardened against the ways users write sizes
gcube's recent releases are all packaging metadata, not simulation code
The R port of Quinlan's Cubist gets reproducibility fixes, not new modelling
ggstats keeps widening what a coefficient or Likert plot can be
ecodive rebuilt itself into a broad diversity-metric library, breaking as it went
State-space data simulation for R, filled in one function at a time
See all brglm2 alternatives → · See all palettecore alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. palettecore is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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. palettecore is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 brglm2 alternatives in Analytics are ranked by recent ship velocity. Browse the "brglm2 alternatives" section above for the current picks, or visit /alternatives/brglm2 for the full list with editorial commentary on each.
Top palettecore alternatives in Analytics are ranked by recent ship velocity. Browse the "palettecore alternatives" section above for the current picks, or visit /alternatives/palettecore for the full list with editorial commentary on each.