← Back to home
Comparison · Infra & APIs

CBTF vs nominatimlite

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

CBTF vs nominatimlite: at a glance

FeatureCBTFnominatimlite
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themestesting, fuzzing, r-package, developer-toolsr, geocoding, openstreetmap, nominatim
Last editorial update1h ago3d 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 nominatimlite?

nominatimlite's real work was self-hosting and caching; 0.6.0 is an internal refactor with no API change

nominatimlite is a dependency-light R client for the Nominatim geocoding API, returning results as plain data frames or sf objects. The features that define it landed in 0.4.0 — structured queries, local Nominatim server support, and JSONV2 output — and 0.5.0 added session-scoped caching plus a 1.2-second inter-request delay to stay within the public API's usage policy. 0.6.0 in June 2026 changed no public behaviour.

Read the full nominatimlite trajectory →

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

N
nominatimlite
INFRA · APIS
0.0

nominatimlite's real work was self-hosting and caching; 0.6.0 is an internal refactor with no API change

◆ Current state

nominatimlite is a dependency-light R client for the Nominatim geocoding API, returning results as plain data frames or sf objects. The features that define it landed in 0.4.0 — structured queries, local Nominatim server support, and JSONV2 output — and 0.5.0 added session-scoped caching plus a 1.2-second inter-request delay to stay within the public API's usage policy. 0.6.0 in June 2026 changed no public behaviour.

◆ Where it's heading

The package has settled. Recent effort goes to being a well-behaved API citizen and to internal consistency: 0.6.0 raised the minimum R to 4.1.0 and refactored URL construction, progress handling, coordinate validation and output preparation with AI assistance, explicitly leaving the public API untouched. That refactor is part of a sweep across the same maintainer's packages in the same weeks.

◆ Prediction

With the API surface stable and rate-limiting handled, future releases most likely track upstream Nominatim endpoint changes, as 0.4.0 did for v4.4.0. Nothing in the entries points to new query capabilities.

Alternatives to CBTF and nominatimlite

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

See all CBTF alternatives → · See all nominatimlite alternatives →

Recent activity from CBTF and nominatimlite

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

  1. 1mo agoCBTFTime inputs added; results groupable by input or function
  2. 2mo agonominatimliteInternal refactor with no public API change; minimum R now 4.1.0
  3. 5mo agonominatimliteSession caching and 1.2s throttling for API calls
  4. 6mo agoCBTFParallel fuzzing with timeouts, and multi-argument support
  5. 7mo agonominatimliteMinor fixes to reverse geocoding functions
  6. 0y agoCBTFWhitelisting for false positives, plus clearer result semantics
  7. 1y agoCBTFFunction discovery skips unfuzzable functions; failures no longer crash
  8. 1y agoCBTFFirst release; notes carry only a website link
  9. 1y agoCBTFRaw results returned as an object with summary and print methods
  10. 1y agonominatimliteDocumentation update
  11. 2y agonominatimliteFix crash on long OSM IDs in address lookup
  12. 2y agonominatimliteStructured queries, local server support and JSONV2 output

Frequently asked questions

What is the difference between CBTF and nominatimlite?

They serve adjacent needs but don't currently overlap on shipped themes. CBTF and nominatimlite 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 nominatimlite?

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

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