compositional.mle
An MLE package rebuilt around composable solvers, then renamed to match.
A side-by-side editorial comparison of snowflakeauth and tidycmprsk — release velocity, themes, recent moves, and the top alternatives to consider.
Eight months from first release to keyring caching and workload identity.
snowflakeauth handles authentication to Snowflake from R, reading the same connections.toml and config.toml files the Python connector and Snowflake CLI use. Since its June 2025 first release it has added JWT key-path configuration, externalbrowser login, on-disk connection caching in the system keyring, and workload identity authentication for the OIDC provider. Roughly a release per quarter, each adding a login method the surrounding ecosystem already assumed.
Competing-risks modelling that now moves only when its neighbours do.
tidycmprsk wraps competing risks regression and cumulative incidence estimation in tidy-style output, so results slot into gtsummary tables and ggsurvfit plots. The last two releases are small: 1.1.2 sorts tidy.tidycuminc() output by stratum, 1.1.1 is an HTML5 documentation update for CRAN. The substantive work in the window is 1.1.0, which reorganised the gtsummary relationship.
snowflakeauth handles authentication to Snowflake from R, reading the same connections.toml and config.toml files the Python connector and Snowflake CLI use. Since its June 2025 first release it has added JWT key-path configuration, externalbrowser login, on-disk connection caching in the system keyring, and workload identity authentication for the OIDC provider. Roughly a release per quarter, each adding a login method the surrounding ecosystem already assumed.
The package is closing the gap between R and Snowflake's other first-party clients one authentication mode at a time, moving from key-pair through interactive browser login to machine identity. Workload identity for OIDC is the notable direction: it targets code running in CI and managed compute where no human and no stored secret is present. A parallel thread of work on error messages, three separate fixes in 0.2.1 alone, suggests the maintainers treat confusing configuration failures as a real defect class.
Expect the remaining Snowflake authentication modes to keep arriving, with workload identity likely extended past the single OIDC provider it currently supports.
tidycmprsk wraps competing risks regression and cumulative incidence estimation in tidy-style output, so results slot into gtsummary tables and ggsurvfit plots. The last two releases are small: 1.1.2 sorts tidy.tidycuminc() output by stratum, 1.1.1 is an HTML5 documentation update for CRAN. The substantive work in the window is 1.1.0, which reorganised the gtsummary relationship.
The package has spent its releases handing responsibilities to neighbouring packages rather than growing its own surface. Plotting was deprecated then made defunct in favour of ggsurvfit::ggcuminc(), and 1.1.0 moved the regression table methods so that gtsummary could drop tidycmprsk as a dependency. What remains is the estimation core plus the S3 methods that let other packages consume it, which is a deliberate narrowing.
Expect releases to continue tracking changes in gtsummary and the broader tidy survival stack rather than adding estimation features.
Other Analytics 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 snowflakeauth or tidycmprsk.
An MLE package rebuilt around composable solvers, then renamed to match.
nabla dropped its C++ engine to chase exact derivatives at any order.
A research-project workflow package where the interesting work is in the plumbing.
A cyclomatic complexity checker that ships once every couple of years, and lands when it does.
Extreme value sampling in pure upkeep mode, mostly answering to Rcpp and CRAN.
A package retired in 2017 just got rewritten against R's public C API.
See all snowflakeauth alternatives → · See all tidycmprsk alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. snowflakeauth and tidycmprsk are shipping at a similar cadence (velocity 0.0 vs 0.0, 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. snowflakeauth and tidycmprsk are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top snowflakeauth alternatives in Analytics are ranked by recent ship velocity. Browse the "snowflakeauth alternatives" section above for the current picks, or visit /alternatives/snowflakeauth for the full list with editorial commentary on each.
Top tidycmprsk alternatives in Analytics are ranked by recent ship velocity. Browse the "tidycmprsk alternatives" section above for the current picks, or visit /alternatives/tidycmprsk for the full list with editorial commentary on each.