nuggets
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
Comparison · Infra & APIs
adjustedCurves vs Prowler
A side-by-side editorial comparison of adjustedCurves and Prowler — release velocity, themes, recent moves, and the top alternatives to consider.
adjustedCurves vs Prowler: 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 Prowler?
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
Prowler is shipping a minor release roughly weekly with patches filling the gaps. The agentic layer, Lighthouse, has moved from explaining findings to acting on them, with named skills attached to individual findings and every write path bound to the asking user's RBAC. Alongside that, 5.39.1 fixes an install path that had been quietly broken: 5.38.0 declared a cryptography floor its own dependencies capped below, so pip install prowler silently resolved back to 5.37.1.
adjustedCurves vs Prowler: 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.
Prowler
7.5INFRA · APIS
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
◆ Current state
Prowler is shipping a minor release roughly weekly with patches filling the gaps. The agentic layer, Lighthouse, has moved from explaining findings to acting on them, with named skills attached to individual findings and every write path bound to the asking user's RBAC. Alongside that, 5.39.1 fixes an install path that had been quietly broken: 5.38.0 declared a cryptography floor its own dependencies capped below, so pip install prowler silently resolved back to 5.37.1.
◆ Where it's heading
Two tracks run in parallel and rarely overlap. The minor releases push the commercial agentic surface forward — triage skills, page context, the MCP tool set — while the patches defend the parts everyone uses: dependency resolution, container CVEs, and check correctness. That second track matters more than its version numbers suggest, because a security scanner reporting PASS when an API call failed is worse than one that errors. 5.39.1 fixes exactly that in the ECS task-definition checks, and makes the SES public-access check evaluate every identity policy rather than stopping at the first.
◆ Prediction
Expect the next minor to extend Lighthouse skills to groups of findings rather than one at a time, with patch releases continuing to absorb Trivy and base-image CVE churn.
Alternatives to adjustedCurves and Prowler
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 Prowler.
projoint
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
eratosthenes
eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.
dqcheckr
dqcheckr adds drift analysis, then removes the YAML a user had to hand-write.
lifecontingencies
An actuarial mainstay spends its releases on CI plumbing, not on new mathematics.
EDAForge
EDAForge is a data-quality auditor renamed mid-flight, still finding its CRAN footing.
See all adjustedCurves alternatives → · See all Prowler alternatives →
Recent activity from adjustedCurves and Prowler
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoProwler5.39.1 unbreaks pip install and stops two checks reporting false PASS
- 6d agoProwlerLighthouse AI triages findings; Azure management-group onboarding ⚡
- 13d agoProwlerCompliance Watchlist and multi-domain SAML SSO
- 15d agoProwlerContainer CVE cleanup and an M365 false-FAIL fix
- 15d agoProwlerLighthouse AI gains page context and the full MCP toolbox ⚡
- 21d agoProwlerFinding Groups dispatch to Jira; Attack Paths query filtering
- 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 Prowler?
They serve adjacent needs but don't currently overlap on shipped themes. Prowler is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 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 Prowler?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Prowler is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 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 Prowler?
Top Prowler alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Prowler alternatives" section above for the current picks, or visit /alternatives/prowler for the full list with editorial commentary on each.