DoseFinding
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
A side-by-side editorial comparison of gMCPLite and patentsview — release velocity, themes, recent moves, and the top alternatives to consider.
gMCPLite exists to be gMCP without Java, and its releases guard that boundary rather than extend it.
gMCPLite is a fork of gMCP with the Java dependency removed and `hGraph()` ported over from gsDesign, giving R users graphical multiple comparison procedures and their visualisation without a JVM. Since that fork, no release has added a statistical capability. The visible history is compatibility work: ggplot2 3.5.0 argument naming, a cairo device for Unicode in examples, testthat 3.3.0 snapshot requirements, and a selective port of an upstream confidence-interval fix.
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.
gMCPLite is a fork of gMCP with the Java dependency removed and `hGraph()` ported over from gsDesign, giving R users graphical multiple comparison procedures and their visualisation without a JVM. Since that fork, no release has added a statistical capability. The visible history is compatibility work: ggplot2 3.5.0 argument naming, a cairo device for Unicode in examples, testthat 3.3.0 snapshot requirements, and a selective port of an upstream confidence-interval fix.
This is a package with a fixed job. The maintainers track two moving targets — the upstream gMCP it forked from, and the R graphics and testing stack underneath it — and pull across only what is needed. The addition of vdiffr visual regression tests for `hGraph()` is the most substantive recent change and fits the same posture: the plots are the deliverable, so pin them against accidental drift rather than redesign them.
Expect the pattern to continue — compatibility releases driven by ggplot2, testthat and pkgdown changes, with any statistical content arriving only as a selective port from upstream gMCP.
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.
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 gMCPLite or patentsview.
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 gMCPLite alternatives → · See all patentsview alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. gMCPLite 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. gMCPLite 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.
Top gMCPLite alternatives in Analytics are ranked by recent ship velocity. Browse the "gMCPLite alternatives" section above for the current picks, or visit /alternatives/gmcplite for the full list with editorial commentary on each.
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.