← Back to home
Comparison · Infra & APIs

contagionchannels vs webfakes

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

Shared themes:r-package

contagionchannels vs webfakes: at a glance

Featurecontagionchannelswebfakes
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themeseconometrics, contagion-analysis, cran-submission, r-packagetesting, http-server, r-package, test-fixtures
Last editorial update1h ago5d ago
WebsiteVisit →Visit →

What is contagionchannels?

Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.

contagionchannels reached CRAN on 2026-05-08 with a methodology preprint behind it and a cross-quantilogram lineage visible in its citations. What the release feed does not contain is any description of what the package computes: all three entries document the submission process — a licence field reduced from GPL-3 plus file to plain GPL-3, an arXiv reference rewritten in canonical DOI form, and a base-graphics fallback adjusted on a reviewer's request.

Read the full contagionchannels trajectory →

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.

Read the full webfakes trajectory →

contagionchannels vs webfakes: editorial side-by-side

C
contagionchannels
INFRA · APIS
0.0

Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.

◆ Current state

contagionchannels reached CRAN on 2026-05-08 with a methodology preprint behind it and a cross-quantilogram lineage visible in its citations. What the release feed does not contain is any description of what the package computes: all three entries document the submission process — a licence field reduced from GPL-3 plus file to plain GPL-3, an arXiv reference rewritten in canonical DOI form, and a base-graphics fallback adjusted on a reviewer's request.

◆ Where it's heading

There is no product trajectory to read here yet, only a submission one, and it is unusually well documented — each entry names the reviewer or check that prompted it and quotes the feedback verbatim. That transparency is the one signal available: the maintainer treats review rounds as releases worth publishing rather than squashing. Any judgement about direction will have to wait for a release that changes the package rather than its metadata.

◆ Prediction

With CRAN acceptance secured, the next release should be the first to carry actual methodological content; until one appears, there is not enough in these entries to say where the package is heading.

W
webfakes
INFRA · APIS
0.0

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 contagionchannels 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 contagionchannels or webfakes.

See all contagionchannels alternatives → · See all webfakes alternatives →

Recent activity from contagionchannels and webfakes

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

  1. 3mo agowebfakesKeep-alive tuning, locale-safe HTTP dates, looser routes
  2. 3mo agocontagionchannelsv0.1.3 — first CRAN release
  3. 3mo agocontagionchannelsv0.1.2: switch arXiv reference in DESCRIPTION to canonical DOI form
  4. 3mo agocontagionchannelsv0.1.1: address CRAN reviewer feedback (License) + add arXiv reference
  5. 1y agowebfakesHTTPS support lands in the fake server
  6. 1y agowebfakesNew decode_url server option
  7. 2y agowebfakesAdds a fake git HTTP server and CGI middleware
  8. 2y agowebfakesFixes tmpl_glue() on affected macOS builds
  9. 3y agowebfakeshttpbin clone reaches parity with the Python original

Frequently asked questions

What is the difference between contagionchannels and webfakes?

Both compete on the same themes — r-package — within Infra & APIs. contagionchannels 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 contagionchannels better than webfakes?

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

Top contagionchannels alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "contagionchannels alternatives" section above for the current picks, or visit /alternatives/contagionchannels 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.