← Back to home
Comparison · Analytics

cyclocomp vs tidycmprsk

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

Shared themes:r-package

cyclocomp vs tidycmprsk: at a glance

Featurecyclocomptidycmprsk
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesstatic-analysis, code-complexity, linting, r-packagecompeting-risks, survival-analysis, tidyverse, gtsummary
Last editorial update32m ago35m ago
WebsiteVisit →Visit →

What is cyclocomp?

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.

Read the full cyclocomp trajectory →

What is tidycmprsk?

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.

Read the full tidycmprsk trajectory →

cyclocomp vs tidycmprsk: editorial side-by-side

C
cyclocomp
ANALYTICS
0.0

A cyclomatic complexity checker that ships once every couple of years, and lands when it does.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

Expect the next change to arrive the same way, as a contributed patch serving a linting or CI workflow rather than as planned development.

T
tidycmprsk
ANALYTICS
0.0

Competing-risks modelling that now moves only when its neighbours do.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

Expect releases to continue tracking changes in gtsummary and the broader tidy survival stack rather than adding estimation features.

Alternatives to cyclocomp and tidycmprsk

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

See all cyclocomp alternatives → · See all tidycmprsk alternatives →

Recent activity from cyclocomp and tidycmprsk

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

  1. 4mo agotidycmprsktidycmprsk 1.1.2
  2. 5mo agocyclocompcyclocomp_package_dir() gains a quiet argument
  3. 9mo agotidycmprsktidycmprsk 1.1.1
  4. 1y agotidycmprsktidycmprsk 1.1.0
  5. 2y agotidycmprsktidycmprsk 1.0.0
  6. 2y agocyclocompLarge speedup on long linear code
  7. 2y agocyclocompComplexity checks run against a local package tree
  8. 3y agotidycmprsktidycmprsk 0.2.0
  9. 4y agotidycmprsktidycmprsk 0.1.2

Frequently asked questions

What is the difference between cyclocomp and tidycmprsk?

Both compete on the same themes — r-package — within Analytics. cyclocomp 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.

Is cyclocomp better than tidycmprsk?

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

What are the best alternatives to cyclocomp?

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.

What are the best alternatives to tidycmprsk?

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.