openairmaps
The mapping half of the openair stack, currently dismantling its own static plotting in favour of the parent package.
A side-by-side editorial comparison of Clerk and lifecontingencies — release velocity, themes, recent moves, and the top alternatives to consider.
Clerk is building auth for machines: API keys, a CLI agents can drive, per-verification pricing.
Two threads dominate. The first is machine authentication: API keys reached general availability with usage-based billing at $0.001 per creation and $0.00001 per verification, and a new CLI is described as a tool for developers and their agents to manage auth and billing. The second is enterprise readiness — Directory Sync (SCIM) generally available with custom attribute mapping and IdP role assignment, plus an Application Logs event stream across auth, billing, and organizations. Dashboard polish and Expo theming fill in around them.
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.
Two threads dominate. The first is machine authentication: API keys reached general availability with usage-based billing at $0.001 per creation and $0.00001 per verification, and a new CLI is described as a tool for developers and their agents to manage auth and billing. The second is enterprise readiness — Directory Sync (SCIM) generally available with custom attribute mapping and IdP role assignment, plus an Application Logs event stream across auth, billing, and organizations. Dashboard polish and Expo theming fill in around them.
Clerk is extending from human sign-in toward credentials for software acting on a user's behalf, and pricing that surface by the call rather than by the seat. The CLI framing makes the direction explicit: the control plane should be operable by an agent, not only by a person in a dashboard. Meanwhile SCIM, logs, and billing controls are the enterprise checklist that lets it sell upmarket while that bet plays out.
Expect the machine authentication suite to deepen around delegated and scoped access for agents — finer-grained key permissions or short-lived credentials — with usage-based pricing extended to whatever ships next.
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.
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 Clerk or lifecontingencies.
The mapping half of the openair stack, currently dismantling its own static plotting in favour of the parent package.
Air quality analysis rebuilt on ggplot2, twenty years of lattice plotting dropped in one release.
Survey harmonization tooling that spent its last release earning its way back onto CRAN.
A NOAA report-template generator being debugged by the workshops that teach it.
A fuzzer for R packages that grew from one argument at a time to parallel runs across whole namespaces.
An atlas of the tree of life that keeps publishing what it got wrong, and stopped shipping the trees it does not own.
See all Clerk alternatives → · See all lifecontingencies alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. lifecontingencies 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. lifecontingencies 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 Clerk alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Clerk alternatives" section above for the current picks, or visit /alternatives/clerk for the full list with editorial commentary on each.
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.