authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
Comparison · Infra & APIs
Mergify vs mod_auth_openidc
A side-by-side editorial comparison of Mergify and mod_auth_openidc — release velocity, themes, recent moves, and the top alternatives to consider.
Mergify vs mod_auth_openidc: at a glance
What is Mergify?
Mergify's queue learned to merge stacked pull requests, then spent August tightening the edges.
Mergify automates merge queues for GitHub, and August was a mix of one real capability and a batch of contract cleanup. The queue can now merge GitHub-native stacked pull requests in order, speculative-check budgets apply per lane across dynamic scope sets, and conditions can match on whether a pull request came from a fork. Alongside that, the badge API was removed, pagination stopped advertising first and last links, and author-run commands were restricted to fork pull requests by default.
What is mod_auth_openidc?
mod_auth_openidc keeps hardening its own attack surface, one audited subsystem at a time
This is the Apache module implementing OpenID Connect relying-party support, and its 2.4.20.x line has been an almost unbroken security programme. An internal audit turned up eight issues including an identity-header bypass; PBKDF2 key stretching changed the session encryption key and invalidated every session created by 2.4.19.x and earlier; out-of-bounds reads and writes were fixed in the state-cookie parser. The latest release continues in the same register, hardening file-backed metadata and cache I/O and the shared-memory cache itself.
Mergify vs mod_auth_openidc: editorial side-by-side
Mergify
6.3INFRA · APIS
Mergify's queue learned to merge stacked pull requests, then spent August tightening the edges.
◆ Current state
Mergify automates merge queues for GitHub, and August was a mix of one real capability and a batch of contract cleanup. The queue can now merge GitHub-native stacked pull requests in order, speculative-check budgets apply per lane across dynamic scope sets, and conditions can match on whether a pull request came from a fork. Alongside that, the badge API was removed, pagination stopped advertising first and last links, and author-run commands were restricted to fork pull requests by default.
◆ Where it's heading
Two threads. The queue is absorbing workflows that used to sit outside it - stacked pull requests, flaky-test detection and rerunning within a CI budget - which pushes Mergify from a merge gate toward owning the whole pre-merge pipeline. The other thread is a deliberate narrowing of surface: deprecated endpoints removed, the github_actions action marked for removal in March 2027, default command permissions tightened around forks. That is a product trimming what it maintains so the queue can take on more.
◆ Prediction
Expect more of the pre-merge pipeline to move inside the queue on the flaky-test pattern, and further deprecations of automation that overlaps with what GitHub Actions now does natively.
mod_auth_openidc
6.3INFRA · APIS
mod_auth_openidc keeps hardening its own attack surface, one audited subsystem at a time
◆ Current state
This is the Apache module implementing OpenID Connect relying-party support, and its 2.4.20.x line has been an almost unbroken security programme. An internal audit turned up eight issues including an identity-header bypass; PBKDF2 key stretching changed the session encryption key and invalidated every session created by 2.4.19.x and earlier; out-of-bounds reads and writes were fixed in the state-cookie parser. The latest release continues in the same register, hardening file-backed metadata and cache I/O and the shared-memory cache itself.
◆ Where it's heading
The project is working outward from the code paths an attacker actually reaches: cookie parsing, then session key derivation, then cache storage and the files the module reads at runtime. Keyed hashing of cache keys to stop bucket-chain flooding, refusing non-regular files, capping allocations and writing metadata atomically all address resource-exhaustion and file-substitution classes rather than single bugs. Packaging and commercial distribution notes take up an increasing share of each release body, with Redis and Valkey over TLS behind a commercial agreement.
◆ Prediction
With the cache and file layers now hardened, the remaining large surface is the HTTP client and provider metadata handling, so that is the likeliest next area — and the 2.4.20.x line should settle into ordinary maintenance once the audit backlog is worked through.
Alternatives to Mergify and mod_auth_openidc
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 Mergify or mod_auth_openidc.
incident.io
Alert rate limits stop being per-source and start being per-tenant, by query.
Warp
The essay series keeps running ahead of the products it describes.
Node-RED
Both lines patch on the same day, and the reverted JSONata upgrade finally sticks.
werf
The 3.x line finally ships function: authenticated secret writes and render patches.
Infisical
Folder-level RBAC lands, and approvals finally get a webhook to talk to.
See all Mergify alternatives → · See all mod_auth_openidc alternatives →
Recent activity from Mergify and mod_auth_openidc
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agomod_auth_openidcFile and shared-memory cache hardened against flooding and substitution
- 1d agomod_auth_openidcUntagged GitHub artifact duplicating the 2.4.20.3 release
- 8d agoMergifyPer-lane check capacity for dynamic scopes
- 8d agoMergifyPagination drops the first and last links
- 8d agoMergifyRepository badge API removed
- 8d agoMergifyClearer reason when the merge queue can't create the draft pull request
- 21d agoMergifyMerge GitHub stacked pull requests with the merge queue ⚡
- 22d agoMergifyNew from-fork condition attribute
- 23d agomod_auth_openidcOIDCDebugMaskSecrets reopens debug logs, cache tier removed
- 24d agomod_auth_openidcInternal audit turns up eight security issues, including an identity-header bypass ⚡
- 1mo agomod_auth_openidcPBKDF2 key stretching invalidates all existing sessions
- 2mo agomod_auth_openidcOut-of-bounds read and write fixed in the state-cookie parser
Frequently asked questions
What is the difference between Mergify and mod_auth_openidc?
They serve adjacent needs but don't currently overlap on shipped themes. Mergify and mod_auth_openidc are shipping at a similar cadence (velocity 6.3 vs 6.3, 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 Mergify better than mod_auth_openidc?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Mergify and mod_auth_openidc are shipping at a similar cadence (velocity 6.3 vs 6.3, 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 Mergify?
Top Mergify alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Mergify alternatives" section above for the current picks, or visit /alternatives/mergify for the full list with editorial commentary on each.
What are the best alternatives to mod_auth_openidc?
Top mod_auth_openidc alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "mod_auth_openidc alternatives" section above for the current picks, or visit /alternatives/mod-auth-openidc for the full list with editorial commentary on each.