← Back to home
Comparison · Infra & APIs

L1centrality vs Nebula

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

L1centrality vs Nebula: at a glance

FeatureL1centralityNebula
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themesgraph-analysis, centrality, r-package, visualizationmesh-vpn, overlay-network, certificates, ipv6
Last editorial update58m ago8d ago
WebsiteVisit →Visit →

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 →

What is Nebula?

Overlay network that rewrote its certificate format, then spent a year fixing what it exposed.

Nebula is a peer-to-peer mesh VPN built around a certificate authority model. The v1.10.0 release was the pivot: IPv6 and multiple addresses in the overlay, plus a new v2 ASN.1 certificate format with a unified interface for external implementations. Everything since has been consequence management — a P256 signature malleability issue that allowed blocklist bypass, a source-IP acceptance flaw tied to the new multi-address certificates, and a run of fixes around route tables and Windows listeners.

Read the full Nebula trajectory →

L1centrality vs Nebula: editorial side-by-side

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.

N
Nebula
INFRA · APIS
2.5

Overlay network that rewrote its certificate format, then spent a year fixing what it exposed.

◆ Current state

Nebula is a peer-to-peer mesh VPN built around a certificate authority model. The v1.10.0 release was the pivot: IPv6 and multiple addresses in the overlay, plus a new v2 ASN.1 certificate format with a unified interface for external implementations. Everything since has been consequence management — a P256 signature malleability issue that allowed blocklist bypass, a source-IP acceptance flaw tied to the new multi-address certificates, and a run of fixes around route tables and Windows listeners.

◆ Where it's heading

The project has moved from single-IPv4-per-node assumptions toward a genuinely flexible addressing model, and the security fixes since v1.10.0 map directly onto that change — the new certificate features widened what the code has to validate. v1.11.0 shifts attention to the operational surface instead: structured logging, corrected firewall reject-versus-drop semantics, and Windows WFP filters installed by default.

◆ Prediction

The stated plan to assert low-s signature form when validating certificates is the concrete next step visible in these entries; expect it to land as a breaking validation change in a future release.

Alternatives to L1centrality and Nebula

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

See all L1centrality alternatives → · See all Nebula alternatives →

Recent activity from L1centrality and Nebula

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

  1. 26d agoNebulaBreaking: slog logging, corrected firewall reject/drop directions, Windows WFP filters
  2. 1mo agoL1centralityTypo fixes only
  3. 3mo agoL1centralityWarning message wording updated
  4. 3mo agoL1centralityMulti-group prominence and multicore local centrality
  5. 6mo agoNebulaP256 signature malleability allowed blocklist bypass
  6. 6mo agoNebulaFix panic in use_system_route_table introduced by the previous release
  7. 7mo agoNebulaRoute-reload, handshake, and Windows listener fixes after the v1.10 rework
  8. 8mo agoNebulaIPv6 and multiple addresses in the overlay, plus a v2 certificate format
  9. 9mo agoL1centralityPlot methods for every result class, plus edge-weight transforms
  10. 10mo agoNebulaPackets accepted from erroneous source IPs with unsafe_routes or multi-IP certificates
  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 L1centrality and Nebula?

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

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

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