← Back to home
Comparison · Infra & APIs

adjustedCurves vs Casdoor

A side-by-side editorial comparison of adjustedCurves and Casdoor — release velocity, themes, recent moves, and the top alternatives to consider.

adjustedCurves vs Casdoor: at a glance

FeatureadjustedCurvesCasdoor
SectorInfra & APIsInfra & APIs
Velocity score0.05.0
Sparks · 30d00
Top themessurvival-analysis, causal-inference, r-package, biostatisticsidentity, sso, authorization, mfa
Last editorial update52m ago18h ago
WebsiteVisit →Visit →

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.

Read the full adjustedCurves trajectory →

What is Casdoor?

An identity platform tightening server-side enforcement one micro-release at a time.

Casdoor is a self-hosted single sign-on and identity management service covering OAuth, LDAP, MFA and user administration. It releases continuously — four tags landed within eighty minutes on 16 August — with each carrying a single commit, so a version number here marks one change rather than a bundle.

Read the full Casdoor trajectory →

adjustedCurves vs Casdoor: editorial side-by-side

A
adjustedCurves
INFRA · APIS
0.0

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.

C
Casdoor
INFRA · APIS
5.0

An identity platform tightening server-side enforcement one micro-release at a time.

◆ Current state

Casdoor is a self-hosted single sign-on and identity management service covering OAuth, LDAP, MFA and user administration. It releases continuously — four tags landed within eighty minutes on 16 August — with each carrying a single commit, so a version number here marks one change rather than a bundle.

◆ Where it's heading

The recent run is almost entirely about moving enforcement to where it cannot be bypassed. Password update and MFA setup are now enforced server-side, the column whitelist is respected when an admin updates a user, and sessions and tokens are revoked when a user is forbidden. Each of these closes a gap where the client or an administrative path could sidestep a rule the product already claimed to apply. LDAP search by uidNumber and gidNumber and phone number normalisation round out the same period.

◆ Prediction

Expect the per-commit release cadence to continue, with further authorization-boundary fixes given three of the last five entries address exactly that. Nothing here signals a larger architectural change.

Alternatives to adjustedCurves and Casdoor

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 Casdoor.

See all adjustedCurves alternatives → · See all Casdoor alternatives →

Recent activity from adjustedCurves and Casdoor

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 2d agoCasdoorHelm chart push retries on non-fast-forward
  2. 2d agoCasdoorPassword update and MFA setup enforced server-side
  3. 2d agoCasdoorColumns whitelist respected on admin user updates
  4. 2d agoCasdoorPhone numbers normalised and validated before saving
  5. 2d agoCasdoorSessions and tokens revoked when a user is forbidden
  6. 4d agoCasdoorLDAP search by uidNumber and gidNumber
  7. 6mo agoadjustedCurvesOff-by-one-step error corrected in cumulative incidence estimates
  8. 1y agoadjustedCurvesIPTW curves can now extend to the last observed time
  9. 2y agoadjustedCurvesDropped arguments and a wrong multiple-imputation pooling formula
  10. 2y agoadjustedCurvesRisk tables, contrast consolidation and faster bootstrapping
  11. 3y agoadjustedCurvestmle and ostmle methods dropped
  12. 3y agoadjustedCurvesDependency compatibility and installation documentation

Frequently asked questions

What is the difference between adjustedCurves and Casdoor?

They serve adjacent needs but don't currently overlap on shipped themes. Casdoor 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 Casdoor?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Casdoor 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 Casdoor?

Top Casdoor alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Casdoor alternatives" section above for the current picks, or visit /alternatives/casdoor for the full list with editorial commentary on each.