← Back to home
Comparison · Infra & APIs

Skipper vs usmapdata

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

Skipper vs usmapdata: at a glance

FeatureSkipperusmapdata
SectorInfra & APIsInfra & APIs
Velocity score5.02.5
Sparks · 30d00
Top themesreverse-proxy, kubernetes, memory-footprint, zone-aware-routingr-packages, geospatial, census-data, cartography
Last editorial update8h ago36m ago
WebsiteVisit →Visit →

What is Skipper?

Skipper trims a 4x memory regression out of routesrv, days after shipping h2c

Zalando's HTTP router ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.63, which stops routesrv holding an uncompressed route tree alongside the compressed buffer: retained memory in the release's own benchmark falls from 30.7 MB to 2.0 MB, undoing most of the 4x increase zone-aware routing had introduced. Around it sit narrow auth repairs, and an eskip parser change that finally accepts negative numeric arguments in predicates and filters.

Read the full Skipper trajectory →

What is usmapdata?

usmapdata ships its 2025 shapefiles on the year-indexed model it adopted in 0.4.0.

usmapdata supplies the boundary data behind usmap's plotting functions. Since 0.4.0 it has been year-indexed: us_map(data_year = ) selects a vintage, and each Census release is added as its own year with older ones still reachable. 1.1.0 adds 2025. 1.0.0 closed the package's longest-standing gap by adding Puerto Rico, retroactively across every vintage.

Read the full usmapdata trajectory →

Skipper vs usmapdata: editorial side-by-side

S
Skipper
INFRA · APIS
5.0

Skipper trims a 4x memory regression out of routesrv, days after shipping h2c

◆ Current state

Zalando's HTTP router ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.63, which stops routesrv holding an uncompressed route tree alongside the compressed buffer: retained memory in the release's own benchmark falls from 30.7 MB to 2.0 MB, undoing most of the 4x increase zone-aware routing had introduced. Around it sit narrow auth repairs, and an eskip parser change that finally accepts negative numeric arguments in predicates and filters.

◆ Where it's heading

Two threads run through the recent tags. The data path keeps getting real work - leastRequests balancing, then h2c end to end in v0.27.57, now the memory cost of zone-aware routing being paid back. The auth filters, by contrast, are only being maintained: token introspection, grant auth, and now the OIDC Referer handling are fixes rather than new capability, and several are follow-ups to each other rather than independent bugs.

◆ Prediction

Zone-aware routing looks like the source of the recent memory attention, so expect further tuning around route storage and the hash computation done on every pull, which the release's second benchmark already isolates. The OIDC cookie change is the second link in an auth chain that started with the grant-auth fix, and is likely to draw another follow-up.

U
usmapdata
INFRA · APIS
2.5

usmapdata ships its 2025 shapefiles on the year-indexed model it adopted in 0.4.0.

◆ Current state

usmapdata supplies the boundary data behind usmap's plotting functions. Since 0.4.0 it has been year-indexed: us_map(data_year = ) selects a vintage, and each Census release is added as its own year with older ones still reachable. 1.1.0 adds 2025. 1.0.0 closed the package's longest-standing gap by adding Puerto Rico, retroactively across every vintage.

◆ Where it's heading

The package has settled into a predictable rhythm — one shapefile vintage per year, with structural change rare and clustered. The two changes that mattered were data_year in 0.4.0, which turned a single-vintage dataset into a time series, and the tibble-to-data-frame switch in 0.6.0 that reduced what downstream callers have to depend on.

◆ Prediction

The stated policy — each year added going forward, previous years reachable through data_year — points to a 2026 vintage as the next release. Nothing in these notes suggests further change to the data model.

Alternatives to Skipper and usmapdata

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 Skipper or usmapdata.

See all Skipper alternatives → · See all usmapdata alternatives →

Recent activity from Skipper and usmapdata

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

  1. 22h agoSkipperMove OIDC flow protection from Referer to cookies
  2. 22h agoSkipperv0.27.63: Store routes compressed-only, decompress on demand (#4198)
  3. 1d agoSkipperEskip predicates and filters accept negative numbers
  4. 1d agoSkipperFix token introspection handling
  5. 1d agoSkipperFix grant auth flow
  6. 2d agoSkipperUpdate outdated golang.org/x dependencies
  7. 23d agousmapdata2025 Census shapefiles added
  8. 0y agousmapdataPuerto Rico added across every map vintage
  9. 1y agousmapdataus_map() returns a data frame instead of a tibble
  10. 1y agousmapdata2024 Census shapefiles added
  11. 1y agousmapdatadata_year turns the package into a multi-vintage archive
  12. 2y agousmapdataMap data moves to 2023 shapefiles

Frequently asked questions

What is the difference between Skipper and usmapdata?

They serve adjacent needs but don't currently overlap on shipped themes. Skipper is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Skipper better than usmapdata?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Skipper is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to Skipper?

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

What are the best alternatives to usmapdata?

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