ggpointless
ggpointless keeps adding the ggplot2 layers nobody else bothered to write.
Comparison · Infra & APIs
checkhelper vs usmapdata
A side-by-side editorial comparison of checkhelper and usmapdata — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-packages
checkhelper vs usmapdata: at a glance
What is checkhelper?
checkhelper grew from a check wrapper into a CRAN pre-submission auditor.
1.0.0 added a whole audit_* family — audit_downloads(), audit_description(), audit_dontrun() and audit_citation() — each parsing package source statically and returning a tibble of hits paired with a suggested fix. The package is now defending that position: 1.0.1 rc1 is a submission candidate answering a CRAN archival notice, after roxygen2 8.x moved DESCRIPTION's RoxygenNote field and broke a find_missing_tags() test fixture.
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.
checkhelper vs usmapdata: editorial side-by-side
checkhelper
2.5INFRA · APIS
checkhelper grew from a check wrapper into a CRAN pre-submission auditor.
◆ Current state
1.0.0 added a whole audit_* family — audit_downloads(), audit_description(), audit_dontrun() and audit_citation() — each parsing package source statically and returning a tibble of hits paired with a suggested fix. The package is now defending that position: 1.0.1 rc1 is a submission candidate answering a CRAN archival notice, after roxygen2 8.x moved DESCRIPTION's RoxygenNote field and broke a find_missing_tags() test fixture.
◆ Where it's heading
The design commitment is static analysis — AST walks via getParseData(), line-by-line Rd reading, no eval() and no namespace loading — so the tool can report on a package it never runs. That commitment is what made the roxygen2 8.x break survivable: the audit pipeline itself was verified correct under 8.1.0 and only the test scaffolding had to go, now guarded by a dedicated regression test. fix_globals(write = TRUE) is being sanded down in parallel, no longer flattening per-function grouping comments or writing a degenerate empty globalVariables() shell.
◆ Prediction
The immediate move is the 1.0.1 submission itself, clearing the archival notice. Beyond that, each additional CRAN incoming-check rule remains a candidate for another audit_* function; the open question these notes still leave is whether the family ever gets a single combined entry point.
usmapdata
2.5INFRA · APIS
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 checkhelper 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 checkhelper or usmapdata.
mpactr
mpactr spent two spring releases normalizing case in metadata after users kept tripping on it.
surveytidy
surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.
surveycore
surveycore declared its API stable with every survey design type covered.
PEIMAN2
PEIMAN2 cut its annotation database loose from its release cycle without breaking CRAN.
prospectr
prospectr spent its biggest release in years fixing spectra it had been quietly mangling.
See all checkhelper alternatives → · See all usmapdata alternatives →
Recent activity from checkhelper and usmapdata
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agocheckhelpercheckhelper 1.0.1 rc1 (CRAN submission candidate)
- 23d agousmapdata2025 Census shapefiles added
- 3mo agocheckhelperA static audit_* family for CRAN pre-submission checks ⚡
- 0y agousmapdataPuerto Rico added across every map vintage
- 1y agousmapdataus_map() returns a data frame instead of a tibble
- 1y agousmapdata2024 Census shapefiles added
- 1y agousmapdatadata_year turns the package into a multi-vintage archive ⚡
- 2y agousmapdataMap data moves to 2023 shapefiles
- 2y agocheckhelperTest fixes for roxygen2 changes
- 3y agocheckhelpercheckhelper 0.1.0 - First CRAN Release
Frequently asked questions
What is the difference between checkhelper and usmapdata?
Both compete on the same themes — r-packages — within Infra & APIs. checkhelper and usmapdata are shipping at a similar cadence (velocity 2.5 vs 2.5, 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 checkhelper better than usmapdata?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. checkhelper and usmapdata are shipping at a similar cadence (velocity 2.5 vs 2.5, 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 checkhelper?
Top checkhelper alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "checkhelper alternatives" section above for the current picks, or visit /alternatives/checkhelper 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.