DoseFinding
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
A side-by-side editorial comparison of patentsview and ymlthis — release velocity, themes, recent moves, and the top alternatives to consider.
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.
ymlthis retired itself, naming Quarto as the reason it no longer needs to exist.
ymlthis built R Markdown YAML front matter programmatically — a fluent `yml_*()` interface plus RStudio add-ins, so users did not have to hand-write metadata blocks whose valid fields were scattered across output-format documentation. Version 1.0.0 declares the package retired, with only CRAN-preserving changes to follow, and states the reason plainly: Quarto now provides good YAML support.
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.
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.
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.
ymlthis built R Markdown YAML front matter programmatically — a fluent `yml_*()` interface plus RStudio add-ins, so users did not have to hand-write metadata blocks whose valid fields were scattered across output-format documentation. Version 1.0.0 declares the package retired, with only CRAN-preserving changes to follow, and states the reason plainly: Quarto now provides good YAML support.
The retirement is the endpoint of a long drift. Between 2020 and 2022 every release was reactive — patching around a crayon update that mangled rendered YAML, tracking shiny 1.6, following roxygen2 7.0.0, fixing a typo in an add-in. No new capability has landed in six years, and the four-year gap before 1.0.0 had already answered the question the release note finally makes explicit.
Nothing further of substance is expected — the stated policy is changes only where CRAN requires them, so the next release, if any, will be a compatibility patch.
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 patentsview or ymlthis.
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul took mocking back from webmockr and made it a property of the client itself
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
Six years since the last functional change, and Google renamed the service it wraps in the release before that
See all patentsview alternatives → · See all ymlthis alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. patentsview and ymlthis 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. patentsview and ymlthis 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.
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.
Top ymlthis alternatives in Analytics are ranked by recent ship velocity. Browse the "ymlthis alternatives" section above for the current picks, or visit /alternatives/ymlthis for the full list with editorial commentary on each.