beekeeper
A code generator that turns an OpenAPI spec into a working R client package, milestone by milestone.
A side-by-side editorial comparison of doctest and taxifydb — release velocity, themes, recent moves, and the top alternatives to consider.
doctest is leaving CRAN: 0.4.1 is the last release through R's default channel.
doctest lets R package authors write tests inline with documentation examples, generating .Rd content and test files from the same source. The current release is a small bugfix, removing empty lines that @testraw was producing in generated .Rd files. Feature work has been quiet, with the two most recent entries both correcting artifacts in generated output rather than adding capability.
taxifydb found that its coverage audit was checking a hand-maintained list, not reality.
taxifydb packages taxonomic backbone databases for R, publishing prebuilt registers alongside the underlying data. The 0.1.21 release is a self-audit: the coverage checker was walking a hand-kept BACKENDS vector, so a backbone wired into the build but never added to that list was audited by nothing and reported clean, which had been the state of one backbone since it was added. The check now parses the real registration source, and refuses to run rather than audit a guessed set.
doctest lets R package authors write tests inline with documentation examples, generating .Rd content and test files from the same source. The current release is a small bugfix, removing empty lines that @testraw was producing in generated .Rd files. Feature work has been quiet, with the two most recent entries both correcting artifacts in generated output rather than adding capability.
The direction is distribution, not features. The last release states plainly that future versions will ship as GitHub releases or through r-universe.dev, so the package is stepping outside CRAN while continuing to be developed. Read with 0.4.0, which suppressed Source line output so example edits stop producing irrelevant test churn, the recent work is about generated output being stable and predictable.
The next versions should appear on GitHub and r-universe rather than CRAN, which means users on a CRAN-only install policy stay on 0.4.1 indefinitely. What the freedom from CRAN's review cycle gets spent on is not indicated in these entries.
taxifydb packages taxonomic backbone databases for R, publishing prebuilt registers alongside the underlying data. The 0.1.21 release is a self-audit: the coverage checker was walking a hand-kept BACKENDS vector, so a backbone wired into the build but never added to that list was audited by nothing and reported clean, which had been the state of one backbone since it was added. The check now parses the real registration source, and refuses to run rather than audit a guessed set.
The visible work is about closing gaps between what the build actually contains and what the checks believe it contains. Alongside the coverage fix, register artifacts are now compared against the backbones recorded in their own metadata sidecar, adding drift states the weekly workflow can open issues on. A curl bug in the same release is the same theme at a different level: setting an Authorization header replaced the header set rather than adding to it, silently dropping the Accept header that requests the asset bytes.
Expect the drift detection to keep expanding into the parts of the build that currently have no signal, since each release so far has found another place where a check was passing without looking at anything.
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 doctest or taxifydb.
A code generator that turns an OpenAPI spec into a working R client package, milestone by milestone.
A canvas grid wrapper aiming at the row counts where R's HTML table widgets stop being usable.
An R binding whose releases are mostly the upstream JS graph engine arriving, plus port ergonomics.
Antrea turned on gossip encryption by default and made users read the upgrade guide first.
Post-1.0 Strimzi tracks Kafka releases and hardens its own defaults
Security patching gives way to a hard Node.js 22 floor for every self-hosted install.
See all doctest alternatives → · See all taxifydb alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. taxifydb is currently shipping more aggressively (velocity 5.0 vs 3.8), with 0 editorial sparks in the last 30 days against 1. 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. taxifydb is currently shipping more aggressively (velocity 5.0 vs 3.8), with 0 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top doctest alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "doctest alternatives" section above for the current picks, or visit /alternatives/doctest for the full list with editorial commentary on each.
Top taxifydb alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "taxifydb alternatives" section above for the current picks, or visit /alternatives/taxifydb for the full list with editorial commentary on each.