compositional.mle
An MLE package rebuilt around composable solvers, then renamed to match.
A side-by-side editorial comparison of cyclocomp and procs — release velocity, themes, recent moves, and the top alternatives to consider.
A cyclomatic complexity checker that ships once every couple of years, and lands when it does.
cyclocomp measures cyclomatic complexity of R functions and packages, and is best known as the engine behind lintr's complexity rule. It has three releases in the visible window spread across nearly three years. The current one, 1.1.2, adds a quiet argument to cyclocomp_package_dir(); the two before it, shipped a day apart in 2023, added a large speedup and the package-directory entry point itself.
An R package rebuilding SAS procedures one PROC at a time, now filling in their options.
procs reimplements SAS statistical procedures — FREQ, MEANS, TTEST, REG, SORT, TRANSPOSE — as R functions returning both datasets and report-ready output, as part of the r-sassy suite. The catalogue of procedures is largely assembled; recent releases concentrate on the parameters each one accepts rather than on adding new procedures. Validation documentation is maintained alongside the code, consistent with the regulated environments the suite targets.
cyclocomp measures cyclomatic complexity of R functions and packages, and is best known as the engine behind lintr's complexity rule. It has three releases in the visible window spread across nearly three years. The current one, 1.1.2, adds a quiet argument to cyclocomp_package_dir(); the two before it, shipped a day apart in 2023, added a large speedup and the package-directory entry point itself.
This is a small tool that reached feature-complete and now moves only when a downstream consumer needs something. Every change in the window is externally contributed, and each addresses a concrete integration need: a function that works on a local package tree rather than an installed one, complexity results sorted so the worst offenders come first, and output suppression for programmatic callers. The 2023 pair shipped a day apart because the new entry point immediately exposed a performance problem on long linear code.
Expect the next change to arrive the same way, as a contributed patch serving a linting or CI workflow rather than as planned development.
procs reimplements SAS statistical procedures — FREQ, MEANS, TTEST, REG, SORT, TRANSPOSE — as R functions returning both datasets and report-ready output, as part of the r-sassy suite. The catalogue of procedures is largely assembled; recent releases concentrate on the parameters each one accepts rather than on adding new procedures. Validation documentation is maintained alongside the code, consistent with the regulated environments the suite targets.
The work has shifted from breadth to fidelity: where earlier releases introduced whole procedures, recent ones add the options a SAS user expects to find on them, most visibly the where parameter spread across five functions at once and plotting support across three. Statistical output is being widened too, with AIC and adjusted Chi-Square appearing. The remaining gap is per-procedure option coverage rather than missing procedures.
Expect continued option-level parity work on the existing procedures, with new statistics added to their output tables, rather than a new proc_* function.
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 cyclocomp or procs.
An MLE package rebuilt around composable solvers, then renamed to match.
nabla dropped its C++ engine to chase exact derivatives at any order.
Eight months from first release to keyring caching and workload identity.
A research-project workflow package where the interesting work is in the plumbing.
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 cyclocomp alternatives → · See all procs alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. cyclocomp and procs 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. cyclocomp and procs 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 cyclocomp alternatives in Analytics are ranked by recent ship velocity. Browse the "cyclocomp alternatives" section above for the current picks, or visit /alternatives/cyclocomp for the full list with editorial commentary on each.
Top procs alternatives in Analytics are ranked by recent ship velocity. Browse the "procs alternatives" section above for the current picks, or visit /alternatives/procs for the full list with editorial commentary on each.