← Back to home
Comparison · Infra & APIs

AdGuard Home vs L1centrality

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

AdGuard Home vs L1centrality: at a glance

FeatureAdGuard HomeL1centrality
SectorInfra & APIsInfra & APIs
Velocity score5.00.0
Sparks · 30d00
Top themesdns, ad-blocking, security, dns-over-quicgraph-analysis, centrality, r-package, visualization
Last editorial update20h ago1h ago
WebsiteVisit →Visit →

What is AdGuard Home?

AdGuard Home patches a DNS-over-QUIC resource exhaustion advisory and moves edge to the new UI

v0.107.79 is presented as a stability release but carries the security work: a Go update for the vulnerabilities fixed in 1.26.6 and hardening against resource exhaustion over DNS-over-QUIC, published as GHSA-w6v6-f44j-3rj2. Alongside it, bootstrap server config accepts comments, install APIs gain a language property, static lease hostnames can be removed over HTTP, strict_sni_check is deprecated, and DNS64 stops treating unresolved CNAME/DNAME answers as the end of the chain.

Read the full AdGuard Home trajectory →

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.

Read the full L1centrality trajectory →

AdGuard Home vs L1centrality: editorial side-by-side

A
AdGuard Home
INFRA · APIS
5.0

AdGuard Home patches a DNS-over-QUIC resource exhaustion advisory and moves edge to the new UI

◆ Current state

v0.107.79 is presented as a stability release but carries the security work: a Go update for the vulnerabilities fixed in 1.26.6 and hardening against resource exhaustion over DNS-over-QUIC, published as GHSA-w6v6-f44j-3rj2. Alongside it, bootstrap server config accepts comments, install APIs gain a language property, static lease hostnames can be removed over HTTP, strict_sni_check is deprecated, and DNS64 stops treating unresolved CNAME/DNAME answers as the end of the chain.

◆ Where it's heading

Two channels run in parallel — the 0.107 stable line and the 0.108 beta — and the edge channel has now switched to the new UI and versioning scheme, which is the first concrete sign that the 0.108 work is being staged for release. Stable releases keep absorbing protocol correctness fixes and DNS-over-QUIC hardening.

◆ Prediction

With edge already on the new UI and versioning scheme, the 0.108 line is the likely destination for that switch, and strict_sni_check being deprecated now points to its removal there.

L
L1centrality
INFRA · APIS
0.0

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.

Alternatives to AdGuard Home and L1centrality

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 AdGuard Home or L1centrality.

See all AdGuard Home alternatives → · See all L1centrality alternatives →

Recent activity from AdGuard Home and L1centrality

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

  1. 23h agoAdGuard HomeAdGuard Home 0.107.79 hardens DNS-over-QUIC against resource exhaustion
  2. 20d agoAdGuard HomeBeta b.90 carries the DNS-over-QUIC exhaustion fix
  3. 1mo agoAdGuard HomeBeta b.89 hardens against JIGGLE attacks (GHSA-p5f5-3p5g-rfjw)
  4. 1mo agoL1centralityTypo fixes only
  5. 1mo agoAdGuard Home0.107.78: over half the changelog is security fixes
  6. 2mo agoAdGuard HomeBeta b.88 patches path traversal in GLiNET auth (CVE-2026-41448)
  7. 2mo agoAdGuard Home0.107.77 patches a community-reported vulnerability
  8. 3mo agoL1centralityWarning message wording updated
  9. 3mo agoL1centralityMulti-group prominence and multicore local centrality
  10. 9mo agoL1centralityPlot methods for every result class, plus edge-weight transforms
  11. 1y agoL1centralityHandles unnamed vertices; quantile type pinned
  12. 1y agoL1centralityS3 classes for all results, plus a Gini coefficient

Frequently asked questions

What is the difference between AdGuard Home and L1centrality?

They serve adjacent needs but don't currently overlap on shipped themes. AdGuard Home 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 AdGuard Home better than L1centrality?

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

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

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.