Traefik
Traefik's 2.11 line spends August fixing the names it generates for Kubernetes resources.
Comparison · Infra & APIs
crandep vs surveycore
A side-by-side editorial comparison of crandep and surveycore — release velocity, themes, recent moves, and the top alternatives to consider.
crandep vs surveycore: at a glance
What is crandep?
Half CRAN dependency scraper, half extreme-value modelling kit — and the scraper half keeps finding bugs.
crandep does two jobs that rarely share a package: it harvests the CRAN dependency network, and it fits power-law and extreme-value mixture models to the resulting degree distributions. The 2024 releases were all model work — profile posteriors, wrappers, a constrained variant, a TZP-power-law mixture between the two- and three-component models. The 2025 releases are entirely the other half, fixing what the harvester was silently getting wrong.
What is surveycore?
surveycore declared its API stable with every survey design type covered.
surveycore is the estimation engine of a two-package survey stack, handling design objects and variance estimation while surveytidy supplies the dplyr verbs on top. The June release marks it 1.0.0 and states the API is complete and stable across Taylor series linearization, replicate weights, two-phase and non-probability designs, with means, totals, frequencies, quantiles, ratios, correlations, regression, t-tests, ANOVA and effective sample size all in place.
crandep vs surveycore: editorial side-by-side
crandep
0.0INFRA · APIS
Half CRAN dependency scraper, half extreme-value modelling kit — and the scraper half keeps finding bugs.
◆ Current state
crandep does two jobs that rarely share a package: it harvests the CRAN dependency network, and it fits power-law and extreme-value mixture models to the resulting degree distributions. The 2024 releases were all model work — profile posteriors, wrappers, a constrained variant, a TZP-power-law mixture between the two- and three-component models. The 2025 releases are entirely the other half, fixing what the harvester was silently getting wrong.
◆ Where it's heading
The modelling side has settled into a family of mixtures with matching wrapper and profile-posterior functions, and has not gained a new component since mid-2024. Attention has shifted to data quality in the scraper, where two consecutive releases dealt with the same class of problem: rows that should not exist because of trailing commas in CRAN's own metadata, and rows that should exist but did not because orphan packages have no edges. For a package whose science is degree distributions, missing isolated nodes is a modelling error, not a formatting one.
◆ Prediction
Expect further hardening against CRAN metadata quirks in the harvesting functions; the mixture-model side looks feature-complete and is likely to stay quiet unless a new component model is published.
surveycore
0.0INFRA · APIS
surveycore declared its API stable with every survey design type covered.
◆ Current state
surveycore is the estimation engine of a two-package survey stack, handling design objects and variance estimation while surveytidy supplies the dplyr verbs on top. The June release marks it 1.0.0 and states the API is complete and stable across Taylor series linearization, replicate weights, two-phase and non-probability designs, with means, totals, frequencies, quantiles, ratios, correlations, regression, t-tests, ANOVA and effective sample size all in place.
◆ Where it's heading
The last months before 1.0.0 were spent making the awkward designs behave like the ordinary ones. Non-probability designs gained jackknife replicate schemes and got their bootstrap repweights routed through the replicate-weight variance estimator in survey_glm(), matching every other estimation function. The survey_collection abstraction — several surveys treated as one pseudo-data-frame — was tightened rather than extended: divergent grouping across members now errors instead of stitching a patchwork with bind_rows(), and the missing-variable argument was renamed and given a stored default on the collection itself. A documentation audit before 1.0.0 turned up six dispatch and print bugs and corrections across forty-plus files, which is the kind of thing that surfaces when an API is being frozen rather than extended.
◆ Prediction
A declared-stable API means the next releases should be additive or corrective rather than breaking, and the pre-1.0.0 pattern of breaking renames should stop. The tight version pinning between the two packages means surveytidy releases will keep following surveycore's.
Alternatives to crandep and surveycore
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 crandep or surveycore.
NGINX
nginx returns to feature work with PROXY v2 upstream writes, and quietly adds JSON to core.
ESPHome
ESPHome closes the 2026.8 cycle, but the release body is a bare link to the real notes.
vcfR
A genomics workhorse whose visible release feed stops dead in mid-2020.
dialr
The R phone-number package stopped only parsing numbers and started asking them where they are.
ggVennDiagram
A Venn diagram package whose public release notes say almost nothing — including about its copyright cleanup.
See all crandep alternatives → · See all surveycore alternatives →
Recent activity from crandep and surveycore
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agosurveycoreFirst stable release: all four survey design types complete ⚡
- 3mo agosurveycoreget_effective_n() computes effective sample size
- 3mo agosurveycoreCollections error on divergent grouping; .on_missing renamed
- 4mo agosurveycoreCRAN patch removing surveytidy from the vignette
- 1y agocrandepDependency harvest split in two so orphan packages stop disappearing
- 1y agocrandepTrailing commas in CRAN metadata no longer produce empty-name rows
- 2y agocrandepConstrained two-component mixture with continuity at the threshold
- 2y agocrandepArgument names normalised to x_max; MCMC wrapper defaults set
- 2y agocrandepTZP-power-law mixture fills the gap between the 2- and 3-component models
- 2y agocrandepProfile posteriors and chained MCMC wrappers for the mixture models
Frequently asked questions
What is the difference between crandep and surveycore?
They serve adjacent needs but don't currently overlap on shipped themes. crandep and surveycore 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 crandep better than surveycore?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. crandep and surveycore 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 crandep?
Top crandep alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "crandep alternatives" section above for the current picks, or visit /alternatives/crandep for the full list with editorial commentary on each.
What are the best alternatives to surveycore?
Top surveycore alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "surveycore alternatives" section above for the current picks, or visit /alternatives/surveycore for the full list with editorial commentary on each.