L1centrality
A graph-centrality package that spent 2026 making its existing measures usable at scale, then went quiet.
A side-by-side editorial comparison of lifecontingencies and restic — release velocity, themes, recent moves, and the top alternatives to consider.
An actuarial mainstay spends its releases on CI plumbing, not on new mathematics.
lifecontingencies is a long-running R package for actuarial life-contingency mathematics. Its three most recent tags show a maintainer keeping the infrastructure alive rather than extending the library: 1.5.2 is entirely author-metadata corrections, CI workflow repairs and release automation, 1.4.4 moved presentValue() onto Rcpp, and 1.4.1 states outright that it is identical to the version before it. The 1.5.2 notes jump from 1.4.4, so whatever happened in between never reached this feed.
A backup tool whose roadmap is correctness, release after release
restic ships roughly two releases a year, and the changelogs are almost entirely fixes ordered by importance. The 0.19 line (June and July 2026) continues that pattern: mount safety, SFTP behavior on Windows servers, exclude handling, and exit-code semantics. New capability appears rarely and narrowly, usually as backend credential support rather than new commands.
lifecontingencies is a long-running R package for actuarial life-contingency mathematics. Its three most recent tags show a maintainer keeping the infrastructure alive rather than extending the library: 1.5.2 is entirely author-metadata corrections, CI workflow repairs and release automation, 1.4.4 moved presentValue() onto Rcpp, and 1.4.1 states outright that it is identical to the version before it. The 1.5.2 notes jump from 1.4.4, so whatever happened in between never reached this feed.
The one genuine engineering thread is performance: rewriting presentValue() in Rcpp targets the innermost loop of every annuity and insurance valuation the package performs. Everything since has been about keeping CRAN checks green across platforms — TinyTeX install order, cross-platform caching, automated release tagging — plus a set of Italian actuarial benchmark tests that pin results against published tables. That is maintenance discipline on a stable API, not expansion.
Expect further patch tags carrying CI and documentation work, with any Rcpp performance work extending from presentValue() into adjacent valuation functions if it continues at all.
restic ships roughly two releases a year, and the changelogs are almost entirely fixes ordered by importance. The 0.19 line (June and July 2026) continues that pattern: mount safety, SFTP behavior on Windows servers, exclude handling, and exit-code semantics. New capability appears rarely and narrowly, usually as backend credential support rather than new commands.
The concentration of work is on the platforms where a backup tool is hardest to get right — Windows ACL inheritance and VSS metadata, macOS resource forks and FUSE mounts, SFTP and rclone backends under background execution. Running alongside that is a steady push toward being scriptable: distinct exit codes for missing source paths, snapshot removal failures and SIGINT, JSON output extended across more commands, and errors on invalid environment variables instead of silent defaults.
The next release will most likely be another 0.19.x patch of platform-specific fixes, since every minor in this window has been followed by one within a month or two.
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 lifecontingencies or restic.
A graph-centrality package that spent 2026 making its existing measures usable at scale, then went quiet.
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.
See all lifecontingencies alternatives → · See all restic alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. lifecontingencies and restic are shipping at a similar cadence (velocity 2.5 vs 2.5, 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. lifecontingencies and restic are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top lifecontingencies alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "lifecontingencies alternatives" section above for the current picks, or visit /alternatives/lifecontingencies for the full list with editorial commentary on each.
Top restic alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "restic alternatives" section above for the current picks, or visit /alternatives/restic for the full list with editorial commentary on each.