exametrika
A test-theory package that grew into a graphical-model toolkit, now spending its releases paying down the API debt that growth created.
A side-by-side editorial comparison of inti and rdocdump — release velocity, themes, recent moves, and the top alternatives to consider.
inti keeps compounding small statistics and publishing tools for plant-science labs.
inti bundles the tooling a plant-science lab uses end to end: the Yupana analysis app, the Tarpuy experiment planner, scihub and rticle document rendering, and helpers for ANOVA and heritability. The 0.7.x line has been dominated by one thread, a PCA sub-module in Yupana carrying variable contribution, dimension correlation, supplementary variables and per-dimension selection. Releases are cumulative: 0.7.0, 0.7.1 and 0.7.2 all restate the same PCA lines, with each tag adding a few items on top, and 0.7.0 itself is split across two tags published 35 seconds apart.
rdocdump grew from a CRAN doc dumper into a resolver that pulls packages from anywhere
rdocdump flattens an R package's documentation and source into plain text, a shape aimed squarely at feeding code and docs to language models. It reached CRAN in June 2025 handling CRAN packages only. Within a year it accepted GitHub, GitLab and Bitbucket references with branch, tag and commit pinning, and 0.3.0 in May 2026 moved resolution onto pak.
inti bundles the tooling a plant-science lab uses end to end: the Yupana analysis app, the Tarpuy experiment planner, scihub and rticle document rendering, and helpers for ANOVA and heritability. The 0.7.x line has been dominated by one thread, a PCA sub-module in Yupana carrying variable contribution, dimension correlation, supplementary variables and per-dimension selection. Releases are cumulative: 0.7.0, 0.7.1 and 0.7.2 all restate the same PCA lines, with each tag adding a few items on top, and 0.7.0 itself is split across two tags published 35 seconds apart.
Two axes are moving. Analysis is deepening inside Yupana, where PCA went from a single view to a sub-module with its own contribution and correlation outputs across three tags. Publishing is widening around rticle() and scihub(), which now handle Google Docs markdown, crossrefs and page numbers, continuing the gdocs2qmd work from the 0.6 line. Neither is a change of direction; the package accretes features where the maintainer's own research workflow needs them.
Expect the next tag to extend the PCA sub-module again and add another rticle() or scihub() rendering detail, on the two-to-six-week cadence the 0.7 line has held.
rdocdump flattens an R package's documentation and source into plain text, a shape aimed squarely at feeding code and docs to language models. It reached CRAN in June 2025 handling CRAN packages only. Within a year it accepted GitHub, GitLab and Bitbucket references with branch, tag and commit pinning, and 0.3.0 in May 2026 moved resolution onto pak.
The direction is to stop caring where a package lives. 0.2.0 opened remote repository references and direct URLs; 0.3.0 swapped remotes for pak, added auto-discovery of packages in subdirectories, broadened URL format support to Bioconductor and GitLab, and added git clone as an automatic fallback when resolution fails. Cross-platform handling moved to internal tar operations.
With resolution generalized, remaining work is likely on output shaping — what gets included and how it is chunked — rather than on more sources. The entries do not say whether the text output format itself is stable.
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 inti or rdocdump.
A test-theory package that grew into a graphical-model toolkit, now spending its releases paying down the API debt that growth created.
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.
See all inti alternatives → · See all rdocdump alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. inti is currently shipping more aggressively (velocity 2.5 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. inti is currently shipping more aggressively (velocity 2.5 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 inti alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "inti alternatives" section above for the current picks, or visit /alternatives/inti for the full list with editorial commentary on each.
Top rdocdump alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rdocdump alternatives" section above for the current picks, or visit /alternatives/rdocdump for the full list with editorial commentary on each.