← Back to home
Comparison · Analytics

cyclocomp vs hubData

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

Shared themes:r-package

cyclocomp vs hubData: at a glance

FeaturecyclocomphubData
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesstatic-analysis, code-complexity, linting, r-packagedata-access, arrow, cloud-storage, hubverse
Last editorial update24m ago1h 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 hubData?

The Arrow data layer for forecast hubs, spending its releases on cloud and materialisation bugs.

hubData is the access layer for hubverse forecasting hubs, connecting to local and cloud-stored model output through Arrow and handing back lazy connections or materialised tibbles. Its releases divide sharply between schema and utility additions in the 1.x line and, more recently, a run of defect fixes in the cloud and Arrow integration. Two of those fixes involved data being silently wrong rather than an error being raised.

Read the full hubData trajectory →

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

H
hubData
ANALYTICS
0.0

The Arrow data layer for forecast hubs, spending its releases on cloud and materialisation bugs.

◆ Current state

hubData is the access layer for hubverse forecasting hubs, connecting to local and cloud-stored model output through Arrow and handing back lazy connections or materialised tibbles. Its releases divide sharply between schema and utility additions in the 1.x line and, more recently, a run of defect fixes in the cloud and Arrow integration. Two of those fixes involved data being silently wrong rather than an error being raised.

◆ Where it's heading

The package has largely finished adding surface and is now paying down the cost of sitting on top of Arrow and S3: ALTREP-backed columns escaping into user sessions, cloud hubs whose declared format differs from what is actually written, and metadata arrays parsing inconsistently. Each fix narrows the gap between what the storage layer does and what an R user expects. The performance-motivated default flip in 2.0.0 points the same way, prioritising large cloud hubs over conservative local behaviour.

◆ Prediction

Expect continued fixes at the Arrow and cloud boundary, particularly where declared hub configuration and actual stored format disagree, which has now produced defects twice.

Alternatives to cyclocomp and hubData

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

See all cyclocomp alternatives → · See all hubData alternatives →

Recent activity from cyclocomp and hubData

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

  1. 1mo agohubDataCloud hubs declaring CSV no longer return an empty connection
  2. 3mo agohubDatacollect_hub() returns plain vectors instead of ALTREP views
  3. 3mo agohubDataArray-valued metadata fields now parse as list columns
  4. 5mo agocyclocompcyclocomp_package_dir() gains a quiet argument
  5. 7mo agohubDatadate_col parameter for oracle output schemas
  6. 8mo agohubDataconnect_hub() skips file validation by default (breaking)
  7. 10mo agohubDataArrow schema conversion and validation utilities
  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 hubData?

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

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

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