Read 2026-10-23
doorkeeper-gem/doorkeeper: technical due diligence, read from its repository
What Borehole read in doorkeeper-gem/doorkeeper's code and history at c3df01d: its licence, security advisories, releases, review practice, tests, dependencies and operations. Every finding cites the file and line it rests on. The full report also covers the team and asks the questions the code cannot answer.
| Dimension | Rating |
|---|---|
| Architecture & Codebase — including AI provenance | strong |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | strong |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
Architecture & Codebase — including AI provenance
strongNo finding.
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v5.9.9, is not on the branch this survey read; the newest release on it is v5.9.3. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v5.9.9 |
Security & Reliability Posture
strongThe build runs third-party code it does not pin
adequate4 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
.github/workflows/changelog.yml:21 — action pinned by tag |
.github/workflows/changelog.yml:36 — action pinned by tag |
5 advisories against this project in the last 24 months
adequateThe newest was published on 2026-10-21. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 4 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 5.9.3. Answer lives in: the release you run, set against each fixed version.
| 2026-10-21: GHSA-c62j-746x-gfcr (moderate), fixed in 5.9.7: Access token authentication silently accepts multiple simultaneous transmission methods (RFC 6750 §2) |
| 2026-10-21: GHSA-c8r6-23w7-5q9p (low), fixed in 5.9.6: Client authentication silently accepts multiple simultaneous methods (RFC 6749 §2.3) |
| 2026-08-25: CVE-2026-44476 (moderate): Doorkeeper is an OAuth 2 provider for Ruby on Rails. In version 1.9.0, an attacker who knows only a dynamically registered client's client_id, which is public i |
| 2026-08-25: CVE-2026-70665 (moderate): Doorkeeper OpenID Connect implements an OpenID Connect authentication provider for Rails applications on top of Doorkeeper. Prior to 1.10.4, the Dynamic Client |
| 2026-07-30: GHSA-h5m9-42h9-vcq6 (moderate), fixed in 5.9.1: Improper authorization on token revocation endpoint |
Observability & Operations
not assessableNot rated: only 5 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on doorkeeper-gem/doorkeeper: every dimension, the questions for the room, and the audit log.
Survey a repository: free on public repositories. Private code is read on your own machine by a collector whose source you can read first.