mpactr
mpactr spent two spring releases normalizing case in metadata after users kept tripping on it.
Comparison · Infra & APIs
checkhelper vs Cursor
A side-by-side editorial comparison of checkhelper and Cursor — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:developer-tools
checkhelper vs Cursor: at a glance
| Feature | checkhelper | Cursor |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 2.5 | 8.8 |
| Sparks · 30d | 0 | 3 |
| Top themes | r-packages, cran-compliance, static-analysis, developer-tools | ai-agents, autonomous-agents, event-driven, cloud-agents |
| Last editorial update | 1h ago | 17h ago |
| Website | Visit → | — |
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 Cursor?
Cursor's agents stop waiting to be asked - they subscribe, and they hold a goal until it's done.
Cursor has spent two months moving agents out of the editor: cloud agents on iPhone and iPad, in Slack, on schedules, a team marketplace, a router picking the model per request, and Origin hosting repos and pull requests inside the product. This release changes how those agents are started. Cloud agents can subscribe to an event source - a PR, a Slack thread, a schedule - and wake when something happens, and /goal gives one a long-lived objective it works toward until complete. Subagents now get their own virtual machines with isolated project copies.
checkhelper vs Cursor: 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.
Cursor
8.8INFRA · APIS
Cursor's agents stop waiting to be asked - they subscribe, and they hold a goal until it's done.
◆ Current state
Cursor has spent two months moving agents out of the editor: cloud agents on iPhone and iPad, in Slack, on schedules, a team marketplace, a router picking the model per request, and Origin hosting repos and pull requests inside the product. This release changes how those agents are started. Cloud agents can subscribe to an event source - a PR, a Slack thread, a schedule - and wake when something happens, and /goal gives one a long-lived objective it works toward until complete. Subagents now get their own virtual machines with isolated project copies.
◆ Where it's heading
The through-line has been removing external dependencies and wait states; this release removes the human from the trigger. Agents that Cursor created now subscribe to their own pull requests and drive them to completion, fixing CI and answering bot comments unprompted. Isolated per-subagent VMs are what make that safe to parallelize - swarms can work without colliding - and steering lets a person redirect a running agent at the next tool call rather than interrupting it. Cursor is building the always-on case rather than the faster-autocomplete one.
◆ Prediction
With subscriptions limited to cloud agents for now, the obvious next step is bringing event-triggered runs to local agents, along with the controls an always-on fleet needs - spend limits, approval gates, and a way to review what ran while nobody was watching.
Alternatives to checkhelper and Cursor
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 Cursor.
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.
standardlastprofile
A German electricity load-profile package added gas and doubled the market it serves.
See all checkhelper alternatives → · See all Cursor alternatives →
Recent activity from checkhelper and Cursor
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agocheckhelpercheckhelper 1.0.1 rc1 (CRAN submission candidate)
- 1d agoCursorCloud agents subscribe to events and hold goals on their own ⚡
- 3d agoCursorCursor starts hosting repos and pull requests ⚡
- 7d agoCursorCloud agents boot from prebuilt environment snapshots
- 22d agoCursorCursor for iPad adds full PR review and an agent inbox
- 29d agoCursorAuto mode moves to Cursor Router with cost/intelligence modes ⚡
- 1mo agoCursorCursor in Slack plans first and works across multiple repos
- 3mo agocheckhelperA static audit_* family for CRAN pre-submission checks ⚡
- 2y agocheckhelperTest fixes for roxygen2 changes
- 3y agocheckhelpercheckhelper 0.1.0 - First CRAN Release
Frequently asked questions
What is the difference between checkhelper and Cursor?
Both compete on the same themes — developer-tools — within Infra & APIs. Cursor is currently shipping more aggressively (velocity 8.8 vs 2.5), with 3 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 checkhelper better than Cursor?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Cursor is currently shipping more aggressively (velocity 8.8 vs 2.5), with 3 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 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 Cursor?
Top Cursor alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Cursor alternatives" section above for the current picks, or visit /alternatives/cursor for the full list with editorial commentary on each.