← Back to home
Comparison · Analytics

cyclocomp vs TrialEmulation

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

Shared themes:r-package

cyclocomp vs TrialEmulation: at a glance

FeaturecyclocompTrialEmulation
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesstatic-analysis, code-complexity, linting, r-packagecausal-inference, target-trial-emulation, duckdb, maintenance
Last editorial update40m ago41m 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 TrialEmulation?

Target trial emulation held steady by dependency maintenance, not new methods.

TrialEmulation implements target trial emulation from observational data, using duckdb to handle the expanded per-period datasets that approach generates. Every release in the visible window is upkeep: two consecutive releases removing the archived parglm dependency, two fixing tests against testthat updates, and two tracking duckdb sampling changes. No methodological work appears in the feed since before February 2025.

Read the full TrialEmulation trajectory →

cyclocomp vs TrialEmulation: 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.

T0.0

Target trial emulation held steady by dependency maintenance, not new methods.

◆ Current state

TrialEmulation implements target trial emulation from observational data, using duckdb to handle the expanded per-period datasets that approach generates. Every release in the visible window is upkeep: two consecutive releases removing the archived parglm dependency, two fixing tests against testthat updates, and two tracking duckdb sampling changes. No methodological work appears in the feed since before February 2025.

◆ Where it's heading

The package is being kept installable rather than extended. Its dependency surface, duckdb for storage, parglm for fitting, testthat for checks, generates most of the release traffic, and CRAN archiving parglm forced two separate releases three months apart to fully excise it. The version numbering, still in the 0.0.4.x range after years, suggests the maintainers do not consider the API settled enough to promote.

◆ Prediction

Further releases will most likely be triggered by upstream dependency changes; the entries give no signal on when methodological work resumes.

Alternatives to cyclocomp and TrialEmulation

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

See all cyclocomp alternatives → · See all TrialEmulation alternatives →

Recent activity from cyclocomp and TrialEmulation

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

  1. 4mo agoTrialEmulationDocumentation references to the archived parglm removed
  2. 5mo agocyclocompcyclocomp_package_dir() gains a quiet argument
  3. 7mo agoTrialEmulationparglm dependency dropped after CRAN archiving
  4. 9mo agoTrialEmulationTest fixes for updated testthat, plus link updates
  5. 9mo agoTrialEmulationCompatibility fixes ahead of testthat 3.3.0
  6. 1y agoTrialEmulationTests updated for duckdb 1.3.0 sampling; R 4.1 now required
  7. 1y agoTrialEmulationTests updated for duckdb 1.2.0 sampling changes
  8. 2y agocyclocompLarge speedup on long linear code
  9. 2y agocyclocompComplexity checks run against a local package tree

Frequently asked questions

What is the difference between cyclocomp and TrialEmulation?

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

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

Top TrialEmulation alternatives in Analytics are ranked by recent ship velocity. Browse the "TrialEmulation alternatives" section above for the current picks, or visit /alternatives/trialemulation for the full list with editorial commentary on each.