← Back to home
Comparison · Infra & APIs

AdGuard Home vs CBTF

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

AdGuard Home vs CBTF: at a glance

FeatureAdGuard HomeCBTF
SectorInfra & APIsInfra & APIs
Velocity score5.00.0
Sparks · 30d00
Top themesdns, ad-blocking, security, dns-over-quictesting, fuzzing, r-package, developer-tools
Last editorial update21h ago1h ago
WebsiteVisit →Visit →

What is AdGuard Home?

AdGuard Home patches a DNS-over-QUIC resource exhaustion advisory and moves edge to the new UI

v0.107.79 is presented as a stability release but carries the security work: a Go update for the vulnerabilities fixed in 1.26.6 and hardening against resource exhaustion over DNS-over-QUIC, published as GHSA-w6v6-f44j-3rj2. Alongside it, bootstrap server config accepts comments, install APIs gain a language property, static lease hostnames can be removed over HTTP, strict_sni_check is deprecated, and DNS64 stops treating unresolved CNAME/DNAME answers as the end of the chain.

Read the full AdGuard Home trajectory →

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 →

AdGuard Home vs CBTF: editorial side-by-side

A
AdGuard Home
INFRA · APIS
5.0

AdGuard Home patches a DNS-over-QUIC resource exhaustion advisory and moves edge to the new UI

◆ Current state

v0.107.79 is presented as a stability release but carries the security work: a Go update for the vulnerabilities fixed in 1.26.6 and hardening against resource exhaustion over DNS-over-QUIC, published as GHSA-w6v6-f44j-3rj2. Alongside it, bootstrap server config accepts comments, install APIs gain a language property, static lease hostnames can be removed over HTTP, strict_sni_check is deprecated, and DNS64 stops treating unresolved CNAME/DNAME answers as the end of the chain.

◆ Where it's heading

Two channels run in parallel — the 0.107 stable line and the 0.108 beta — and the edge channel has now switched to the new UI and versioning scheme, which is the first concrete sign that the 0.108 work is being staged for release. Stable releases keep absorbing protocol correctness fixes and DNS-over-QUIC hardening.

◆ Prediction

With edge already on the new UI and versioning scheme, the 0.108 line is the likely destination for that switch, and strict_sni_check being deprecated now points to its removal there.

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.

Alternatives to AdGuard Home and CBTF

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 AdGuard Home or CBTF.

See all AdGuard Home alternatives → · See all CBTF alternatives →

Recent activity from AdGuard Home and CBTF

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

  1. 23h agoAdGuard HomeAdGuard Home 0.107.79 hardens DNS-over-QUIC against resource exhaustion
  2. 20d agoAdGuard HomeBeta b.90 carries the DNS-over-QUIC exhaustion fix
  3. 1mo agoAdGuard HomeBeta b.89 hardens against JIGGLE attacks (GHSA-p5f5-3p5g-rfjw)
  4. 1mo agoAdGuard Home0.107.78: over half the changelog is security fixes
  5. 1mo agoCBTFTime inputs added; results groupable by input or function
  6. 2mo agoAdGuard HomeBeta b.88 patches path traversal in GLiNET auth (CVE-2026-41448)
  7. 2mo agoAdGuard Home0.107.77 patches a community-reported vulnerability
  8. 6mo agoCBTFParallel fuzzing with timeouts, and multi-argument support
  9. 0y agoCBTFWhitelisting for false positives, plus clearer result semantics
  10. 1y agoCBTFFunction discovery skips unfuzzable functions; failures no longer crash
  11. 1y agoCBTFFirst release; notes carry only a website link
  12. 1y agoCBTFRaw results returned as an object with summary and print methods

Frequently asked questions

What is the difference between AdGuard Home and CBTF?

They serve adjacent needs but don't currently overlap on shipped themes. AdGuard Home is currently shipping more aggressively (velocity 5.0 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 AdGuard Home better than CBTF?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. AdGuard Home is currently shipping more aggressively (velocity 5.0 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 AdGuard Home?

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

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.