← Back to home
Comparison · Infra & APIs

CBTF vs estimatr

A side-by-side editorial comparison of CBTF and estimatr — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-package

CBTF vs estimatr: at a glance

FeatureCBTFestimatr
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themestesting, fuzzing, r-package, developer-toolscausal-inference, experiments, robust-standard-errors, econometrics
Last editorial update1h ago1d ago
WebsiteVisit →Visit →

What is CBTF?

A fuzzer for R packages that grew from one argument at a time to parallel runs across whole namespaces.

CBTF throws deliberately problematic inputs at exported functions and reports which ones error, warn, or survive. It now covers 85 input classes, fuzzes multiple named arguments per call, runs in parallel with a per-function timeout, and reports results as a classed object with print, summary, length, and whitelist methods for pruning false positives. Output control has been refined repeatedly — the latest release adds grouping by input or by function and a summary-only mode.

Read the full CBTF trajectory →

What is estimatr?

Fast design-based estimators for experiments, coasting on CRAN patches.

estimatr provides the design-based regression estimators the DeclareDesign ecosystem is built on — robust and cluster-robust standard errors, blocked and clustered randomization inference — implemented for speed rather than generality. The last three releases carry no substantive notes: each is a merge commit for a CRAN patch, one of them accompanied by a typo fix.

Read the full estimatr trajectory →

CBTF vs estimatr: editorial side-by-side

C
CBTF
INFRA · APIS
0.0

A fuzzer for R packages that grew from one argument at a time to parallel runs across whole namespaces.

◆ Current state

CBTF throws deliberately problematic inputs at exported functions and reports which ones error, warn, or survive. It now covers 85 input classes, fuzzes multiple named arguments per call, runs in parallel with a per-function timeout, and reports results as a classed object with print, summary, length, and whitelist methods for pruning false positives. Output control has been refined repeatedly — the latest release adds grouping by input or by function and a summary-only mode.

◆ Where it's heading

The package has moved from a script-shaped tool to a test-suite component. The single-argument, sequential fuzz() of the early releases could not finish a large namespace or survive a function that simply hangs; the mirai rewrite fixed both, and multi-argument support widened what a run can actually reach. Nearly everything since has gone into making results triageable rather than merely produced: whitelisting, result classes, grouping, and terminal output that fits real function signatures. Note that the 0.1.0 through 0.3.0 entries carry backfilled timestamps recorded in reverse order within under a minute, so their published dates do not reflect release order.

◆ Prediction

The steady expansion of the input catalogue from 70 to 85 with a new time class suggests more input classes are the cheapest next win; the reporting surface is now detailed enough that machine-readable output for CI would be the natural follow-on.

E
estimatr
INFRA · APIS
0.0

Fast design-based estimators for experiments, coasting on CRAN patches.

◆ Current state

estimatr provides the design-based regression estimators the DeclareDesign ecosystem is built on — robust and cluster-robust standard errors, blocked and clustered randomization inference — implemented for speed rather than generality. The last three releases carry no substantive notes: each is a merge commit for a CRAN patch, one of them accompanied by a typo fix.

◆ Where it's heading

Direction cannot be read from this feed. The release notes are unedited merge-commit messages, so the only signal is cadence — roughly annual, each release framed as a CRAN patch rather than as feature work. That pattern is consistent with a package whose estimators are considered finished and which now moves only when CRAN policy requires it.

◆ Prediction

On the evidence here the next release is another CRAN compliance patch, but the notes are too thin to support a confident read of what the maintainers are actually working on.

Alternatives to CBTF and estimatr

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 CBTF or estimatr.

See all CBTF alternatives → · See all estimatr alternatives →

Recent activity from CBTF and estimatr

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1mo agoCBTFTime inputs added; results groupable by input or function
  2. 6mo agoCBTFParallel fuzzing with timeouts, and multi-argument support
  3. 0y agoCBTFWhitelisting for false positives, plus clearer result semantics
  4. 1y agoCBTFFunction discovery skips unfuzzable functions; failures no longer crash
  5. 1y agoCBTFFirst release; notes carry only a website link
  6. 1y agoCBTFRaw results returned as an object with summary and print methods
  7. 1y agoestimatrCRAN version 1.0.4
  8. 2y agoestimatrCRAN version 1.0.2
  9. 3y agoestimatrCRAN version 1.0.0

Frequently asked questions

What is the difference between CBTF and estimatr?

Both compete on the same themes — r-package — within Infra & APIs. CBTF and estimatr 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.

Is CBTF better than estimatr?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. CBTF and estimatr 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 Infra & APIs products to evaluate alongside.

What are the best alternatives to CBTF?

Top CBTF alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "CBTF alternatives" section above for the current picks, or visit /alternatives/caught-by-the-fuzz for the full list with editorial commentary on each.

What are the best alternatives to estimatr?

Top estimatr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "estimatr alternatives" section above for the current picks, or visit /alternatives/estimatr for the full list with editorial commentary on each.