Lima
Lima 2.3 nears release, with a Windows path that drops QEMU and a new TUI
Comparison · Infra & APIs
Greenbone Vulnerability Manager vs runc
A side-by-side editorial comparison of Greenbone Vulnerability Manager and runc — release velocity, themes, recent moves, and the top alternatives to consider.
Greenbone Vulnerability Manager vs runc: at a glance
| Feature | Greenbone Vulnerability Manager | runc |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 5.0 | 2.5 |
| Sparks · 30d | 0 | 0 |
| Top themes | vulnerability-management, active-directory, reporting, agents | container runtime, release candidate, breaking changes, kernel workaround |
| Last editorial update | 1h ago | 3h ago |
| Website | Visit → | Visit → |
What is Greenbone Vulnerability Manager?
Greenbone's gvmd starts on Active Directory credentials as report exports settle.
26.43.0 on 27 October adds an LDAP/AD credential type, a GMP command to verify it and feature flags for AD integration, plus encryption and anonymization options for agent bundles. The surrounding releases finish the report export work: cancellation in 26.40.0, then reuse of completed exports and repeatable downloads. 26.41.0 also adds executable report formats and validates keys and certificates when credentials are modified.
What is runc?
runc 1.6.0-rc.1 lifts the 1024-CPU limit and refuses settings it used to quietly ignore
The 1.6.0 cycle opened on October 6 with a first release candidate that is mostly cleanup: deprecated libcontainer APIs removed, Go 1.26 now required, urfave/cli moved from v1 to v3, and the binary about 15% smaller on amd64. The changes with operational weight are that cpuAffinity and NUMA memoryPolicy no longer stop at 1024 CPUs or nodes, and that a container asking for a read-only rootfs without its own mount namespace is now refused. Eleven days earlier 1.5.2 worked around a kernel bug, present since v6.17, that corrupted memory inside runc and caused random crashes on cgroup v2. It also stopped runc exec --cgroup from escaping into a sibling cgroup.
Greenbone Vulnerability Manager vs runc: editorial side-by-side
Greenbone Vulnerability Manager
5.0INFRA · APIS
Greenbone's gvmd starts on Active Directory credentials as report exports settle.
◆ Current state
26.43.0 on 27 October adds an LDAP/AD credential type, a GMP command to verify it and feature flags for AD integration, plus encryption and anonymization options for agent bundles. The surrounding releases finish the report export work: cancellation in 26.40.0, then reuse of completed exports and repeatable downloads. 26.41.0 also adds executable report formats and validates keys and certificates when credentials are modified.
◆ Where it's heading
Report export, the summer's main thread, has reached the fix-and-polish stage. New work is moving toward agents and directory integration: agent OS metadata, group scheduling delay and bundle options sit alongside the AD credential type. The steady memory-leak fixes suggest a code base being tightened as these features land.
◆ Prediction
AD integration sits behind feature flags, so expect follow-up releases to complete it. The entries don't say when it will be enabled by default.
runc
2.5INFRA · APIS
runc 1.6.0-rc.1 lifts the 1024-CPU limit and refuses settings it used to quietly ignore
◆ Current state
The 1.6.0 cycle opened on October 6 with a first release candidate that is mostly cleanup: deprecated libcontainer APIs removed, Go 1.26 now required, urfave/cli moved from v1 to v3, and the binary about 15% smaller on amd64. The changes with operational weight are that cpuAffinity and NUMA memoryPolicy no longer stop at 1024 CPUs or nodes, and that a container asking for a read-only rootfs without its own mount namespace is now refused. Eleven days earlier 1.5.2 worked around a kernel bug, present since v6.17, that corrupted memory inside runc and caused random crashes on cgroup v2. It also stopped runc exec --cgroup from escaping into a sibling cgroup.
◆ Where it's heading
The project keeps converting silent behaviour into explicit behaviour. Read-only requests that were ignored now fail, a umask that was dropped is now honoured, and poststart hooks moved to conform to the runtime spec. The same maintainers are shrinking the surface underneath, dropping the deprecated API and the high-level cilium/ebpf path, which took roughly 7.5% off the 1.5.2 binary. Stricter behaviour plus a smaller dependency set is what a component under every container host would be expected to do between majors.
◆ Prediction
1.5.0's notes pointed to a 1.6.0 in late October 2026, and the feed so far shows only rc.1, so further release candidates or the final are the next entries to expect. The refused read-only configurations are the change most likely to surface as user reports during testing.
Alternatives to Greenbone Vulnerability Manager and runc
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 runc.
Verdaccio
Verdaccio's v9 pre-release counter reaches 41, and the notes still say nothing
Snort 3
Snort 3.12.4 pairs a long memory-safety pass with detection speed work
HAProxy Kubernetes Ingress Controller
Nineteen patches into 3.2, HAProxy's ingress controller is mostly bumping dependencies
Honeycomb
Honeycomb is working on the first ten minutes, not just the incident
Talos Linux
Talos 1.15's alpha keeps moving: a silent containerd config trap and declarative CPU control
See all Greenbone Vulnerability Manager alternatives → · See all runc alternatives →
Recent activity from Greenbone Vulnerability Manager and runc
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 5d agoGreenbone Vulnerability Managergvmd 26.43.0: LDAP/AD credentials and agent-bundle encryption
- 18d agoGreenbone Vulnerability Managergvmd 26.42.0: Scan config in report XML, export fixes
- 20d agoGreenbone Vulnerability Managergvmd 26.41.0: Executable report formats, credential validation
- 26d agoruncRelease candidate lifts 1024-CPU limit, removes deprecated APIs
- 1mo agoGreenbone Vulnerability Managergvmd 26.40.2: Web target and agent error-path fixes
- 1mo agoruncWorkaround for kernel bug that crashed runc on cgroup v2
- 1mo agoGreenbone Vulnerability Managergvmd 26.40.1: Sensor scanner port handling, leak fixes
- 1mo agoGreenbone Vulnerability Managergvmd 26.40.0: Cancel report exports over GMP
- 3mo agorunctmpfs regression on Ubuntu 20.04 kernels fixed
- 4mo agoruncrunc 1.5.0 stable, with dated support windows for older branches
- 4mo agoruncCVE-2026-41579: /dev symlink host write access fixed
- 4mo agoruncRelease candidate carrying the CVE-2026-41579 fix
Frequently asked questions
What is the difference between Greenbone Vulnerability Manager and runc?
They serve adjacent needs but don't currently overlap on shipped themes. Greenbone Vulnerability Manager is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 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 runc?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Greenbone Vulnerability Manager is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 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 runc?
Top runc alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "runc alternatives" section above for the current picks, or visit /alternatives/runc for the full list with editorial commentary on each.