evaluate
The engine under every knitted R document reached 1.0 by making evaluation behave like the console.
A side-by-side editorial comparison of checkhelper and Dashy — release velocity, themes, recent moves, and the top alternatives to consider.
checkhelper grew from a check wrapper into a CRAN pre-submission auditor.
Two years of near-silence ended with a 1.0.0 that adds 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. check_n_covr() runs R CMD check and coverage in a single test pass instead of two.
A release per merged PR, and right now nearly every one is a translation string.
Dashy is shipping a tagged release for essentially every merged pull request, producing ten versions in under three weeks. The current run is dominated by internationalization work: German and Traditional Chinese UI strings, plus a refactor that pulls hard-coded strings out of components so they can be translated at all. Dependabot accounts for the remainder.
Two years of near-silence ended with a 1.0.0 that adds 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. check_n_covr() runs R CMD check and coverage in a single test pass instead of two.
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. The existing fix_globals() was reworked the same way: it merges with an existing R/globals.R instead of overwriting it, and separates data.table and rlang pronouns from real undeclared globals so they get an @importFrom line rather than a globalVariables() entry.
Each additional CRAN incoming-check rule is a candidate for another audit_* function; the open question these notes leave is whether the family ever gets a single combined entry point.
Dashy is shipping a tagged release for essentially every merged pull request, producing ten versions in under three weeks. The current run is dominated by internationalization work: German and Traditional Chinese UI strings, plus a refactor that pulls hard-coded strings out of components so they can be translated at all. Dependabot accounts for the remainder.
The i18n push looks deliberate rather than incidental — extracting hard-coded strings is groundwork that only pays off if more locale contributions follow. Feature work has moved to the background; the last substantive changes in the visible window were OIDC post-logout redirect support and item sorting, both before this stretch. Cadence is high but the per-release payload is small.
Expect further locale contributions landing as individual patch releases while the string-extraction work continues to open up translatable surface area.
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 Dashy.
The engine under every knitted R document reached 1.0 by making evaluation behave like the console.
carrier's 0.3.0 quietly rewrites how crated functions see each other — and breaks code that relied on the old rules.
watcher is a thin filesystem-events binding whose releases are mostly build work.
gh spent its last two releases making failures and interruptions recoverable.
dockerfiler's 1.0.0 changes what its generated Dockerfiles actually contain.
Crane is turning into the table-and-plot layer for Roche's clinical output stack.
See all checkhelper alternatives → · See all Dashy alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Dashy is currently shipping more aggressively (velocity 6.3 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. Dashy is currently shipping more aggressively (velocity 6.3 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 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 Dashy alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dashy alternatives" section above for the current picks, or visit /alternatives/dashy for the full list with editorial commentary on each.