← Back to home
Comparison · Infra & APIs

cvms vs L1centrality

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

Shared themes:r-packagevisualization

cvms vs L1centrality: at a glance

FeaturecvmsL1centrality
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themescross-validation, r-package, model-evaluation, visualizationgraph-analysis, centrality, r-package, visualization
Last editorial update1d ago56m ago
WebsiteVisit →Visit →

What is cvms?

A cross-validation package whose real development has moved to its plotting function

cvms runs repeated cross-validation over model formulas and reports comparable metrics. The 2.0.0 release was a breaking correctness fix: every function accepting fold_cols mismatched training and testing data when fold indices were non-sequential, did not start at 1, or were strings, because the iteration index was compared against the raw fold value rather than its factor level index. 2.0.1 restored coefficient extraction for nnet::multinom and mixed models by supplying an environment containing the training data, and followed lme4's move of findbars() into the reformulas package.

Read the full cvms 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 →

cvms vs L1centrality: editorial side-by-side

C
cvms
INFRA · APIS
0.0

A cross-validation package whose real development has moved to its plotting function

◆ Current state

cvms runs repeated cross-validation over model formulas and reports comparable metrics. The 2.0.0 release was a breaking correctness fix: every function accepting fold_cols mismatched training and testing data when fold indices were non-sequential, did not start at 1, or were strings, because the iteration index was compared against the raw fold value rather than its factor level index. 2.0.1 restored coefficient extraction for nnet::multinom and mixed models by supplying an environment containing the training data, and followed lme4's move of findbars() into the reformulas package.

◆ Where it's heading

Two threads run in parallel and only one is about cross-validation. The plotting function plot_confusion_matrix() has absorbed most feature work since 1.5.0 - custom gradient palettes, intensity limits, per-tile settings, dynamic font colors keyed to value thresholds, and arguments that accept functions rather than constants - to the point where a companion web application exists for using it without code. The cross-validation core, by contrast, sees maintenance: upstream compatibility fixes for pROC, ggnewscale and ggplot2, and the fold-matching correction that finally forced a major version.

◆ Prediction

Expect continued option growth in the confusion matrix plotting surface, since that is where nearly every release since 1.5.0 has spent its changes, with core cross-validation changes arriving only as upstream packages force them.

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 cvms 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 cvms or L1centrality.

See all cvms alternatives → · See all L1centrality alternatives →

Recent activity from cvms and L1centrality

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

  1. 1mo agoL1centralityTypo fixes only
  2. 2mo agocvmsCoefficient extraction restored for multinom and mixed models
  3. 3mo agoL1centralityWarning message wording updated
  4. 3mo agoL1centralityMulti-group prominence and multicore local centrality
  5. 9mo agocvmsBreaking fix for mismatched folds with non-sequential fold IDs
  6. 9mo agoL1centralityPlot methods for every result class, plus edge-weight transforms
  7. 11mo agocvmsTest compatibility with pROC 1.19 and a deprecation warning fix
  8. 1y agocvmsConfusion matrix fonts and colors can now be computed from the values
  9. 1y agocvmsTile intensity by row or column percentages
  10. 1y agocvmsMultinom coefficient extraction fix after a parameters update
  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 cvms and L1centrality?

Both compete on the same themes — r-package, visualization — within Infra & APIs. cvms and L1centrality 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 cvms better than L1centrality?

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

Top cvms alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "cvms alternatives" section above for the current picks, or visit /alternatives/cvms 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.