nuggets
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
A side-by-side editorial comparison of g6R and Resend — release velocity, themes, recent moves, and the top alternatives to consider.
An R binding whose releases are mostly the upstream JS graph engine arriving, plus port ergonomics.
g6R wraps AntV's G6 graph engine as an htmlwidget, with Shiny proxy functions for data updates, layout control and mouse position read-back. The current release bundles G6 5.1.1 and ships the widget as a single self-contained bundle, having removed the split chunk. Recent work has concentrated on ports, the connection points nodes expose, with a new label-bottom placement, a larger default radius and a quieter hover state.
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
Most recent entries are about who or what can call Resend rather than about email delivery itself: OAuth 2.1 with PKCE, a remote MCP server tracking the current spec, a Codex plugin, a one-click Claude connector, and support for the Agent Plugins Standard. The email product still gets attention — suppressions, template folders, a compatibility checker in the code editor, and now cancellation of scheduled or queued Broadcasts from the API. Entries are terse one-liners, so the shipping cadence reads faster than the surface area actually changing.
g6R wraps AntV's G6 graph engine as an htmlwidget, with Shiny proxy functions for data updates, layout control and mouse position read-back. The current release bundles G6 5.1.1 and ships the widget as a single self-contained bundle, having removed the split chunk. Recent work has concentrated on ports, the connection points nodes expose, with a new label-bottom placement, a larger default radius and a quieter hover state.
Two threads run through the record. One is upstream tracking: the 0.6.5 engine bump alone restored the SVG renderer, fixed a combo-related canvas crash and pulled in new node and edge query APIs, which is a lot of user-visible change that this package did not author. The other is R-side ergonomics, where ports have been reworked in three consecutive releases and 0.5.0 added data validation strict enough that the notes warn existing code may break. Layout behaviour has moved toward explicit control, with recomputation now opt-in via an option and a dedicated proxy function.
The port work looks unfinished given three releases in a row on it, so more placement and styling options are the likeliest next step, alongside another engine bump as G6 5.1.x moves. Nothing in these entries indicates a direction beyond keeping pace with upstream.
Most recent entries are about who or what can call Resend rather than about email delivery itself: OAuth 2.1 with PKCE, a remote MCP server tracking the current spec, a Codex plugin, a one-click Claude connector, and support for the Agent Plugins Standard. The email product still gets attention — suppressions, template folders, a compatibility checker in the code editor, and now cancellation of scheduled or queued Broadcasts from the API. Entries are terse one-liners, so the shipping cadence reads faster than the surface area actually changing.
Resend is treating agents as the next class of sending client and building the authorization and discovery plumbing they need before that traffic arrives. The progression is legible: authenticate third parties (OAuth), be callable (MCP), be installable per vendor (Codex, Claude), then be installable by standard. The Cancel Broadcast API is the first sign of the next phase — once non-human callers can schedule sends, the ability to revoke one programmatically stops being a convenience.
Authorization and discovery are covered and reversibility has now started; the remaining gap is what an agent is permitted to send in the first place, so scoped per-agent sending limits or approval gates before dispatch are the natural next piece.
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 g6R or Resend.
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.
dqcheckr adds drift analysis, then removes the YAML a user had to hand-write.
An actuarial mainstay spends its releases on CI plumbing, not on new mathematics.
EDAForge is a data-quality auditor renamed mid-flight, still finding its CRAN footing.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Resend is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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. Resend is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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 g6R alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "g6R alternatives" section above for the current picks, or visit /alternatives/g6r for the full list with editorial commentary on each.
Top Resend alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Resend alternatives" section above for the current picks, or visit /alternatives/resend for the full list with editorial commentary on each.