ggpointless
ggpointless keeps adding the ggplot2 layers nobody else bothered to write.
A side-by-side editorial comparison of checkhelper and mLLMCelltype — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Consensus cell-type annotation that keeps adding LLM providers, and keeps fixing how they fail.
mLLMCelltype annotates scRNA-seq clusters by polling several LLMs and reconciling their answers into a consensus label, shipping as paired R and Python packages. The 2.0 line has settled into a rhythm: broaden the provider roster, then harden the parsing and retry paths that decide whether a given provider's answer survives into the consensus. Version 2.0.8 is pure reliability work, disabling DeepSeek V4's thinking mode because it exhausted the response budget before labels were returned, and raising non-streaming timeouts to 120 seconds.
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.
mLLMCelltype annotates scRNA-seq clusters by polling several LLMs and reconciling their answers into a consensus label, shipping as paired R and Python packages. The 2.0 line has settled into a rhythm: broaden the provider roster, then harden the parsing and retry paths that decide whether a given provider's answer survives into the consensus. Version 2.0.8 is pure reliability work, disabling DeepSeek V4's thinking mode because it exhausted the response budget before labels were returned, and raising non-streaming timeouts to 120 seconds.
The centre of gravity has moved from adding models to defending against them. Recent notes read as a catalogue of ways an LLM response can be malformed: numbered lists, preamble headers, annotation-internal colons, a mid-list Unknown, thinking blocks that precede the answer, rate limits returned as HTTP 200 with an error buried in the body. Each of those could previously shift or drop a cluster's annotation, which for a consensus tool is the failure that matters most. Provider additions now land as routine catalogue growth rather than a change in what the package can do.
Expect the next release to continue the reliability arc with more provider-specific timeout and parsing guards, and a CRAN publication of 2.0.8 to close the gap the notes themselves flag. Whether return_reasoning grows from an option into the default per-cluster evidence record is the open question these entries do not yet answer.
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 mLLMCelltype.
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 checkhelper alternatives → · See all mLLMCelltype alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. checkhelper and mLLMCelltype 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. checkhelper and mLLMCelltype 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.
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.
Top mLLMCelltype alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "mLLMCelltype alternatives" section above for the current picks, or visit /alternatives/mllmcelltype for the full list with editorial commentary on each.