finnts
Microsoft's automated forecasting framework, still mostly a one-maintainer effort.
Comparison · Infra & APIs
adjustedCurves vs Infisical
A side-by-side editorial comparison of adjustedCurves and Infisical — release velocity, themes, recent moves, and the top alternatives to consider.
adjustedCurves vs Infisical: at a glance
What is adjustedCurves?
A survival curve package spending release after release correcting its own estimates
adjustedCurves computes confounder-adjusted survival and cumulative incidence curves across a range of estimators - IPTW, AIPTW, Aalen-Johansen, direct standardisation - with support for multiple imputation and bootstrapping. The recent releases are dominated by corrections to numbers the package already reported. Version 0.11.4 fixed cumulative incidence estimates under method="aalen_johansen" that were being read one time step early, which the maintainer notes could differ substantially when events are few, and added risk and event counts to the ggsurvplot conversion including correctly pooled values under multiple imputation.
What is Infisical?
Infisical's release notes now read like a certificate authority's, not a secrets store's.
Infisical ships roughly twice a week, and the bulk of each release is now PKI and PAM work rather than secret storage. The latest version adds KMIP automatic certificate renewal alongside a continuing migration of the console to a third-generation component set. Secret management itself appears mostly as plumbing changes: a revised validation API contract, folder-creation locking moved to Redis, and the removal of the legacy environment dashboard.
adjustedCurves vs Infisical: editorial side-by-side
adjustedCurves
0.0INFRA · APIS
A survival curve package spending release after release correcting its own estimates
◆ Current state
adjustedCurves computes confounder-adjusted survival and cumulative incidence curves across a range of estimators - IPTW, AIPTW, Aalen-Johansen, direct standardisation - with support for multiple imputation and bootstrapping. The recent releases are dominated by corrections to numbers the package already reported. Version 0.11.4 fixed cumulative incidence estimates under method="aalen_johansen" that were being read one time step early, which the maintainer notes could differ substantially when events are few, and added risk and event counts to the ggsurvplot conversion including correctly pooled values under multiple imputation.
◆ Where it's heading
Multiple imputation is the recurring fault line. The standard error pooling formula was implemented incorrectly until 0.11.2, then fixed again in 0.11.3 for the bootstrapping-plus-imputation combination, and 0.11.4 added the pooled risk table values that had previously been omitted entirely. A separate thread quietly removed capability: tmle and ostmle methods went in 0.10.0, and tmle support was pulled again in 0.11.1 after the concrete package left CRAN. Feature work does happen - risk tables, contrast arguments, the extend_to_last control on IPTW curves - but it is outweighed by correction.
◆ Prediction
Expect continued estimator-level corrections rather than new methods, and a possible return of tmle support if its upstream dependency returns to CRAN, since the removal was described as temporary.
Infisical
5.0INFRA · APIS
Infisical's release notes now read like a certificate authority's, not a secrets store's.
◆ Current state
Infisical ships roughly twice a week, and the bulk of each release is now PKI and PAM work rather than secret storage. The latest version adds KMIP automatic certificate renewal alongside a continuing migration of the console to a third-generation component set. Secret management itself appears mostly as plumbing changes: a revised validation API contract, folder-creation locking moved to Redis, and the removal of the legacy environment dashboard.
◆ Where it's heading
Infisical is assembling a credential platform rather than a secrets store, and it is doing so without a single headline release — each pillar arrives as two or three PRs per version. PKI is furthest along: after external AWS authorities, Intune enrollment and Nutanix sync, KMIP auto-renewal closes the loop on unattended certificate lifecycle. The v3 console migration is now touching the shared shell — page headers, dynamic-secret provider forms — which usually signals the old UI is being retired rather than patched.
◆ Prediction
Expect the v3 migration to finish sweeping the remaining project settings surfaces, and PAM to keep collecting account types the way PKI collected sync destinations. Whether the agent proxy graduates from telemetry and templates into a launched product is the open question these notes do not answer.
Alternatives to adjustedCurves and Infisical
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 adjustedCurves or Infisical.
BayLum
Bayesian luminescence dating that finally replaced its folder-structure input format.
daedalus
An epidemic-economic model teaching its interventions to react to the outbreak itself.
bkmrhat
A parallel-chain helper for bkmr that has settled into pure upkeep.
driveR
A cancer driver prioritization package that ships rarely and mostly to stay installable
metR
A meteorology ggplot2 extension where the netCDF reader became the main event
See all adjustedCurves alternatives → · See all Infisical alternatives →
Recent activity from adjustedCurves and Infisical
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 18h agoInfisicalKMIP certificates renew themselves; legacy environment dashboard removed
- 7d agoInfisicalMachine identities gain PAM access
- 10d agoInfisicalChef app connection gains gateway support
- 11d agoInfisicalPAM adds Redis access; PKI issues from AWS Private CA
- 13d agoInfisicalSpacelift sync, Cloudflare rotation, cert manager revamp
- 19d agoInfisicalSCEP support for Microsoft Intune lands in PKI
- 6mo agoadjustedCurvesOff-by-one-step error corrected in cumulative incidence estimates
- 1y agoadjustedCurvesIPTW curves can now extend to the last observed time
- 2y agoadjustedCurvesDropped arguments and a wrong multiple-imputation pooling formula
- 2y agoadjustedCurvesRisk tables, contrast consolidation and faster bootstrapping
- 3y agoadjustedCurvestmle and ostmle methods dropped
- 3y agoadjustedCurvesDependency compatibility and installation documentation
Frequently asked questions
What is the difference between adjustedCurves and Infisical?
They serve adjacent needs but don't currently overlap on shipped themes. Infisical is currently shipping more aggressively (velocity 5.0 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.
Is adjustedCurves better than Infisical?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Infisical is currently shipping more aggressively (velocity 5.0 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.
What are the best alternatives to adjustedCurves?
Top adjustedCurves alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "adjustedCurves alternatives" section above for the current picks, or visit /alternatives/adjustedcurves for the full list with editorial commentary on each.
What are the best alternatives to Infisical?
Top Infisical alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Infisical alternatives" section above for the current picks, or visit /alternatives/infisical for the full list with editorial commentary on each.