monitOS
monitOS relicenses to MIT, the clearest signal in a sparse Novartis release feed.
A side-by-side editorial comparison of filtro and npi — release velocity, themes, recent moves, and the top alternatives to consider.
filtro moves to S7 and multiplies its feature-scoring methods in a single release.
filtro supplies feature-selection filter scores for the tidymodels stack. Version 0.2.0 adds five scoring methods — correlation, random forest importance, information gain, ROC AUC and cross tabulation — and moves the package from S3 to S7. It also gains a ranking layer: show_best_score_* and rank_best_score_* helpers for a single score, plus desirability-function helpers for optimising across several scores at once.
An R client for the US provider registry, tightening its types and edge-case handling
npi wraps the US National Provider Identifier registry API for R users, covering search, validation and summarisation of provider records. The one release in view is a consolidation pass rather than new surface: input normalisation, vectorised validation, and a typed empty result instead of an ambiguous one when a search finds nothing.
filtro supplies feature-selection filter scores for the tidymodels stack. Version 0.2.0 adds five scoring methods — correlation, random forest importance, information gain, ROC AUC and cross tabulation — and moves the package from S3 to S7. It also gains a ranking layer: show_best_score_* and rank_best_score_* helpers for a single score, plus desirability-function helpers for optimising across several scores at once.
The package is being built out on two axes at once — the catalogue of scores, and the machinery for choosing between them. The desirability functions are the more telling half, since they assume users will filter on several criteria rather than one. Adopting S7 while still pre-1.0 suggests the object model is being settled before the API is frozen.
Expect more scoring methods on the same S7 interface and a 1.0 release once the score and ranking APIs stop moving; the ranking helpers' naming is the most likely thing to change first.
npi wraps the US National Provider Identifier registry API for R users, covering search, validation and summarisation of provider records. The one release in view is a consolidation pass rather than new surface: input normalisation, vectorised validation, and a typed empty result instead of an ambiguous one when a search finds nothing.
The work is aimed at making the package behave predictably inside larger pipelines. Returning a typed empty `npi_results` object on no matches, and having `npi_is_valid()` accept vectors and return logical vectors, both remove branches a caller would otherwise write by hand. The bug fix follows the same line — `npi_summarize()` no longer drops input rows when a record's nested address or taxonomy data is missing.
With a single release visible there is not enough of a pattern to predict a direction confidently; the changes here suggest continued interface tidying rather than new API coverage, but that is one data point.
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 filtro or npi.
monitOS relicenses to MIT, the clearest signal in a sparse Novartis release feed.
kernelshap makes permutation SHAP practical past eight features, then fixes the kernel weights it had wrong.
modeltime.resample exists to keep backtesting working as tidymodels shifts underneath it.
modeltime.ensemble wakes after four years, and the work is all tune 2.0 compatibility.
shapviz refines its SHAP plots release by release while chasing ggplot2's moving target.
hstats settled into maintenance after its 1.0 restructuring, with model coverage the only thing still growing.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. filtro and npi are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. filtro and npi are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top filtro alternatives in Analytics are ranked by recent ship velocity. Browse the "filtro alternatives" section above for the current picks, or visit /alternatives/filtro-r for the full list with editorial commentary on each.
Top npi alternatives in Analytics are ranked by recent ship velocity. Browse the "npi alternatives" section above for the current picks, or visit /alternatives/npi-r for the full list with editorial commentary on each.