WPML
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
Comparison · Infra & APIs
L1centrality vs Quay
A side-by-side editorial comparison of L1centrality and Quay — release velocity, themes, recent moves, and the top alternatives to consider.
L1centrality vs Quay: at a glance
What is L1centrality?
A graph-centrality package that spent 2026 making its existing measures usable at scale, then went quiet.
L1centrality implements L1 centrality and prestige for graphs, including group, local, and neighbourhood variants plus MDS-based visualization. The measure set has been stable since 0.3.0; the work since has gone into interfaces around it — S3 classes with print and summary methods, plot methods for every result class, and in 0.5.0 both multi-group evaluation and multicore computation for the local variant. The two releases since have been a warning-message pass and a typo pass.
What is Quay?
Quay ships nothing but CVE remediation, mirrored across two supported branches
Every entry in Quay's recent history is a security maintenance release, and they arrive as coordinated pairs — a 3.10.x and a 3.12.x tag cut hours apart carrying the same fixes cherry-picked to each branch. The content is dependency remediation against tracked advisories plus two SSRF hardening fixes, one in proxy cache upstream registry configuration and one in repository mirroring sources. No feature work appears in the window.
L1centrality vs Quay: editorial side-by-side
L1centrality
0.0INFRA · APIS
A graph-centrality package that spent 2026 making its existing measures usable at scale, then went quiet.
◆ Current state
L1centrality implements L1 centrality and prestige for graphs, including group, local, and neighbourhood variants plus MDS-based visualization. The measure set has been stable since 0.3.0; the work since has gone into interfaces around it — S3 classes with print and summary methods, plot methods for every result class, and in 0.5.0 both multi-group evaluation and multicore computation for the local variant. The two releases since have been a warning-message pass and a typo pass.
◆ Where it's heading
The package has moved from defining measures to operationalizing them. 0.5.0 was the inflection: parallel local computation and list-valued group input both target users running these measures over many vertex sets or large graphs rather than illustrating them on one. The same release renamed weight_transform and eta to edge_weight_transform and vertex_weight, and added an explicit message when a distance matrix is received — the signature of a maintainer fielding the same misuse repeatedly.
◆ Prediction
The last two releases carry no functional change, so the near-term path is maintenance rather than new measures; a 0.6.0 would most likely extend parallelism beyond L1centLOC to the other computationally heavy variants.
Quay
5.0INFRA · APIS
Quay ships nothing but CVE remediation, mirrored across two supported branches
◆ Current state
Every entry in Quay's recent history is a security maintenance release, and they arrive as coordinated pairs — a 3.10.x and a 3.12.x tag cut hours apart carrying the same fixes cherry-picked to each branch. The content is dependency remediation against tracked advisories plus two SSRF hardening fixes, one in proxy cache upstream registry configuration and one in repository mirroring sources. No feature work appears in the window.
◆ Where it's heading
This is a registry in pure maintenance posture on its long-lived branches, with the release process itself automated down to changelog-bump commits. The recurring SSRF fixes across proxy cache and mirroring suggest a deliberate sweep through the code paths that fetch from upstream registries rather than isolated reports. Feature development, if it is happening, is landing on a branch this feed does not cover.
◆ Prediction
Expect the paired-branch cadence to continue at roughly the rate advisories land against the bundled Python and npm dependencies. The SSRF sweep looks close to complete, having now covered both proxy cache and mirroring.
Alternatives to L1centrality and Quay
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 L1centrality or Quay.
forestploter
A forest plot package that keeps handing users control of one more graphical detail.
ggInterval
Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.
rgm
A microbiome network model that got itself un-archived by deleting the dependency that killed it.
contagionchannels
Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.
tidyaudit
Pipeline provenance for tidyverse workflows, recording what changed at each step without keeping the data.
See all L1centrality alternatives → · See all Quay alternatives →
Recent activity from L1centrality and Quay
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 7d agoQuayv3.12.21 patches six advisories and blocks SSRF in mirroring
- 7d agoQuayv3.10.25 carries the same advisory fixes to the 3.10 branch
- 27d agoQuayv3.12.20 bumps Go and blocks SSRF in proxy cache config
- 1mo agoQuayv3.10.24 backports the Go bump and proxy cache SSRF fix
- 1mo agoL1centralityTypo fixes only
- 1mo agoQuayv3.10.23 clears PyJWT, urllib3 and shell-quote advisories
- 1mo agoQuayv3.12.19 clears the same four dependency advisories
- 3mo agoL1centralityWarning message wording updated
- 3mo agoL1centralityMulti-group prominence and multicore local centrality
- 9mo agoL1centralityPlot methods for every result class, plus edge-weight transforms
- 1y agoL1centralityHandles unnamed vertices; quantile type pinned
- 1y agoL1centralityS3 classes for all results, plus a Gini coefficient
Frequently asked questions
What is the difference between L1centrality and Quay?
They serve adjacent needs but don't currently overlap on shipped themes. Quay is currently shipping more aggressively (velocity 5.0 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 L1centrality better than Quay?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Quay is currently shipping more aggressively (velocity 5.0 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 L1centrality?
Top L1centrality alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "L1centrality alternatives" section above for the current picks, or visit /alternatives/l1centrality for the full list with editorial commentary on each.
What are the best alternatives to Quay?
Top Quay alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Quay alternatives" section above for the current picks, or visit /alternatives/quay for the full list with editorial commentary on each.