← Back to home
Comparison · Analytics

cfr vs S7

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

cfr vs S7: at a glance

FeaturecfrS7
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesepidemiology, severity-estimation, outbreak-analytics, epiverseobject-system, r-language, api-stability, backward-compatibility
Last editorial update4h ago45m ago
WebsiteVisit →Visit →

What is cfr?

cfr packaged delay-corrected severity estimation, then went quiet on maintenance.

The package estimates disease severity and case ascertainment while correcting for the delay between a case being reported and its outcome being known. After the 0.1.1 rework of the estimation internals and a maintainer handover to Adam Kucharski, activity dropped to a vignette and an R-devel compatibility patch in February 2025.

Read the full cfr trajectory →

What is S7?

S7 has stopped adding surface and started proving it holds up against R itself.

S7 is R's third-generation object system, built to unify the S3 and S4 lineages rather than add a fourth. The design work landed in 0.2.0, which reworked the default constructor, extended base-class coverage, and added a backward-compatibility shim so `@` property access works on R older than 4.3. Everything since has been maintenance: property setters gained a `check` escape hatch, and two consecutive releases exist mainly to keep the package compiling against R-devel 4.6.

Read the full S7 trajectory →

cfr vs S7: editorial side-by-side

C
cfr
ANALYTICS
0.0

cfr packaged delay-corrected severity estimation, then went quiet on maintenance.

◆ Current state

The package estimates disease severity and case ascertainment while correcting for the delay between a case being reported and its outcome being known. After the 0.1.1 rework of the estimation internals and a maintainer handover to Adam Kucharski, activity dropped to a vignette and an R-devel compatibility patch in February 2025.

◆ Where it's heading

The methodological work is done and consolidated: likelihood approximation is now selected automatically from outbreak size and an initial severity estimate, and the internals were renamed with a dot prefix to close the public surface down to cfr_static(), cfr_rolling() and the data-preparation generic. Releases since have been documentation and compatibility only.

◆ Prediction

The 0.1.0 notes flagged time-varying ascertainment as future work and it has not appeared in the two releases since; nothing in these entries indicates when or whether it lands.

S
S7
ANALYTICS
0.0

S7 has stopped adding surface and started proving it holds up against R itself.

◆ Current state

S7 is R's third-generation object system, built to unify the S3 and S4 lineages rather than add a fourth. The design work landed in 0.2.0, which reworked the default constructor, extended base-class coverage, and added a backward-compatibility shim so `@` property access works on R older than 4.3. Everything since has been maintenance: property setters gained a `check` escape hatch, and two consecutive releases exist mainly to keep the package compiling against R-devel 4.6.

◆ Where it's heading

The changelog is thinning by design — 0.1.0 was a months-long feature dump, 0.2.0 a coordinated architectural revision, 0.2.2 a single line about internal R-devel support. That shape usually means an API the maintainers consider settled, where the remaining work is tracking the host language rather than extending the system. The one recurring theme is validation cost: repeated releases have made validation less frequent, more targeted, or skippable outright.

◆ Prediction

Expect continued small releases pinned to R-devel changes rather than new class-system features, with any further movement most likely in the validation and property-setter path that the last two feature changes both touched.

Alternatives to cfr and S7

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 cfr or S7.

See all cfr alternatives → · See all S7 alternatives →

Recent activity from cfr and S7

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

  1. 3mo agoS7Internal fixes for R-devel 4.6 compatibility
  2. 9mo agoS7Property setters gain an opt-out from validation
  3. 1y agocfrR-devel difftime patch and an individual-data vignette
  4. 1y agoS7Constructor rework and pre-4.3 support for @ access
  5. 2y agocfrSeverity estimator picks its own likelihood approximation
  6. 2y agocfrDelay-corrected severity and ascertainment estimation on CRAN
  7. 2y agoS7Per-property validators and better S3 method registration
  8. 2y agoS7First release: unions, set_props, and S4 virtual dispatch

Frequently asked questions

What is the difference between cfr and S7?

They serve adjacent needs but don't currently overlap on shipped themes. cfr and S7 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 cfr better than S7?

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

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

What are the best alternatives to S7?

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