← Back to home
Comparison · Infra & APIs

packageRank vs usmap

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

packageRank vs usmap: at a glance

FeaturepackageRankusmap
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themescran, download-analytics, log-filtering, visualizationcartography, sf, data-packaging, fips
Last editorial update2h ago49m 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 usmap?

Ten years in, US mapping splits its data out and finally adds Puerto Rico.

usmap plots US state and county maps in an Alaska- and Hawaii-inset projection and joins user data to them by FIPS code. Over the last two years it has been rebuilt underneath: the map data moved out to a companion usmapdata package, the geometry became sf, and a data_year parameter lets a plot match the vintage of the data being plotted. Version 1.0.0 marks ten years of the project and adds Puerto Rico across every function.

Read the full usmap trajectory →

packageRank vs usmap: 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.

U
usmap
INFRA · APIS
0.0

Ten years in, US mapping splits its data out and finally adds Puerto Rico.

◆ Current state

usmap plots US state and county maps in an Alaska- and Hawaii-inset projection and joins user data to them by FIPS code. Over the last two years it has been rebuilt underneath: the map data moved out to a companion usmapdata package, the geometry became sf, and a data_year parameter lets a plot match the vintage of the data being plotted. Version 1.0.0 marks ten years of the project and adds Puerto Rico across every function.

◆ Where it's heading

The package has separated what it draws from how it draws, and that separation is what makes the recent releases possible: annual map vintages ship in usmapdata without touching usmap, and Puerto Rico could be backfilled into every existing year at once. The remaining work is coverage and defaults rather than architecture, and the Puerto Rico exclusion default is already governed by an environment variable rather than a code change.

◆ Prediction

Expect the annual map vintage to keep arriving through usmapdata, with usmap itself changing only where a new territory or a projection default needs handling.

Alternatives to packageRank and usmap

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 usmap.

See all packageRank alternatives → · See all usmap alternatives →

Recent activity from packageRank and usmap

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

  1. 5mo agopackageRankPackage and version axis annotations across every plot
  2. 10mo agopackageRankMissing CRAN log dates shipped as data and drawn on plots
  3. 11mo agousmapPuerto Rico added across every usmap function and map year
  4. 1y agousmapdata_year parameter threaded through the plotting functions
  5. 1y agopackageRankWeekend and version overlays for the base graphics path
  6. 1y agopackageRankPackage history prefers CRAN over the pkgsearch fallback
  7. 1y agopackageRankDistribution summaries gain totals and a top-N default
  8. 1y agopackageRankcranDistribution() object and a direct query family
  9. 2y agousmapPopulation and poverty data refreshed; ggplot2 3.5 legend fix
  10. 2y agousmapMap data becomes sf; usmap_transform() returns geometry
  11. 2y agousmapDocumentation links updated
  12. 2y agousmapMap data extracted to a companion usmapdata package

Frequently asked questions

What is the difference between packageRank and usmap?

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

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

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