← Back to home
Comparison · Infra & APIs

CBTF vs gkwdist

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

Shared themes:r-package

CBTF vs gkwdist: at a glance

FeatureCBTFgkwdist
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themestesting, fuzzing, r-package, developer-toolsr-package, statistical-distributions, numerical-stability, mle
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 gkwdist?

gkwdist keeps finding that its distributions were returning the wrong numbers.

The package implements the Generalized Kumaraswamy distribution family and its sub-families. The current release fixes six numerical defects, the most serious being that dgkw() returned zero for every input because internal helpers collided with same-named functions in R's public Rmath.h header. Log-likelihoods for three sub-families were also wrong for data near zero due to clamping instead of working in log space.

Read the full gkwdist trajectory →

CBTF vs gkwdist: 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.

G
gkwdist
INFRA · APIS
2.5

gkwdist keeps finding that its distributions were returning the wrong numbers.

◆ Current state

The package implements the Generalized Kumaraswamy distribution family and its sub-families. The current release fixes six numerical defects, the most serious being that dgkw() returned zero for every input because internal helpers collided with same-named functions in R's public Rmath.h header. Log-likelihoods for three sub-families were also wrong for data near zero due to clamping instead of working in log space.

◆ Where it's heading

Every release in this window is correctness work with an unchanged public API — critical MLE fixes in 1.1.3, a CRAN timing-test patch in 1.1.4, numerical corrections in 1.1.5. The recurring theme is that analytically correct formulas were being defeated by implementation details: name collisions, sign errors returning negative infinity where positive was required, and clamping thresholds that destroyed precision in the tails. Test infrastructure added in 1.1.2 validates analytical derivatives against numerical differentiation, which is how several of these were caught.

◆ Prediction

Expect further validation-driven fixes rather than new distributions, since the derivative-checking suite added earlier is still surfacing defects in existing routines.

Alternatives to CBTF and gkwdist

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

See all CBTF alternatives → · See all gkwdist alternatives →

Recent activity from CBTF and gkwdist

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

  1. 7d agogkwdistv1.1.5 — Numerical correctness fixes and componentwise derivative validation
  2. 1mo agoCBTFTime inputs added; results groupable by input or function
  3. 2mo agogkwdistv1.1.4 — CRAN fix: skip timing-based tests on CRAN
  4. 3mo agogkwdistv1.1.3 — Critical MLE Bug Fixes & Numerical Corrections
  5. 6mo agoCBTFParallel fuzzing with timeouts, and multi-argument support
  6. 7mo agogkwdistAdds analytical derivative validation across all sub-families
  7. 8mo agogkwdistRefactors the C++ backend around stable log-space utilities
  8. 0y agoCBTFWhitelisting for false positives, plus clearer result semantics
  9. 1y agoCBTFFunction discovery skips unfuzzable functions; failures no longer crash
  10. 1y agoCBTFFirst release; notes carry only a website link
  11. 1y agoCBTFRaw results returned as an object with summary and print methods

Frequently asked questions

What is the difference between CBTF and gkwdist?

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

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

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