rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
Comparison · Infra & APIs
coga vs packageRank
A side-by-side editorial comparison of coga and packageRank — release velocity, themes, recent moves, and the top alternatives to consider.
coga vs packageRank: at a glance
What is coga?
A gamma-convolution density package that reached completion in 2018 and has coasted since.
coga computes densities, distribution functions and random numbers for convolutions of gamma distributions, with the numerical work in C++ through Rcpp. It has been feature-complete since 1.0.0 in 2018, and every release in the seven years since has been maintenance: a documentation alias for CRAN, a compiler warning, a maintainer email change, and an Rcpp update requiring Rf_error calls to be guarded. The one functional addition in that period, in 1.1.0, was an unexported function added explicitly for research use.
What is packageRank?
CRAN download analytics maintained one micro-change at a time, hundreds per year
packageRank computes download counts and percentile ranks from CRAN's logs, with a filtering layer that tries to separate real installs from mirrors, sequences and bots. The recent releases are dense lists of small changes — thirty or more per version — spread across plot arguments, filter behaviour, and the cranDistribution object that now absorbs what packageDistribution() used to do separately.
coga vs packageRank: editorial side-by-side
coga
0.0INFRA · APIS
A gamma-convolution density package that reached completion in 2018 and has coasted since.
◆ Current state
coga computes densities, distribution functions and random numbers for convolutions of gamma distributions, with the numerical work in C++ through Rcpp. It has been feature-complete since 1.0.0 in 2018, and every release in the seven years since has been maintenance: a documentation alias for CRAN, a compiler warning, a maintainer email change, and an Rcpp update requiring Rf_error calls to be guarded. The one functional addition in that period, in 1.1.0, was an unexported function added explicitly for research use.
◆ Where it's heading
This is a finished package being kept alive rather than developed. The releases track external pressure exactly: CRAN documentation requirements, compiler warnings, Rcpp API changes. Its maintenance is visibly shared with smam, the same maintainer's animal-movement package, which received the same email update, the same format-security fix and the same Rcpp guard within a minute or twenty of coga each time. Neither package is being extended; both are being kept installable.
◆ Prediction
Expect nothing but CRAN and toolchain maintenance, arriving whenever Rcpp or R's check requirements change, and arriving alongside smam. There is no signal in these entries of planned functional work.
packageRank
0.0INFRA · APIS
CRAN download analytics maintained one micro-change at a time, hundreds per year
◆ Current state
packageRank computes download counts and percentile ranks from CRAN's logs, with a filtering layer that tries to separate real installs from mirrors, sequences and bots. The recent releases are dense lists of small changes — thirty or more per version — spread across plot arguments, filter behaviour, and the cranDistribution object that now absorbs what packageDistribution() used to do separately.
◆ Where it's heading
There is no directional arc here; there is a maintainer keeping a measurement instrument calibrated against a data source that keeps moving. CRAN's logs went missing for a week in 2025 and the package now ships those dates as data and draws them as polygons on every plot. A chatgpt argument has been threaded through the plotting functions since 0.9.6. Function surface churns constantly — arguments renamed, plot helpers archived, others integrated.
◆ Prediction
Given the cadence, the next release will be another few dozen adjustments concentrated wherever CRAN's logs last surprised the maintainer. The consolidation of plotting arguments toward a single axis.package annotation looks unfinished.
Alternatives to coga and packageRank
Other Infra & APIs 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 coga or packageRank.
massProps
A mass-properties rollup spends a year on documentation and follows its sibling's API
writeAlizer
Six months of releases and not one of them touched the scoring models
samplr
A cognitive-science sampling package ships once, then goes quiet for eighteen months
stochvol
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
midr
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
See all coga alternatives → · See all packageRank alternatives →
Recent activity from coga and packageRank
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 5mo agopackageRankPackage and version axis annotations across every plot
- 5mo agocogaRcpp attributes regenerated; email updated
- 10mo agopackageRankMissing CRAN log dates shipped as data and drawn on plots
- 1y agopackageRankWeekend and version overlays for the base graphics path
- 1y agopackageRankPackage history prefers CRAN over the pkgsearch fallback
- 1y agopackageRankDistribution summaries gain totals and a top-N default
- 1y agopackageRankcranDistribution() object and a direct query family
- 2y agocogaMaintainer email updated
- 2y agocogaCompiler format-security warning resolved
- 3y agocogaPackage documentation alias added for CRAN
- 6y agocogaUnexported density variant added for research use
- 8y agocoga1.0.0 declares the package complete and documented
Frequently asked questions
What is the difference between coga and packageRank?
They serve adjacent needs but don't currently overlap on shipped themes. coga and packageRank 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 coga better than packageRank?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. coga and packageRank 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 Infra & APIs products to evaluate alongside.
What are the best alternatives to coga?
Top coga alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "coga alternatives" section above for the current picks, or visit /alternatives/coga for the full list with editorial commentary on each.
What are the best alternatives to packageRank?
Top packageRank alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "packageRank alternatives" section above for the current picks, or visit /alternatives/packagerank for the full list with editorial commentary on each.