← Back to home
Comparison · Infra & APIs

L1centrality vs survivoR

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

Shared themes:r-package

L1centrality vs survivoR: at a glance

FeatureL1centralitysurvivoR
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesgraph-analysis, centrality, r-package, visualizationdata-package, r-package, television, reality-tv
Last editorial update58m 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 survivoR?

A Survivor data package that keeps turning a TV show into a relational database

survivoR ships Survivor franchise data as R data frames covering the US, Australian, UK and New Zealand versions. Recent releases track broadcast: US48, US49 and US50 arrived across 2.3.6, 2.3.9 and 2.3.12, alongside AU09, AU12 and Australia vs. The World. The 2.3.12 release also reworked castaway_scores into an explicit three-tier structure - standardised residual scores, probabilistic scores bounded on [0,1], and combined scores - and added advantage_timeline as a long-format view of advantage movement.

Read the full survivoR trajectory →

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

A Survivor data package that keeps turning a TV show into a relational database

◆ Current state

survivoR ships Survivor franchise data as R data frames covering the US, Australian, UK and New Zealand versions. Recent releases track broadcast: US48, US49 and US50 arrived across 2.3.6, 2.3.9 and 2.3.12, alongside AU09, AU12 and Australia vs. The World. The 2.3.12 release also reworked castaway_scores into an explicit three-tier structure - standardised residual scores, probabilistic scores bounded on [0,1], and combined scores - and added advantage_timeline as a long-format view of advantage movement.

◆ Where it's heading

The work is less about adding seasons than about making the tables join cleanly. 2.3.1 rebuilt challenge_description and challenge_results around a shared challenge_id, added challenge characteristic flags and result notes, and put logical finalist, winner and jury flags on castaways. Since then the pattern repeats at smaller scale: boot_order as its own table, season_name deprecated everywhere except season_summary, castaways cleaned so people booted twice appear once. Derived analytical columns are being separated from raw records rather than mixed into them.

◆ Prediction

Expect the next release to add the current season's data on the same broadcast-following cadence, with any structural work continuing to split derived scores out of the raw tables.

Alternatives to L1centrality and survivoR

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

See all L1centrality alternatives → · See all survivoR alternatives →

Recent activity from L1centrality and survivoR

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

  1. 1mo agoL1centralityTypo fixes only
  2. 2mo agosurvivoRUS50 and AU12 land, castaway scores split into three tiers
  3. 3mo agoL1centralityWarning message wording updated
  4. 3mo agoL1centralityMulti-group prominence and multicore local centrality
  5. 7mo agosurvivoRUS49 data completed and season 50 cast added
  6. 9mo agoL1centralityPlot methods for every result class, plus edge-weight transforms
  7. 11mo agosurvivoRSurvivor Australia vs. The World added
  8. 1y agosurvivoRboot_order table added and castaways deduplicated
  9. 1y agoL1centralityHandles unnamed vertices; quantile type pinned
  10. 1y agoL1centralityS3 classes for all results, plus a Gini coefficient
  11. 2y agosurvivoRComplete AU09 data reaches CRAN
  12. 2y agosurvivoRChallenge tables rebuilt around a shared linking key

Frequently asked questions

What is the difference between L1centrality and survivoR?

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

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

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