Borehole · Project · free tier
authorizerdev/authorizer
Free reading: not for reliance
b0f6b62 · 1,649 commits · 1,218 files
Read 2026-11-03

authorizerdev/authorizer: technical due diligence, read from its repository

What Borehole read in authorizerdev/authorizer's code and history at b0f6b62: 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.

DimensionRating
Architecture & Codebase — including AI provenancestrong
Engineering Process & SDLC Maturityadequate
Product & Engineering Maturitystrong
Security & Reliability Postureadequate
Observability & Operationsstrong
Fit with the Acquirernot assessable

What the repository says

  • README.md:57: This repository is a mirror; development happens elsewhere
  • GOVERNANCE.md:100: names CNCF
  • README.md:26: names OpenSSF

Architecture & Codebase — including AI provenance

strong
01.6

internal/http_handlers/oauth_callback.go is 1,735 lines, 17× this codebase's median file

adequate

The median source file here is 102 lines. 4 files exceed 1,020 lines, the largest being 1,735. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.

Evidence
internal/http_handlers/oauth_callback.go:1 — 1,735 lines (17× median)
internal/http_handlers/authorize.go:1 — 1,524 lines (14× median)
internal/http_handlers/token.go:1 — 1,199 lines (11× median)
internal/token/auth_token.go:1 — 1,088 lines (10× median)

Engineering Process & SDLC Maturity

adequate
02.24

5% of recent commits change more than 2,000 lines

adequate

22 of 410 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.

Evidence
22 commits over 2,000 lines

Product & Engineering Maturity

strong

No finding.

Security & Reliability Posture

adequate
05.27

The build runs third-party code it does not pin

adequate

6 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.

Evidence
.github/workflows/buf.yml:44 — action pinned by tag
.github/workflows/govulncheck.yml:33 — action pinned by tag
05.13

6 outbound calls can wait forever

adequate

6 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.

Evidence
internal/http_handlers/oauth_callback.go:814 — outbound call without a timeout
internal/http_handlers/oauth_callback.go:952 — outbound call without a timeout
internal/http_handlers/oauth_callback.go:1032 — outbound call without a timeout
05.20

4 SQL statements built from strings

adequate

4 places in product code build SQL by formatting or joining strings rather than passing parameters. In each, what the code shows going in is a table or column name, a constant, or something the line does not show, not a request's value. Ask whether any value reaches these strings, rather than a parameter.

Evidence
internal/storage/db/cassandradb/session_token.go:336 — SQL built from a string
internal/storage/db/sql/cockroachdb.go:62 — SQL built from a string
internal/storage/db/sql/provider.go:123 — SQL built from a string
05.26

3 locked dependencies have published vulnerabilities, 1 high or critical in what ships

adequate

3 of 313 locked dependencies match 6 published advisories in OSV, 1 of them rated high or critical. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version.

Evidence
go.mod — github.com/go-jose/go-jose/v4 v4.1.4: GHSA-mgcc-cww5-fp2q (high), fixed in 4.1.6
web/app/package-lock.json — react-router 6.30.4: GHSA-337j-9hxr-rhxg (moderate), fixed in 7.18.0
web/app/package-lock.json — react-router-dom 6.30.4: GHSA-jjmj-jmhj-qwj2 (moderate), fixed in 6.30.6
05.65

22 advisories against this project in the last 24 months, 17 high or critical

adequate

The newest was published on 2026-10-14. 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 3 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 2.4.4. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 21 records name authorizer with nothing tying them to this repository (CVE-2024-2435, CVE-2024-49756, CVE-2026-103752, …).

Evidence
2026-10-14: GHSA-m46m-j9p5-5j99 (high), fixed in 2.4.2: Trusted-URL pin (--url) is bypassed on the gRPC and REST gateway transports, allowing host-header-style token poisoning
2026-10-14: GHSA-hhhh-p743-q3cp (low), fixed in 2.4.2: OAuth consent approval (/authorize/consent) accepts a delegated RFC 8693 token with no scope check, letting an openid-only agent grant full-scope third-party ac
2026-10-14: GHSA-44vr-f829-xfch (high), fixed in 2.4.2: Origin-only redirect validation in /verify_email leaks OAuth tokens as query-string params to attacker path
2026-10-14: GHSA-25j3-4jg3-w352 (high), fixed in 2.4.2: Missing Authorization via Public MFA Setup RPCs
2026-10-14: GHSA-qx8r-9p3g-vcp4 (moderate), fixed in 2.4.2: UpdateProfile password-only change does not revoke existing sessions/refresh tokens

Observability & Operations

strong
06.9

No error reporter is wired in

adequate

Nothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.

Evidence
no error reporter initialised

Fit with the Acquirer

not assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on authorizerdev/authorizer: 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.