ggpointless
ggpointless keeps adding the ggplot2 layers nobody else bothered to write.
A side-by-side editorial comparison of BIOMASS and checkhelper — release velocity, themes, recent moves, and the top alternatives to consider.
A tropical-forest biomass staple modernising its geospatial stack without saying so
BIOMASS estimates aboveground biomass and its uncertainty in tropical forests and is well established in that niche. Its public changelog is close to empty: the most recent entry, 2.2.4, is a thirty-four character pointer to the NEWS file. The last release with readable content, 2.1.11, bundled six versions of work whose substantive part was migrating off sp and raster to sf and terra, and from httr to httr2.
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.
BIOMASS estimates aboveground biomass and its uncertainty in tropical forests and is well established in that niche. Its public changelog is close to empty: the most recent entry, 2.2.4, is a thirty-four character pointer to the NEWS file. The last release with readable content, 2.1.11, bundled six versions of work whose substantive part was migrating off sp and raster to sf and terra, and from httr to httr2.
The visible arc is dependency modernisation and CRAN compliance rather than science: retiring sp and raster ahead of their deprecation, failing gracefully when taxonomic services are unreachable, and repeatedly changing taxonomic backend as those services disappeared — taxosaurus to TNRS, then away from Tropicos once it was no longer maintained. The recurring fragility is correctTaxo(), which depends on third-party name resolution outside the maintainers' control.
Expect the next release to be another compliance or dependency response; on this feed's record the release notes will not say what changed, leaving the NEWS file as the only reliable source.
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.
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.
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.
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 BIOMASS or checkhelper.
ggpointless keeps adding the ggplot2 layers nobody else bothered to write.
mpactr spent two spring releases normalizing case in metadata after users kept tripping on it.
surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.
surveycore declared its API stable with every survey design type covered.
PEIMAN2 cut its annotation database loose from its release cycle without breaking CRAN.
prospectr spent its biggest release in years fixing spectra it had been quietly mangling.
See all BIOMASS alternatives → · See all checkhelper alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. checkhelper is currently shipping more aggressively (velocity 2.5 vs 0.0), 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. checkhelper is currently shipping more aggressively (velocity 2.5 vs 0.0), 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.
Top BIOMASS alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "BIOMASS alternatives" section above for the current picks, or visit /alternatives/biomass for the full list with editorial commentary on each.
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.