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 Kaniko — 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.
Kaniko's release feed stops dead in June 2024 after a patch that undid its own change
Kaniko builds container images inside a container without a Docker daemon, and its release feed reads as a project in late-stage maintenance that then simply stopped. Every entry in this window carries the same boilerplate header of executor, debug and slim image tags, and underneath it the substance is dependency bumps, CVE-driven upgrades, and narrow fixes to ADD and COPY semantics. The last release here, v1.23.1, is a revert of behaviour changed weeks earlier plus documentation clarifying what the flag was supposed to do.
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.
Kaniko builds container images inside a container without a Docker daemon, and its release feed reads as a project in late-stage maintenance that then simply stopped. Every entry in this window carries the same boilerplate header of executor, debug and slim image tags, and underneath it the substance is dependency bumps, CVE-driven upgrades, and narrow fixes to ADD and COPY semantics. The last release here, v1.23.1, is a revert of behaviour changed weeks earlier plus documentation clarifying what the flag was supposed to do.
The cadence tells the story: nine releases between December 2023 and June 2024, then nothing at all in the two years since. Even during the active stretch the work was defensive — registry-map compatibility, ECR authentication breakage, tar.gz handling in ADD, vulnerability scanning added to the executor image — rather than any expansion of what Kaniko does. The one recurring theme with forward motion, registry mirror and registry-map support, was about surviving locked-down or mirrored registry environments.
Nothing in these entries points at planned work, and a two-year gap after a revert-and-document patch is the signature of a project no longer being released; anyone depending on it should assume the last published executor image is the last one.
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 Kaniko.
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.
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 Kaniko alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Kaniko alternatives" section above for the current picks, or visit /alternatives/kaniko for the full list with editorial commentary on each.