← Back to home
Comparison · Infra & APIs

crandep vs NGINX

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

crandep vs NGINX: at a glance

FeaturecrandepNGINX
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themescran, dependency-network, power-law, mcmcweb-server, reverse-proxy, quic, security-hardening
Last editorial update1h ago44m ago
WebsiteVisit →Visit →

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.

Read the full crandep trajectory →

What is NGINX?

nginx returns to feature work with PROXY v2 upstream writes, and quietly adds JSON to core.

1.31.4 is the first mainline release in months that is not primarily a CVE response. It adds PROXY protocol version 2 write support for stream upstreams, special-cases the Host header for HTTP and gRPC upstreams, and tightens QUIC flow control on RESET_STREAM final sizes. Underneath those, core gained data model and JSON serialization libraries that nothing in this release consumes.

Read the full NGINX trajectory →

crandep vs NGINX: editorial side-by-side

C
crandep
INFRA · APIS
0.0

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.

N
NGINX
INFRA · APIS
2.5

nginx returns to feature work with PROXY v2 upstream writes, and quietly adds JSON to core.

◆ Current state

1.31.4 is the first mainline release in months that is not primarily a CVE response. It adds PROXY protocol version 2 write support for stream upstreams, special-cases the Host header for HTTP and gRPC upstreams, and tightens QUIC flow control on RESET_STREAM final sizes. Underneath those, core gained data model and JSON serialization libraries that nothing in this release consumes.

◆ Where it's heading

The five preceding releases were security releases: three CVEs in July across both branches, an HTTP/2 and gRPC buffer overflow and an HTTP/3 use-after-free in June. Against that run, 1.31.4 reads as the project returning to feature work, with F5 contributors visible across the stream and upstream changes and four first-time contributors landing fixes. The JSON and data-model libraries are the item worth watching, since general serialization is not something a proxy needs for proxying.

◆ Prediction

Those libraries have no consumer in this release, so the plausible next move is a feature that uses them, such as structured status output or configuration, rather than another round of parser hardening.

Alternatives to crandep and NGINX

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 NGINX.

See all crandep alternatives → · See all NGINX alternatives →

Recent activity from crandep and NGINX

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

  1. 1d agoNGINXPROXY protocol v2 upstream writes, plus QUIC and parser hardening
  2. 1mo agoNGINXThree CVEs: map regex overflow, slice disclosure, SSI use-after-free
  3. 1mo agoNGINXStable branch takes the same three CVE fixes
  4. 2mo agoNGINXBuffer overflow in HTTP/2 and gRPC proxy modules
  5. 2mo agoNGINXHTTP/3 use-after-free fixed; $ssl_sigalgs variable added
  6. 3mo agoNGINXRewrite module overflow with overlapping captures
  7. 1y agocrandepDependency harvest split in two so orphan packages stop disappearing
  8. 1y agocrandepTrailing commas in CRAN metadata no longer produce empty-name rows
  9. 2y agocrandepConstrained two-component mixture with continuity at the threshold
  10. 2y agocrandepArgument names normalised to x_max; MCMC wrapper defaults set
  11. 2y agocrandepTZP-power-law mixture fills the gap between the 2- and 3-component models
  12. 2y agocrandepProfile posteriors and chained MCMC wrappers for the mixture models

Frequently asked questions

What is the difference between crandep and NGINX?

They serve adjacent needs but don't currently overlap on shipped themes. NGINX is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is crandep better than NGINX?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. NGINX is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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 NGINX?

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