← Back to home
Comparison · Infra & APIs

L1centrality vs SLmetrics

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

Shared themes:r-package

L1centrality vs SLmetrics: at a glance

FeatureL1centralitySLmetrics
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesgraph-analysis, centrality, r-package, visualizationmachine-learning, model-evaluation, performance, cpp-backend
Last editorial update1h ago2d 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 SLmetrics?

A young ML metrics package rewrote its own backend twice in six months chasing speed.

SLmetrics provides supervised learning evaluation metrics for R — confusion matrices, classification and regression measures, ROC and precision-recall curves — with the computation pushed into C++. After a series of pre-releases it now runs on an Armadillo backend, supports OpenMP parallelism and LAPACK/BLAS, and reports 5-20x speedups over its earlier implementations. The API has been reshaped for extensibility, with an estimator argument replacing the fixed aggregation options.

Read the full SLmetrics trajectory →

L1centrality vs SLmetrics: 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
SLmetrics
INFRA · APIS
0.0

A young ML metrics package rewrote its own backend twice in six months chasing speed.

◆ Current state

SLmetrics provides supervised learning evaluation metrics for R — confusion matrices, classification and regression measures, ROC and precision-recall curves — with the computation pushed into C++. After a series of pre-releases it now runs on an Armadillo backend, supports OpenMP parallelism and LAPACK/BLAS, and reports 5-20x speedups over its earlier implementations. The API has been reshaped for extensibility, with an estimator argument replacing the fixed aggregation options.

◆ Where it's heading

Every release in this timeline is about making the same metrics compute faster or compose better. The backend moved from Rcpp to plain C++, gained OpenMP, then was ported wholesale from Eigen to Armadillo with heavy templating. In parallel the author has been widening the API's joints: generic S3 signatures, an extensible estimator argument, and function signatures loose enough that wrapping packages can rename arguments. Bundled datasets and embedded formulas in the docs point at teaching and benchmarking use. The package still labels itself pre-release, which is consistent with how freely it has broken argument names along the way.

◆ Prediction

A stable non-pre-release version is the natural next step now that the backend has settled on Armadillo, though the repeated willingness to rename arguments suggests more API churn may come first.

Alternatives to L1centrality and SLmetrics

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

See all L1centrality alternatives → · See all SLmetrics alternatives →

Recent activity from L1centrality and SLmetrics

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

  1. 1mo agoL1centralityTypo fixes only
  2. 3mo agoL1centralityWarning message wording updated
  3. 3mo agoL1centralityMulti-group prominence and multicore local centrality
  4. 9mo agoL1centralityPlot methods for every result class, plus edge-weight transforms
  5. 1y agoSLmetricsArmadillo backend brings 5-20x speedups and an extensible metrics API
  6. 1y agoSLmetricsConsistent S3 signatures and three bundled datasets
  7. 1y agoSLmetricsRegression metrics 2-10x faster with reworked OpenMP controls
  8. 1y agoSLmetricsOpenMP parallelism and a soft-label entropy family
  9. 1y agoL1centralityHandles unnamed vertices; quantile type pinned
  10. 1y agoSLmetricsCross-entropy loss and relative RMSE with three normalisations
  11. 1y agoSLmetricsSample weights flow through the confusion matrix
  12. 1y agoL1centralityS3 classes for all results, plus a Gini coefficient

Frequently asked questions

What is the difference between L1centrality and SLmetrics?

Both compete on the same themes — r-package — within Infra & APIs. L1centrality and SLmetrics are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is L1centrality better than SLmetrics?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. L1centrality and SLmetrics are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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 SLmetrics?

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