← Back to home
Comparison · Infra & APIs

L1centrality vs profoc

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

Shared themes:r-package

L1centrality vs profoc: at a glance

FeatureL1centralityprofoc
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesgraph-analysis, centrality, r-package, visualizationforecasting, online-learning, r-package, rcpp
Last editorial update52m ago1d 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 profoc?

A forecast combination package that spun its profiler out into its own project

profoc combines probabilistic forecasts online, using the Bernstein online aggregation family with B-spline smoothing over quantiles and time. The recent releases are infrastructure rather than method: 1.3.4 removed a using namespace arma directive for CRAN compliance and closed a timer edge case, 1.3.3 adjusted the integration with rcpptimer against its now-stable 1.2.0 API. The last release to change what users can do was 1.3.0, which exposed the conline C++ class to R and exported init_experts_list(), make_basis_mats(), make_hat_mats() and post_process_model() so the engine can be driven directly.

Read the full profoc trajectory →

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

P
profoc
INFRA · APIS
0.0

A forecast combination package that spun its profiler out into its own project

◆ Current state

profoc combines probabilistic forecasts online, using the Bernstein online aggregation family with B-spline smoothing over quantiles and time. The recent releases are infrastructure rather than method: 1.3.4 removed a using namespace arma directive for CRAN compliance and closed a timer edge case, 1.3.3 adjusted the integration with rcpptimer against its now-stable 1.2.0 API. The last release to change what users can do was 1.3.0, which exposed the conline C++ class to R and exported init_experts_list(), make_basis_mats(), make_hat_mats() and post_process_model() so the engine can be driven directly.

◆ Where it's heading

The direction is toward a reusable C++ core with thin language bindings. The timing code that lived inside profoc was extracted into the standalone rcpptimer package in 1.3.2, deliberately so other R packages and Python projects could use it through cpptimer and cppytimer, and the clock header was reworked in 1.3.1 to maximise the code shared between the R and Python versions. Method work sits earlier in the history - periodic splines and penalties in 1.2.0, the penalty() function in 1.1.0 - while the recent cadence, a single release in the last sixteen months, points at a package the maintainer considers finished.

◆ Prediction

The repeated references to future Python use suggest the next significant work happens outside this package, in the shared C++ components, rather than in profoc's R surface.

Alternatives to L1centrality and profoc

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

See all L1centrality alternatives → · See all profoc alternatives →

Recent activity from L1centrality and profoc

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. 6mo agoprofocCRAN compliance fix removing a namespace directive
  5. 9mo agoL1centralityPlot methods for every result class, plus edge-weight transforms
  6. 1y agoL1centralityHandles unnamed vertices; quantile type pinned
  7. 1y agoL1centralityS3 classes for all results, plus a Gini coefficient
  8. 1y agoprofocTimer integration updated to the stable rcpptimer API
  9. 2y agoprofocTiming code extracted into the standalone rcpptimer package
  10. 2y agoprofocInteger overflow fix and Welford timing statistics
  11. 2y agoprofocThe conline C++ class opens up to R users
  12. 2y agoprofocQuantile crossing flagged and tidy methods added

Frequently asked questions

What is the difference between L1centrality and profoc?

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

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

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