compositional.mle
An MLE package rebuilt around composable solvers, then renamed to match.
A side-by-side editorial comparison of cyclocomp and manymome — 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.
Steady quarterly releases behind a feed that shows almost none of what changed.
manymome computes indirect and moderated effects for path-analysis and SEM models using bootstrap and Monte Carlo intervals. The four most recent CRAN releases (0.3.2 through 0.3.6) publish as bare pointers to the package's own NEWS page, so the feed carries no changelog text for any of them. Where content is visible, at 0.3.1 and 0.2.9, the work is fitting-engine breadth and speed rather than new methodology.
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.
manymome computes indirect and moderated effects for path-analysis and SEM models using bootstrap and Monte Carlo intervals. The four most recent CRAN releases (0.3.2 through 0.3.6) publish as bare pointers to the package's own NEWS page, so the feed carries no changelog text for any of them. Where content is visible, at 0.3.1 and 0.2.9, the work is fitting-engine breadth and speed rather than new methodology.
The legible arc runs toward turning the q_* quick-mediation wrappers into a complete workflow: lavaan::sem fitting with full information maximum likelihood for missing data, a plot method, and user-specified mediation models, alongside repeated optimization of do_boot() and do_mc(). Cadence is roughly quarterly and has held for two years. What the last four versions actually contain cannot be read from this feed.
Expect continued quarterly CRAN releases extending the q_* family; beyond that the entries shown do not support a confident call on direction.
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 manymome.
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 manymome alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. cyclocomp and manymome 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 manymome 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 manymome alternatives in Analytics are ranked by recent ship velocity. Browse the "manymome alternatives" section above for the current picks, or visit /alternatives/manymome for the full list with editorial commentary on each.