← Back to home
Comparison · Infra & APIs

CBTF vs eratosthenes

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

Shared themes:r-package

CBTF vs eratosthenes: at a glance

FeatureCBTFeratosthenes
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themestesting, fuzzing, r-package, developer-toolsarchaeology, bayesian-inference, mcmc, input-validation
Last editorial update57m ago2h 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 eratosthenes?

eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.

eratosthenes does Bayesian estimation of archaeological chronologies from relative sequences, absolute constraints and artifact assemblages. The 0.0.9 line built out the inference diagnostics — traceplots, histograms, batch-means MCSE reporting, displacement estimation — and then consolidated artifact probability-density estimation into a single gibbs_ad_type(). The 0.1.0 tag turns outward instead, adding validators for every user-supplied structure and replacing seq_check() with a more informative seq_diag().

Read the full eratosthenes trajectory →

CBTF vs eratosthenes: 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
eratosthenes
INFRA · APIS
2.5

eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.

◆ Current state

eratosthenes does Bayesian estimation of archaeological chronologies from relative sequences, absolute constraints and artifact assemblages. The 0.0.9 line built out the inference diagnostics — traceplots, histograms, batch-means MCSE reporting, displacement estimation — and then consolidated artifact probability-density estimation into a single gibbs_ad_type(). The 0.1.0 tag turns outward instead, adding validators for every user-supplied structure and replacing seq_check() with a more informative seq_diag().

◆ Where it's heading

The package is moving from research code to something a non-author can run. Consolidating estimation behind one function, then wrapping every input class in a validator, are the two steps that make failures legible instead of cryptic, and the diagnostics added earlier serve the same end for the sampler itself. Nothing in the window changes the underlying model; the work is all about making it usable and its output checkable.

◆ Prediction

With inputs validated and diagnostics in place, the next release is more likely to extend the constraint or assemblage modelling than to keep reworking the interface, though the feed's three sparse tags give little to read a cadence from.

Alternatives to CBTF and eratosthenes

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 eratosthenes.

See all CBTF alternatives → · See all eratosthenes alternatives →

Recent activity from CBTF and eratosthenes

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

  1. 10d agoeratosthenesInput validators added; seq_check() replaced by seq_diag()
  2. 1mo agoCBTFTime inputs added; results groupable by input or function
  3. 6mo agoCBTFParallel fuzzing with timeouts, and multi-argument support
  4. 0y agoCBTFWhitelisting for false positives, plus clearer result semantics
  5. 1y agoCBTFFunction discovery skips unfuzzable functions; failures no longer crash
  6. 1y agoCBTFFirst release; notes carry only a website link
  7. 1y agoCBTFRaw results returned as an object with summary and print methods
  8. 1y agoeratosthenesArtifact p.d.f. estimation consolidated into gibbs_ad_type()
  9. 1y agoeratosthenesMCMC diagnostics arrive: traceplots, histograms, batch-means MCSE

Frequently asked questions

What is the difference between CBTF and eratosthenes?

Both compete on the same themes — r-package — within Infra & APIs. eratosthenes 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 CBTF better than eratosthenes?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. eratosthenes 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 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 eratosthenes?

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