← Back to home
Comparison · Infra & APIs

L1centrality vs Skipper

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

L1centrality vs Skipper: at a glance

FeatureL1centralitySkipper
SectorInfra & APIsInfra & APIs
Velocity score0.05.0
Sparks · 30d00
Top themesgraph-analysis, centrality, r-package, visualizationreverse-proxy, kubernetes, http2, load-balancing
Last editorial update52m ago20h 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 Skipper?

Zalando's ingress proxy finally speaks HTTP/2 cleartext end to end

Skipper ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.57, which enables h2c on the server handler, the proxy client, and the net client, with a new h2c:// route scheme and Kubernetes appProtocol wiring. Everything else in the window is Dependabot traffic and two narrow fixes to token introspection and grant auth.

Read the full Skipper trajectory →

L1centrality vs Skipper: 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.

S
Skipper
INFRA · APIS
5.0

Zalando's ingress proxy finally speaks HTTP/2 cleartext end to end

◆ Current state

Skipper ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.57, which enables h2c on the server handler, the proxy client, and the net client, with a new h2c:// route scheme and Kubernetes appProtocol wiring. Everything else in the window is Dependabot traffic and two narrow fixes to token introspection and grant auth.

◆ Where it's heading

The release cadence is a stream of small, individually unremarkable tags where the occasional protocol or load-balancing change is the only thing worth reading. Recent substance has clustered on the data path: leastRequests balancing in v0.27.53, h2c now. The auth filters are being maintained rather than extended, with fixes rather than new capability.

◆ Prediction

Expect the h2c work to generate follow-up fixes as it meets real gRPC backends, since the release notes already show HTTP Upgrade negotiation failing while direct prior knowledge works.

Alternatives to L1centrality and Skipper

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

See all L1centrality alternatives → · See all Skipper alternatives →

Recent activity from L1centrality and Skipper

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

  1. 22h agoSkipperFix token introspection handling
  2. 22h agoSkipperFix grant auth flow
  3. 1d agoSkipperUpdate outdated golang.org/x dependencies
  4. 2d agoSkipperh2c enabled for server handler, proxy client and net client
  5. 2d agoSkipperBump protobuf off a pre-release pin
  6. 2d agoSkipperBump the CodeQL upload-sarif action
  7. 1mo agoL1centralityTypo fixes only
  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 L1centrality and Skipper?

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

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

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