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 Prisma — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | inti | Prisma |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 2.5 | 0.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | plant-science, pca, shiny, reproducible-reporting | wasm-query-engine, rust-free, prisma-postgres, developer-tooling |
| Last editorial update | 1h ago | 3mo ago |
| Website | Visit → | — |
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.
Prisma 7's Rust-free client is the floor — every release since has been hardening the WASM stack and pulling Postgres deeper in.
Prisma is in steady-state release mode after the v7.0 cutover removed the Rust query engine in favor of a WebAssembly query compiler running on the main JS thread. Recent ORM versions have layered on what the WASM architecture made possible — query caching, fast/small compilers, savepoint-based nested transactions — alongside tooling (prisma bootstrap, prisma postgres link, Studio dark mode) that ties the ORM ever more tightly to Prisma's own Postgres offering.
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.
Prisma is in steady-state release mode after the v7.0 cutover removed the Rust query engine in favor of a WebAssembly query compiler running on the main JS thread. Recent ORM versions have layered on what the WASM architecture made possible — query caching, fast/small compilers, savepoint-based nested transactions — alongside tooling (prisma bootstrap, prisma postgres link, Studio dark mode) that ties the ORM ever more tightly to Prisma's own Postgres offering.
Two parallel arcs: (1) catching up on real database semantics that the previous Rust engine couldn't easily expose (savepoints, partial indexes, query caching), and (2) productizing a turnkey Postgres path where the CLI handles provisioning, linking, and migrations end-to-end. Prisma is converging the ORM and the hosted database into a single onboarding experience.
Expect the next minor releases to keep paving the Prisma Postgres path — likely connection-pool defaults, edge-runtime-aware client builds, and tighter CI/migration ergonomics. Independent ORM users may continue to feel like a slower-moving lane while bootstrap-style commands favor the hosted DB.
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 Prisma.
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 Prisma alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Prisma alternatives" section above for the current picks, or visit /alternatives/prisma for the full list with editorial commentary on each.