rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
Comparison · Infra & APIs
packageRank vs prospectr
A side-by-side editorial comparison of packageRank and prospectr — release velocity, themes, recent moves, and the top alternatives to consider.
packageRank vs prospectr: at a glance
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.
What is prospectr?
prospectr spent its biggest release in years fixing spectra it had been quietly mangling.
prospectr provides the signal-processing layer for near-infrared and visible spectroscopy in R — Savitzky-Golay and gap-segment derivatives, standard normal variate, detrending, continuum removal, splice correction, plus calibration sampling algorithms like Kennard-Stone and DUPLEX and readers for ASD and BUCHI NIRCal instrument files. The May release is the substantial one: a long list of corrections to functions that were returning wrong or missing values rather than failing.
packageRank vs prospectr: editorial side-by-side
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.
prospectr
0.0INFRA · APIS
prospectr spent its biggest release in years fixing spectra it had been quietly mangling.
◆ Current state
prospectr provides the signal-processing layer for near-infrared and visible spectroscopy in R — Savitzky-Golay and gap-segment derivatives, standard normal variate, detrending, continuum removal, splice correction, plus calibration sampling algorithms like Kennard-Stone and DUPLEX and readers for ASD and BUCHI NIRCal instrument files. The May release is the substantial one: a long list of corrections to functions that were returning wrong or missing values rather than failing.
◆ Where it's heading
The recent work is corrective rather than additive, and several items changed results silently before being caught. continuumRemoval() derived its convex-hull boundary offset from a fixed one-wavelength assumption that broke for fine-resolution spectra or non-nanometre units; cochranTest() passed an invalid argument name to prcomp() and produced incorrect principal component scores; readASD() silently dropped spectra in one branch of its text path. Two file readers were leaking connections. Alongside that runs a smaller thread of decoupling preprocessing steps from each other, most visibly detrend() gaining an snv argument so polynomial detrending can run without the SNV transform that Barnes et al. bundled with it.
◆ Prediction
The detrend() decoupling is the only recent addition and it fits a broader pipeline-composition direction, so similar separation of other bundled preprocessing steps is the plausible next move. The misspelled substraction argument now carries a deprecation warning, which schedules its removal for a future release.
Alternatives to packageRank and prospectr
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 prospectr.
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 packageRank alternatives → · See all prospectr alternatives →
Recent activity from packageRank and prospectr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoprospectrdetrend() can run without a prior SNV transformation
- 2mo agoprospectrContinuum removal, SNV and cochranTest corrected; readers stop leaking
- 5mo agopackageRankPackage and version axis annotations across every plot
- 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 agoprospectrread_nircal() sample ID field fix
- 1y agopackageRankDistribution summaries gain totals and a top-N default
- 1y agopackageRankcranDistribution() object and a direct query family
- 3y agoprospectrNon-UTF8 sample IDs no longer become NA
- 4y agoprospectrkenStone() bug fix
- 4y agoprospectrread_nircal() execution failure fixed
Frequently asked questions
What is the difference between packageRank and prospectr?
They serve adjacent needs but don't currently overlap on shipped themes. packageRank and prospectr 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 prospectr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. packageRank and prospectr 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 prospectr?
Top prospectr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "prospectr alternatives" section above for the current picks, or visit /alternatives/prospectr for the full list with editorial commentary on each.