Retool
Retool is retiring standalone Assist while folding the same capability into the app builder.
Comparison · Infra & APIs
rgm vs webfakes
A side-by-side editorial comparison of rgm and webfakes — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
rgm vs webfakes: at a glance
What is rgm?
A microbiome network model that got itself un-archived by deleting the dependency that killed it.
rgm implements the random graphical model for microbiome interactions across related environments, published in JABES in 2026. The package was archived from CRAN in February 2026 because of its dependency on huge; the recovery release drops that dependency entirely, which cost it the graphical-lasso warm start that used to seed the initial graph — the default is now an empty graph, with warm starts left to the user. A post-processing function returning ggplot diagnostics arrived in the same release.
What is webfakes?
A fake web server for tests that keeps closing the gap with the real thing.
webfakes runs a real HTTP server inside R tests so packages can exercise network code without hitting the internet. Its releases follow a consistent logic: find a class of behaviour that only the real internet could reproduce, then implement it locally. HTTPS arrived in 1.4.0; before that the httpbin clone reached full parity with the Python original, and a fake git HTTP server landed alongside CGI middleware. The most recent release, 1.5.0, is about the server's own rough edges — keep-alive timeouts, locale-independent HTTP date parsing, and trailing-slash route matching.
rgm vs webfakes: editorial side-by-side
rgm
0.0INFRA · APIS
A microbiome network model that got itself un-archived by deleting the dependency that killed it.
◆ Current state
rgm implements the random graphical model for microbiome interactions across related environments, published in JABES in 2026. The package was archived from CRAN in February 2026 because of its dependency on huge; the recovery release drops that dependency entirely, which cost it the graphical-lasso warm start that used to seed the initial graph — the default is now an empty graph, with warm starts left to the user. A post-processing function returning ggplot diagnostics arrived in the same release.
◆ Where it's heading
Three tags shipped inside two hours on one day, and the notes are candid about why: 1.1.0 held the actual work but was never released, 1.2.0 restated it under a higher version to signal the size of the change, and 1.2.1 answered CRAN pre-test feedback. Beyond the archival recovery, the visible work is housekeeping that had accumulated — a shadowed rmvnorm() definition, roxygen import tags that were silently emitting nothing, leftover C++ template scaffolding, and build artifacts under version control. The diagnostics function is the only genuinely new user-facing capability in the window.
◆ Prediction
The immediate task was restoring availability, and that is done; the open question the entries raise is whether losing the graphical-lasso warm start affects convergence in practice, which the new diagnostic plots are positioned to answer.
webfakes
0.0INFRA · APIS
A fake web server for tests that keeps closing the gap with the real thing.
◆ Current state
webfakes runs a real HTTP server inside R tests so packages can exercise network code without hitting the internet. Its releases follow a consistent logic: find a class of behaviour that only the real internet could reproduce, then implement it locally. HTTPS arrived in 1.4.0; before that the httpbin clone reached full parity with the Python original, and a fake git HTTP server landed alongside CGI middleware. The most recent release, 1.5.0, is about the server's own rough edges — keep-alive timeouts, locale-independent HTTP date parsing, and trailing-slash route matching.
◆ Where it's heading
The package is converging on being indistinguishable from a real server for test purposes, which is the only way it stays useful — every unsupported protocol feature is a piece of code someone cannot test offline. The remaining work has visibly shifted from missing endpoints to correctness details: date header parsing under unusual locales, keep-alive tuning, request body handling across content types.
◆ Prediction
Expect continued fidelity work against real-server behaviour rather than new app types, with HTTP/2 or authentication schemes the most plausible next gaps given the direction HTTPS opened. The entries do not indicate a specific planned feature.
Alternatives to rgm and webfakes
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 rgm or webfakes.
WPML
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
forestploter
A forest plot package that keeps handing users control of one more graphical detail.
ggInterval
Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.
contagionchannels
Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.
tidyaudit
Pipeline provenance for tidyverse workflows, recording what changed at each step without keeping the data.
See all rgm alternatives → · See all webfakes alternatives →
Recent activity from rgm and webfakes
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agowebfakesKeep-alive tuning, locale-safe HTTP dates, looser routes
- 3mo agorgmJournal DOI replaces the preprint; promotional wording removed
- 3mo agorgmBack on CRAN after dropping the dependency that caused archival
- 3mo agorgmUnreleased twin of the CRAN recovery release
- 1y agowebfakesHTTPS support lands in the fake server ⚡
- 1y agowebfakesNew decode_url server option
- 2y agorgmFirst release: simulation, estimation and post-processing
- 2y agowebfakesAdds a fake git HTTP server and CGI middleware
- 2y agowebfakesFixes tmpl_glue() on affected macOS builds
- 3y agowebfakeshttpbin clone reaches parity with the Python original
Frequently asked questions
What is the difference between rgm and webfakes?
Both compete on the same themes — r-package — within Infra & APIs. rgm and webfakes 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 rgm better than webfakes?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rgm and webfakes 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 rgm?
Top rgm alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rgm alternatives" section above for the current picks, or visit /alternatives/rgm for the full list with editorial commentary on each.
What are the best alternatives to webfakes?
Top webfakes alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "webfakes alternatives" section above for the current picks, or visit /alternatives/webfakes for the full list with editorial commentary on each.