← Back to home
Comparison · Analytics

dendroNetwork vs vcr

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

Shared themes:ropensci

dendroNetwork vs vcr: at a glance

FeaturedendroNetworkvcr
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesdendrochronology, network-analysis, cytoscape, archaeologytesting, http-mocking, breaking-change, api-cleanup
Last editorial update1h ago4h ago
WebsiteVisit →Visit →

What is dendroNetwork?

Six releases, six identical bodies — the feed carries the package abstract instead of release notes

dendroNetwork builds networks of dendrochronological series from similarity between tree-ring measurements, applies community detection to find matching material, and hands the result to Cytoscape for visualisation. That description is all the feed provides: every one of the six visible releases carries the same package abstract as its body, with no record of what changed in any of them. Version 0.5.5 in July 2025 is the most recent.

Read the full dendroNetwork trajectory →

What is vcr?

Added the HTTP client everyone moved to, then deleted a decade of its own public surface.

vcr records HTTP interactions to disk so R package tests can replay them without network access. Two releases define its current state. Version 1.6.0 added httr2 support alongside the existing httr and crul backends, following the R ecosystem's migration to httr2. Version 2.0 then removed a large amount of accumulated public surface — the logging functions, vcr_last_error(), the exported R6 classes including RequestHandler, Request, VcrResponse and HTTPInteractionList, and several configuration options that had stopped working or could not be implemented correctly.

Read the full vcr trajectory →

dendroNetwork vs vcr: editorial side-by-side

D
dendroNetwork
ANALYTICS
0.0

Six releases, six identical bodies — the feed carries the package abstract instead of release notes

◆ Current state

dendroNetwork builds networks of dendrochronological series from similarity between tree-ring measurements, applies community detection to find matching material, and hands the result to Cytoscape for visualisation. That description is all the feed provides: every one of the six visible releases carries the same package abstract as its body, with no record of what changed in any of them. Version 0.5.5 in July 2025 is the most recent.

◆ Where it's heading

What the timestamps show is more informative than the text. Versions 0.5.0 through 0.5.3 were all published within two minutes of each other on 12 April 2024, and in descending version order, which is the signature of a release history backfilled in one pass rather than four separate releases. Real releases follow at 0.5.4 a fortnight later and 0.5.5 fifteen months after that. Development is slow and, on this evidence, undocumented.

◆ Prediction

No prediction is supportable from these entries — none of them describe a change. Any read on where this package is heading would need the NEWS file or the commit history rather than the feed.

V
vcr
ANALYTICS
0.0

Added the HTTP client everyone moved to, then deleted a decade of its own public surface.

◆ Current state

vcr records HTTP interactions to disk so R package tests can replay them without network access. Two releases define its current state. Version 1.6.0 added httr2 support alongside the existing httr and crul backends, following the R ecosystem's migration to httr2. Version 2.0 then removed a large amount of accumulated public surface — the logging functions, vcr_last_error(), the exported R6 classes including RequestHandler, Request, VcrResponse and HTTPInteractionList, and several configuration options that had stopped working or could not be implemented correctly.

◆ Where it's heading

The package is consolidating after years of additive growth. The 2.0 removals are almost all things that were exported without needing to be, or options that promised behaviour the implementation could not guarantee — check_cassette_names() was deprecated precisely because it cannot be made correct. Cassette maintenance is being simplified too, with re_record_interval now the single mechanism for expiring recordings.

◆ Prediction

Expect the post-2.0 releases to be about migration support and fallout from the removed API, since the breaking list is long enough that reverse dependencies will surface problems. Async support for httr2 stays blocked until req_perform_parallel gains a mocking hook, which the entries note is upstream work.

Alternatives to dendroNetwork and vcr

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 dendroNetwork or vcr.

See all dendroNetwork alternatives → · See all vcr alternatives →

Recent activity from dendroNetwork and vcr

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

  1. 8mo agovcr2.0 removes the logging API and the exported R6 classes
  2. 1y agodendroNetworkdendroNetwork 0.5.5
  3. 1y agovcrMaintainer email address updated
  4. 2y agovcrAdds httr2 support alongside httr and crul
  5. 2y agodendroNetworkdendroNetwork 0.5.4
  6. 2y agodendroNetworkdendroNetwork 0.5.0
  7. 2y agodendroNetworkdendroNetwork 0.5.1
  8. 2y agodendroNetworkdendroNetwork 0.5.2
  9. 2y agodendroNetworkdendroNetwork 0.5.3
  10. 3y agovcrDrops compilation; test setup moves back to helper files
  11. 3y agovcrFixes request matching with escaped characters
  12. 5y agovcrvcr_test_path() finds the package root correctly

Frequently asked questions

What is the difference between dendroNetwork and vcr?

Both compete on the same themes — ropensci — within Analytics. dendroNetwork and vcr 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 dendroNetwork better than vcr?

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

What are the best alternatives to dendroNetwork?

Top dendroNetwork alternatives in Analytics are ranked by recent ship velocity. Browse the "dendroNetwork alternatives" section above for the current picks, or visit /alternatives/dendronetwork for the full list with editorial commentary on each.

What are the best alternatives to vcr?

Top vcr alternatives in Analytics are ranked by recent ship velocity. Browse the "vcr alternatives" section above for the current picks, or visit /alternatives/vcr for the full list with editorial commentary on each.