← Back to home
Comparison · Infra & APIs

packageRank vs TrendLSW

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

Shared themes:cran

packageRank vs TrendLSW: at a glance

FeaturepackageRankTrendLSW
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themescran, download-analytics, log-filtering, visualizationtime-series, wavelets, defaults, plotting
Last editorial update2h ago40m ago
WebsiteVisit →Visit →

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.

Read the full packageRank trajectory →

What is TrendLSW?

Wavelet trend estimation tightens the defaults it shipped with.

TrendLSW estimates trend and evolutionary wavelet spectrum for locally stationary time series through a single TLSW() entry point. Its history since the first CRAN appearance is short and centres on defaults and plotting around that function, plus one dataset addition. The latest entry carries both the 1.0.4 and 1.0.3 notes in one body.

Read the full TrendLSW trajectory →

packageRank vs TrendLSW: editorial side-by-side

P
packageRank
INFRA · APIS
0.0

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.

T
TrendLSW
INFRA · APIS
0.0

Wavelet trend estimation tightens the defaults it shipped with.

◆ Current state

TrendLSW estimates trend and evolutionary wavelet spectrum for locally stationary time series through a single TLSW() entry point. Its history since the first CRAN appearance is short and centres on defaults and plotting around that function, plus one dataset addition. The latest entry carries both the 1.0.4 and 1.0.3 notes in one body.

◆ Where it's heading

The package has moved from getting onto CRAN to correcting the choices it launched with: the spectrum filter defaults were swapped to their trend counterparts, the plot.CI switch was removed in favour of inferring it from what was actually computed, and an example was shrunk to fit check timings. This is consolidation around a stable API rather than expansion.

◆ Prediction

Further releases most likely continue tuning TLSW() defaults and plot behaviour; the entries show no work toward new estimators.

Alternatives to packageRank and TrendLSW

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 packageRank or TrendLSW.

See all packageRank alternatives → · See all TrendLSW alternatives →

Recent activity from packageRank and TrendLSW

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

  1. 5mo agopackageRankPackage and version axis annotations across every plot
  2. 8mo agoTrendLSWTrend filter defaults replace spectrum defaults; plot.CI dropped
  3. 10mo agopackageRankMissing CRAN log dates shipped as data and drawn on plots
  4. 1y agopackageRankWeekend and version overlays for the base graphics path
  5. 1y agopackageRankPackage history prefers CRAN over the pkgsearch fallback
  6. 1y agopackageRankDistribution summaries gain totals and a top-N default
  7. 1y agopackageRankcranDistribution() object and a direct query family
  8. 2y agoTrendLSWNew z.acc and z.labels datasets shipped with the package
  9. 2y agoTrendLSWDescription field and plot.TLSW documentation fixes

Frequently asked questions

What is the difference between packageRank and TrendLSW?

Both compete on the same themes — cran — within Infra & APIs. packageRank and TrendLSW 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 packageRank better than TrendLSW?

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

What are the best alternatives to TrendLSW?

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