← Back to home
Comparison · Infra & APIs

Greenbone Vulnerability Manager vs L1centrality

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

Greenbone Vulnerability Manager vs L1centrality: at a glance

FeatureGreenbone Vulnerability ManagerL1centrality
SectorInfra & APIsInfra & APIs
Velocity score6.30.0
Sparks · 30d10
Top themesvulnerability management, web application scanning, gmp protocol, report modelinggraph-analysis, centrality, r-package, visualization
Last editorial update11d ago1h ago
WebsiteVisit →Visit →

What is Greenbone Vulnerability Manager?

Greenbone's scanner daemon is growing a web-application scanning class beside its network roots.

gvmd releases every week or two, and the changelog splits cleanly in three: a sustained build-out of web application scanning, a rewrite of how reports are modeled and exported, and a long tail of memory-management fixes in the C core. Recent versions added web application scanner preferences, scanner verification, and a Web Application VT subtype with a database migration. The report work moved from ad-hoc XML toward a structured report model addressable through new GMP commands.

Read the full Greenbone Vulnerability Manager 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 →

Greenbone Vulnerability Manager vs L1centrality: editorial side-by-side

G6.3

Greenbone's scanner daemon is growing a web-application scanning class beside its network roots.

◆ Current state

gvmd releases every week or two, and the changelog splits cleanly in three: a sustained build-out of web application scanning, a rewrite of how reports are modeled and exported, and a long tail of memory-management fixes in the C core. Recent versions added web application scanner preferences, scanner verification, and a Web Application VT subtype with a database migration. The report work moved from ad-hoc XML toward a structured report model addressable through new GMP commands.

◆ Where it's heading

Greenbone is widening what gvmd can orchestrate. Network and container scanning were the existing surface; web application scanning is being brought to parity, with its own VT class, preferences, validation, and verification path. In parallel the GMP protocol is gaining first-class report retrieval commands, which makes report data consumable by tooling rather than only renderable. The bug-fix stream is dominated by frees and cleanup in long-lived report paths, the signature of a codebase under memory pressure at scale.

◆ Prediction

Web Application VTs now have a subtype, a migration, and scanner verification, but the audit and scan report commands were added separately; expect the report model work to fold web application results into the same structured retrieval path rather than leaving a parallel one.

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 Greenbone Vulnerability Manager 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 Greenbone Vulnerability Manager or L1centrality.

See all Greenbone Vulnerability Manager alternatives → · See all L1centrality alternatives →

Recent activity from Greenbone Vulnerability Manager and L1centrality

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

  1. 16d agoGreenbone Vulnerability Manageropenvasd library bumped to 23.9
  2. 16d agoGreenbone Vulnerability ManagerGMP gains a get_audit_report_hosts command
  3. 21d agoGreenbone Vulnerability ManagerWeb Application VTs become a first-class scan type
  4. 29d agoGreenbone Vulnerability ManagerStructured report model and the get_scan_report command
  5. 1mo agoGreenbone Vulnerability ManagerPer-object asset permissions and report-script trust checks
  6. 1mo agoGreenbone Vulnerability ManagerAggregate grouping and family-name fixes
  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 Greenbone Vulnerability Manager and L1centrality?

They serve adjacent needs but don't currently overlap on shipped themes. Greenbone Vulnerability Manager is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 Greenbone Vulnerability Manager better than L1centrality?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Greenbone Vulnerability Manager is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 Greenbone Vulnerability Manager?

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