← Back to home
Comparison · Infra & APIs

pkgcache vs webfakes

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

pkgcache vs webfakes: at a glance

Featurepkgcachewebfakes
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themespackage-management, r-lib, repositories, authenticationtesting, http-server, r-package, test-fixtures
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is pkgcache?

The metadata cache under pak now speaks to authenticated and corporate repositories.

pkgcache maintains the package metadata cache that pak and pkgdepends build on, so its releases are about knowing where packages live and what platform they were built for. Version 2.2.4 added support for authenticated repositories through repo_auth(), the first time the cache could reach private registries directly. The releases around it track a moving target: Posit Package Manager behaviour, R Universe binaries, macOS binary availability per R version, Bioconductor version mapping, and most recently comments in DESCRIPTION and PACKAGES files following a change in R-devel.

Read the full pkgcache 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 →

pkgcache vs webfakes: editorial side-by-side

P
pkgcache
INFRA · APIS
0.0

The metadata cache under pak now speaks to authenticated and corporate repositories.

◆ Current state

pkgcache maintains the package metadata cache that pak and pkgdepends build on, so its releases are about knowing where packages live and what platform they were built for. Version 2.2.4 added support for authenticated repositories through repo_auth(), the first time the cache could reach private registries directly. The releases around it track a moving target: Posit Package Manager behaviour, R Universe binaries, macOS binary availability per R version, Bioconductor version mapping, and most recently comments in DESCRIPTION and PACKAGES files following a change in R-devel.

◆ Where it's heading

The work has shifted from CRAN-shaped assumptions toward the mixed reality of how R packages are actually distributed now — PPM snapshots, R Universe, private and authenticated registries, Bioconductor, and per-platform binaries across several R versions. Resilience is a recurring theme too: 2.2.5 makes an unreachable Bioconductor a non-fatal condition rather than a failure. MRAN's retirement, handled in 2.2.0 by resolving its prefix to PPM, is a reminder of how much of this package's job is absorbing other people's infrastructure changes.

◆ Prediction

Expect continued tracking of R-devel metadata format changes and new binary platforms as R 4.6 lands, since both already appear in 2.2.5. Further work on authenticated repository handling is the plausible follow-on, given how recently that capability arrived.

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

See all pkgcache alternatives → · See all webfakes alternatives →

Recent activity from pkgcache and webfakes

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

  1. 2mo agowebfakesKeep-alive tuning, locale-safe HTTP dates, looser routes
  2. 4mo agopkgcacheParses comments in DESCRIPTION and PACKAGES files
  3. 1y agowebfakesHTTPS support lands in the fake server
  4. 1y agopkgcacherepo_auth() brings authenticated repositories to the cache
  5. 1y agowebfakesNew decode_url server option
  6. 1y agopkgcacheStops using source URLs for archived PPM packages
  7. 2y agopkgcacheHandles macOS binaries for R 4.5 development builds
  8. 2y agowebfakesAdds a fake git HTTP server and CGI middleware
  9. 2y agopkgcacheImproves R to Bioconductor version matching
  10. 2y agowebfakesFixes tmpl_glue() on affected macOS builds
  11. 3y agopkgcacheMRAN prefix deprecated in favour of PPM; platform override added
  12. 3y agowebfakeshttpbin clone reaches parity with the Python original

Frequently asked questions

What is the difference between pkgcache and webfakes?

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

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

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