← Back to home
Comparison · Infra & APIs

CBTF vs missSBM

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

Shared themes:r-package

CBTF vs missSBM: at a glance

FeatureCBTFmissSBM
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themestesting, fuzzing, r-package, developer-toolsr-package, network-analysis, stochastic-block-model, missing-data
Last editorial update56m 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 missSBM?

missSBM returns after four dormant years with a stricter API and a new refinement step.

The package fits stochastic block models to networks with missing data, covering both missing-at-random and informative sampling designs. After a run of releases from 2019 to 2022, the feed goes quiet until this year's 1.1.0, which breaks the control interface, exposes the block split and merge operations as testable instance methods, and adds a node-swap refinement pass that runs after variational convergence.

Read the full missSBM trajectory →

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

M
missSBM
INFRA · APIS
2.5

missSBM returns after four dormant years with a stricter API and a new refinement step.

◆ Current state

The package fits stochastic block models to networks with missing data, covering both missing-at-random and informative sampling designs. After a run of releases from 2019 to 2022, the feed goes quiet until this year's 1.1.0, which breaks the control interface, exposes the block split and merge operations as testable instance methods, and adds a node-swap refinement pass that runs after variational convergence.

◆ Where it's heading

The new release is maintenance-driven in the best sense: it targets the parts of the codebase that were hard to test or easy to misuse. Replacing free-form control lists with a function of named, defaulted arguments turns silent typos into errors, and pulling the exploration logic out of the collection class makes the search algorithm independently testable without changing it. The polish step addresses a known weakness, reaching individually misclassified nodes that split and merge moves cannot fix.

◆ Prediction

Given the gap before this release, the near-term question is whether the cadence resumes at all; the refactoring it contains would support further algorithmic work if it does.

Alternatives to CBTF and missSBM

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

See all CBTF alternatives → · See all missSBM alternatives →

Recent activity from CBTF and missSBM

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

  1. 27d agomissSBMReplaces raw control lists with missSBM_param(), adds polish()
  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. 3y agomissSBMAdapts to Matrix 1.4-2 and fixes HTML5 documentation
  9. 4y agomissSBMFixes linking against nloptR 2.0.0
  10. 5y agomissSBMRelaxes CRAN test tolerances to avoid random failures
  11. 5y agomissSBMRewrites optimisation in C++ armadillo with sparse matrices
  12. 5y agomissSBMRenames core functions and interfaces with the sbm package

Frequently asked questions

What is the difference between CBTF and missSBM?

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

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

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