exametrika
A test-theory package that grew into a graphical-model toolkit, now spending its releases paying down the API debt that growth created.
Comparison · Infra & APIs
bolasso vs dqcheckr
A side-by-side editorial comparison of bolasso and dqcheckr — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
bolasso vs dqcheckr: at a glance
What is bolasso?
Bootstrap lasso got a fast mode, a second selection rule, and multinomial support
bolasso implements the bootstrapped lasso, refitting a regularized regression across bootstrap replicates and selecting variables by how consistently they survive. The 0.3.0 release reshaped it: a fast argument computes one cross-validated lambda on the full dataset instead of cross-validating inside every replicate, and selected_variables() gained a choice between the variable inclusion probability rule and a quantile rule based on bootstrap confidence intervals. Since then 0.4.0 exposed the bootstrap indices through bootstrap_samples(), and 0.5.0 extended the whole surface to multinomial responses, returning one list element per outcome level.
What is dqcheckr?
dqcheckr adds drift analysis, then removes the YAML a user had to hand-write.
dqcheckr runs configurable data-quality checks over files and DuckDB tables, driven by YAML dataset configs and recording results as snapshots. The 0.2.0 release added the ability to compare two historical snapshots and report per-column statistical drift, schema changes and trend charts, extending the tool from point-in-time checking into change over time. The most recent tag, 0.3.0, attacks the other friction point by generating the config itself from a sniff pass over the data.
bolasso vs dqcheckr: editorial side-by-side
bolasso
0.0INFRA · APIS
Bootstrap lasso got a fast mode, a second selection rule, and multinomial support
◆ Current state
bolasso implements the bootstrapped lasso, refitting a regularized regression across bootstrap replicates and selecting variables by how consistently they survive. The 0.3.0 release reshaped it: a fast argument computes one cross-validated lambda on the full dataset instead of cross-validating inside every replicate, and selected_variables() gained a choice between the variable inclusion probability rule and a quantile rule based on bootstrap confidence intervals. Since then 0.4.0 exposed the bootstrap indices through bootstrap_samples(), and 0.5.0 extended the whole surface to multinomial responses, returning one list element per outcome level.
◆ Where it's heading
The package spent 2022 dormant after its initial releases and has been actively developed since late 2024, moving from a single algorithm toward a workbench. The additions cluster around inspection rather than estimation: tidy() for bootstrap-level coefficients, plot_selection_thresholds() for selection stability across thresholds, plot_selected_variables() for the surviving covariates, and now the extracted bootstrap indices. Documented gaps remain, with mgaussian unsupported and multinomial prediction limited to class output.
◆ Prediction
The two stated limitations in 0.5.0 - no mgaussian family and class-only multinomial prediction - are the most likely next targets, since the maintainer flagged both as possible later additions.
dqcheckr
2.5INFRA · APIS
dqcheckr adds drift analysis, then removes the YAML a user had to hand-write.
◆ Current state
dqcheckr runs configurable data-quality checks over files and DuckDB tables, driven by YAML dataset configs and recording results as snapshots. The 0.2.0 release added the ability to compare two historical snapshots and report per-column statistical drift, schema changes and trend charts, extending the tool from point-in-time checking into change over time. The most recent tag, 0.3.0, attacks the other friction point by generating the config itself from a sniff pass over the data.
◆ Where it's heading
Both moves point the same way: reduce what the operator has to write and know. Config generation removes the hand-authored YAML that gated first use, list_runs() and validate_config() make an existing setup inspectable, and the snapshot comparison turns accumulated run history into a second product surface. Check coverage keeps widening underneath — outlier detection, composite keys, row-count and file-size ceilings — and the reporting layer moved from rmarkdown to Quarto, with existing 0.1.x databases auto-migrated on first run.
◆ Prediction
Expect the generated configs and the drift reports to converge, so a sniffed config can seed thresholds from the snapshot history rather than from defaults, plus continued growth in the numbered QC check catalogue.
Alternatives to bolasso and dqcheckr
Other Infra & APIs 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 bolasso or dqcheckr.
nuggets
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
projoint
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
eratosthenes
eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.
lifecontingencies
An actuarial mainstay spends its releases on CI plumbing, not on new mathematics.
EDAForge
EDAForge is a data-quality auditor renamed mid-flight, still finding its CRAN footing.
See all bolasso alternatives → · See all dqcheckr alternatives →
Recent activity from bolasso and dqcheckr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 24d agodqcheckrConfig generation from data sniffing; run listing added
- 2mo agodqcheckrDuckDB CSV ingestion fixed for undetectable delimiters
- 2mo agodqcheckrSnapshot drift analysis arrives; reports move to Quarto ⚡
- 4mo agobolassoMultinomial responses supported across selection and plotting
- 10mo agobolassoBootstrap indices exposed via bootstrap_samples()
- 1y agobolassoFast estimation mode and a second variable selection rule ⚡
- 4y agobolassoBolasso v0.2.0
- 4y agobolassoBolasso v0.1.0
Frequently asked questions
What is the difference between bolasso and dqcheckr?
Both compete on the same themes — r-package — within Infra & APIs. dqcheckr 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.
Is bolasso better than dqcheckr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dqcheckr 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 Infra & APIs products to evaluate alongside.
What are the best alternatives to bolasso?
Top bolasso alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "bolasso alternatives" section above for the current picks, or visit /alternatives/bolasso for the full list with editorial commentary on each.
What are the best alternatives to dqcheckr?
Top dqcheckr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "dqcheckr alternatives" section above for the current picks, or visit /alternatives/dqcheckr for the full list with editorial commentary on each.