Apache ShenYu
ShenYu's AI gateway plugins are back in motion, with 2.7.2 candidate tags in October.
Comparison · Infra & APIs
Oh Dear vs runc
A side-by-side editorial comparison of Oh Dear and runc — release velocity, themes, recent moves, and the top alternatives to consider.
Oh Dear vs runc: at a glance
What is Oh Dear?
Oh Dear's weekly changelogs have carried a security section five weeks running.
Oh Dear, an uptime and site monitoring service, publishes a changelog each week. Since late September, along with features such as custom webhook headers, 30 to 90 days of status page history and AI fix prompts in Broken Links alerts, it has fixed a high-severity SSRF in uptime checks and AI page fetches, a status page CNAME takeover, a reflected XSS and a status page ID leak, restricted scoped API tokens from team-wide endpoints, and made the MCP consent screen show redirect destinations. The MCP URL now opens a landing page in a browser.
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.
Oh Dear vs runc: editorial side-by-side
Oh Dear
5.0INFRA · APIS
Oh Dear's weekly changelogs have carried a security section five weeks running.
◆ Current state
Oh Dear, an uptime and site monitoring service, publishes a changelog each week. Since late September, along with features such as custom webhook headers, 30 to 90 days of status page history and AI fix prompts in Broken Links alerts, it has fixed a high-severity SSRF in uptime checks and AI page fetches, a status page CNAME takeover, a reflected XSS and a status page ID leak, restricted scoped API tokens from team-wide endpoints, and made the MCP consent screen show redirect destinations. The MCP URL now opens a landing page in a browser.
◆ Where it's heading
August's large MCP release opened the whole product to AI agents, and the autumn work is closing the gaps that kind of exposure creates: SSRF through AI page fetches, consent redirects and token scope. Several fixes credit outside reporters, which suggests responsible disclosure is active. Product work continues alongside in small, practical items for webhooks, status pages and resellers.
◆ Prediction
Expect security fixes to keep appearing in most weekly changelogs while outside reports continue. AI features are spreading into notifications, as the Broken Links fix prompts show, so more AI-written guidance inside alerts is likely.
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 Oh Dear 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 Oh Dear or runc.
TestingBot
TestingBot's autumn work is plumbing: a rebuilt tunnel and another bug-tracker link.
KubeArmor
KubeArmor ships fixes as release-candidate tags, and its feed misses the finals.
All Quiet
All Quiet moves from enterprise integrations to the on-call engineer's own day.
Robusta
Robusta's recent releases patch its runner image rather than add features.
Uptrends
Uptrends spent October on account plumbing: vault credentials, bulk edits and a free trial path.
See all Oh Dear alternatives → · See all runc alternatives →
Recent activity from Oh Dear and runc
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoOh DearWebhook custom headers, uptime header rules, reseller teams page
- 9d agoOh DearAI fix prompts in Broken Links alerts, PHP CVE warnings
- 9d agoOh DearScoped tokens locked out of team-wide endpoints
- 15d agoOh DearHigh-severity SSRF fixed in uptime checks and AI fetches
- 26d agoruncRelease candidate lifts 1024-CPU limit, removes deprecated APIs
- 1mo agoOh DearLonger status page history; MCP consent and CNAME fixes
- 1mo agoruncWorkaround for kernel bug that crashed runc on cgroup v2
- 1mo agoOh DearWebhook deep links; one slow monitor no longer stalls others
- 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 Oh Dear and runc?
They serve adjacent needs but don't currently overlap on shipped themes. Oh Dear 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 Oh Dear better than runc?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Oh Dear 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 Oh Dear?
Top Oh Dear alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Oh Dear alternatives" section above for the current picks, or visit /alternatives/ohdear 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.