← Back to home
Comparison · Analytics

crul vs patentsview

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

crul vs patentsview: at a glance

Featurecrulpatentsview
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themeshttp-client, async, mocking, ropensciapi-client, breaking-change, patent-data, r-package
Last editorial update43m ago3h ago
WebsiteVisit →Visit →

What is crul?

crul took mocking back from webmockr and made it a property of the client itself

crul is the R6-based HTTP client underneath much of rOpenSci's package stack, covering synchronous requests, three flavours of async, pagination and retries. Its 1.6.0 release in July 2025 changed where test mocking lives: each client — HttpClient, Async, AsyncVaried — now takes a mocking parameter at initialisation or per method, and the standalone mock() function is deprecated. Mocking used to be something webmockr switched on from outside; it is now a setting on the client.

Read the full crul trajectory →

What is patentsview?

Dormant for years, then rewritten wholesale when the API underneath it broke.

patentsview is an R client for the USPTO PatentsView API, and version 1.0.0 is less a feature release than a forced reconstruction: the upstream API introduced mandatory keys, renamed and re-nested its endpoints, and the package had to follow. Between 2017 and 2021 the release cadence was roughly annual and almost entirely defensive — wrapping examples so CRAN would not fail during API outages, patching URL encoding, adding throttling retries. The 1.0.0 work restores the package to parity with an API that no longer resembles the one it was written against.

Read the full patentsview trajectory →

crul vs patentsview: editorial side-by-side

C
crul
ANALYTICS
0.0

crul took mocking back from webmockr and made it a property of the client itself

◆ Current state

crul is the R6-based HTTP client underneath much of rOpenSci's package stack, covering synchronous requests, three flavours of async, pagination and retries. Its 1.6.0 release in July 2025 changed where test mocking lives: each client — HttpClient, Async, AsyncVaried — now takes a mocking parameter at initialisation or per method, and the standalone mock() function is deprecated. Mocking used to be something webmockr switched on from outside; it is now a setting on the client.

◆ Where it's heading

The async surface has been the growth area for years — retries reached Async, AsyncVaried, AsyncQueue and HttpRequest in 1.4, AsyncQueue gained the response accessors in 1.2, and 1.5.0 wired async requests up to webmockr. The 1.6.0 change reverses that direction of dependency, and it landed within a minute of webmockr's own release severing its tie to vcr. Read together, the rOpenSci HTTP stack is being deliberately untangled so each package can be used without the others.

◆ Prediction

With mock() deprecated rather than removed, the next major release is the likely point of deletion. Expect the remaining work to follow the same decoupling theme rather than adding request features.

P
patentsview
ANALYTICS
0.0

Dormant for years, then rewritten wholesale when the API underneath it broke.

◆ Current state

patentsview is an R client for the USPTO PatentsView API, and version 1.0.0 is less a feature release than a forced reconstruction: the upstream API introduced mandatory keys, renamed and re-nested its endpoints, and the package had to follow. Between 2017 and 2021 the release cadence was roughly annual and almost entirely defensive — wrapping examples so CRAN would not fail during API outages, patching URL encoding, adding throttling retries. The 1.0.0 work restores the package to parity with an API that no longer resembles the one it was written against.

◆ Where it's heading

The arc here is a client package whose roadmap is entirely dictated by an upstream service it does not control. Every release since 0.2.0 has been reactive — HTTPS migration, throttling, encoding fixes, and now a full breaking rewrite. The one forward-looking piece is retrieve_linked_data(), which follows HATEOAS links the API now returns, meaning the package is starting to navigate the API rather than just query fixed endpoints.

◆ Prediction

Expect the next releases to be small follow-ups against the reworked API — field list refreshes and error handling for endpoints that behave differently in practice than in the documentation. The entries do not show any independent roadmap, so anything beyond that would depend on further upstream API changes.

Alternatives to crul and patentsview

Other Analytics 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 crul or patentsview.

See all crul alternatives → · See all patentsview alternatives →

Recent activity from crul and patentsview

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

  1. 6mo agopatentsviewRebuilt for PatentsView's new API: keys, nested endpoints
  2. 1y agocrulMocking becomes a client parameter, independent of webmockr
  3. 2y agocrulAsync requests become mockable through webmockr
  4. 2y agocrulDocumentation fixes and test helper tweak
  5. 3y agocrulHTTP retries reach the async classes
  6. 3y agocrulClearer error for mismatched urls and disk lengths
  7. 4y agocrulAsyncQueue gains response accessors; results print as a summary
  8. 4y agopatentsviewMoves to HTTPS endpoints and handles API throttling
  9. 7y agopatentsviewVignettes dropped so CRAN builds survive API outages
  10. 8y agopatentsviewAPI examples wrapped in dontrun for CRAN stability
  11. 8y agopatentsviewcast_pv_data() converts returned columns to real types
  12. 9y agopatentsviewFirst release: query DSL for the PatentsView API

Frequently asked questions

What is the difference between crul and patentsview?

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

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. crul and patentsview 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 Analytics products to evaluate alongside.

What are the best alternatives to crul?

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

What are the best alternatives to patentsview?

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