goat
A gene-set enrichment package that outgrew its human-only origins, then went quiet.
A side-by-side editorial comparison of Cobbler and writeAlizer — release velocity, themes, recent moves, and the top alternatives to consider.
A backport branch kept alive for downstreams, with the main line nowhere in sight.
Every release in Cobbler's visible history describes itself the same way: backports from main to make Cobbler more stable for the community. The 3.3.x line has absorbed real work under that framing — collection indices, lazy loading, new XML-RPC endpoints — but none of it originates here. The most recent item is a 3.2.3 build carrying the CVE-2024-47533 fix to an older branch, with its Fixed and Added sections left as literal TBD placeholders.
Six months of releases and not one of them touched the scoring models
writeAlizer generates predicted writing-quality scores from features produced by Coh-Metrix, ReaderBench and GAMET, downloading its trained scoring models on demand. Every release in this window — nine of them between September 2025 and February 2026 — is about that download path rather than the scoring: classed error conditions, checksum verification, an offline mode, a mockable artifact directory, and dependency reporting for the model families a user actually invokes.
Every release in Cobbler's visible history describes itself the same way: backports from main to make Cobbler more stable for the community. The 3.3.x line has absorbed real work under that framing — collection indices, lazy loading, new XML-RPC endpoints — but none of it originates here. The most recent item is a 3.2.3 build carrying the CVE-2024-47533 fix to an older branch, with its Fixed and Added sections left as literal TBD placeholders.
This is a stabilization branch serving downstream packagers rather than a product advancing on its own. The work that does land splits cleanly into three buckets: distribution coverage (Ubuntu 22.04, Debian 12, AlmaLinux, RHEL9, openSUSE and SLE signatures), API surface for integrators, and security backports. 3.3.3 flagged dump_vars as the replacement for get_blended_data as of 3.4.0 — a version that has not appeared in any release since.
Expect continued single-purpose backports to 3.3.x and older branches as CVEs surface; the entries give no indication of when or whether the 3.4.0 work these releases keep deferring to will ship.
writeAlizer generates predicted writing-quality scores from features produced by Coh-Metrix, ReaderBench and GAMET, downloading its trained scoring models on demand. Every release in this window — nine of them between September 2025 and February 2026 — is about that download path rather than the scoring: classed error conditions, checksum verification, an offline mode, a mockable artifact directory, and dependency reporting for the model families a user actually invokes.
The package is being made safe to distribute. CRAN's policy on packages that reach the internet drove the first wave — graceful failure, tests that preflight their URLs and skip, examples seeded from a local mock model — and 1.7.0 turned the accumulated fixes into structure with named error classes for each failure mode. Only 1.7.2 adds anything a user would ask for: filename handling for Coh-Metrix and GAMET outputs that arrive as paths.
With the artifact registry hardened and documented, the pressure that produced nine releases in six months should ease, and attention can return to the models themselves — the vignette on scoring-model development added in 1.7.2 hints at that. Nothing here promises new models.
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 Cobbler or writeAlizer.
A gene-set enrichment package that outgrew its human-only origins, then went quiet.
The recursive-computation engine under massProps grows the accessors its consumer needed
A mass-properties rollup spends a year on documentation and follows its sibling's API
A cognitive-science sampling package ships once, then goes quiet for eighteen months
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
See all Cobbler alternatives → · See all writeAlizer alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Cobbler and writeAlizer are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. Cobbler and writeAlizer are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Cobbler alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Cobbler alternatives" section above for the current picks, or visit /alternatives/cobbler for the full list with editorial commentary on each.
Top writeAlizer alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "writeAlizer alternatives" section above for the current picks, or visit /alternatives/writealizer for the full list with editorial commentary on each.