← Back to home
Comparison · Infra & APIs

packageRank vs valr

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

packageRank vs valr: at a glance

FeaturepackageRankvalr
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themescran, download-analytics, log-filtering, visualizationgenomics, interval-arithmetic, bioinformatics, bigwig
Last editorial update1h ago3h ago
WebsiteVisit →Visit →

What is packageRank?

CRAN download analytics maintained one micro-change at a time, hundreds per year

packageRank computes download counts and percentile ranks from CRAN's logs, with a filtering layer that tries to separate real installs from mirrors, sequences and bots. The recent releases are dense lists of small changes — thirty or more per version — spread across plot arguments, filter behaviour, and the cranDistribution object that now absorbs what packageDistribution() used to do separately.

Read the full packageRank trajectory →

What is valr?

valr's interval verbs now read genomic files in place instead of demanding a loaded tibble.

valr reimplements bedtools-style genome interval arithmetic as tidyverse verbs backed by C++. Its long project has been closing the behavioural gap with bedtools — the book-ended interval semantics finally match in 0.10.0, three releases after the deprecation began. The July release also ends the assumption that intervals must be in memory: bed_map(), bed_intersect(), bed_subtract(), bed_coverage() and bed_window() accept a bigWig or bigBed path or URL where an interval table used to go.

Read the full valr trajectory →

packageRank vs valr: editorial side-by-side

P
packageRank
INFRA · APIS
0.0

CRAN download analytics maintained one micro-change at a time, hundreds per year

◆ Current state

packageRank computes download counts and percentile ranks from CRAN's logs, with a filtering layer that tries to separate real installs from mirrors, sequences and bots. The recent releases are dense lists of small changes — thirty or more per version — spread across plot arguments, filter behaviour, and the cranDistribution object that now absorbs what packageDistribution() used to do separately.

◆ Where it's heading

There is no directional arc here; there is a maintainer keeping a measurement instrument calibrated against a data source that keeps moving. CRAN's logs went missing for a week in 2025 and the package now ships those dates as data and draws them as polygons on every plot. A chatgpt argument has been threaded through the plotting functions since 0.9.6. Function surface churns constantly — arguments renamed, plot helpers archived, others integrated.

◆ Prediction

Given the cadence, the next release will be another few dozen adjustments concentrated wherever CRAN's logs last surprised the maintainer. The consolidation of plotting arguments toward a single axis.package annotation looks unfinished.

V
valr
INFRA · APIS
0.0

valr's interval verbs now read genomic files in place instead of demanding a loaded tibble.

◆ Current state

valr reimplements bedtools-style genome interval arithmetic as tidyverse verbs backed by C++. Its long project has been closing the behavioural gap with bedtools — the book-ended interval semantics finally match in 0.10.0, three releases after the deprecation began. The July release also ends the assumption that intervals must be in memory: bed_map(), bed_intersect(), bed_subtract(), bed_coverage() and bed_window() accept a bigWig or bigBed path or URL where an interval table used to go.

◆ Where it's heading

Two arcs converge here. One is compatibility: min_overlap arrived with a deprecation warning in 0.9.0 and its default flipped from 0 to 1 in 0.10.0, so book-ended intervals are excluded by default as bedtools does, with the internal calculations in bed_closest() and friends deliberately left counting them. The other is the file-backed path, which grew out of the cpp11bigwig dependency adopted in 0.8.3 for read_bigwig() and re-exported in 0.9.0 — reading a file became querying one. Underneath, the C++ base keeps getting lighter: Rcpp swapped for cpp11, rlang cut to a single function, per-group memory copies removed from three verbs.

◆ Prediction

Only five verbs take a file argument today and bed_closest(), bed_glyph() and the statistical verbs do not, so extending the file-backed path across the rest of the API is the obvious follow-up. The deprecated tibble re-exports and the now-defunct n_fields argument suggest continued removal of the compatibility layer in the next minor release.

Alternatives to packageRank and valr

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 packageRank or valr.

See all packageRank alternatives → · See all valr alternatives →

Recent activity from packageRank and valr

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

  1. 1mo agovalrInterval verbs read bigWig and bigBed files directly
  2. 5mo agopackageRankPackage and version axis annotations across every plot
  3. 7mo agovalrbed_slop() and bed_flank() preserve input row order
  4. 8mo agovalrmin_overlap introduced; C++ backend moves from Rcpp to cpp11
  5. 10mo agopackageRankMissing CRAN log dates shipped as data and drawn on plots
  6. 1y agovalrTest updated for ggplot2 3.6.0
  7. 1y agopackageRankWeekend and version overlays for the base graphics path
  8. 1y agopackageRankPackage history prefers CRAN over the pkgsearch fallback
  9. 1y agovalrread_bigwig() switches to cpp11bigwig; read_gtf() deprecated
  10. 1y agopackageRankDistribution summaries gain totals and a top-N default
  11. 1y agopackageRankcranDistribution() object and a direct query family
  12. 1y agovalrCRAN Rd link NOTE and maintainer email change

Frequently asked questions

What is the difference between packageRank and valr?

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

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

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

What are the best alternatives to valr?

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