Read 2026-10-28
nextauthjs/next-auth: technical due diligence, read from its repository
What Borehole read in nextauthjs/next-auth's code and history at a1a16a5: 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 | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| 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
strongTests are retried until they pass
adequateThe suite is configured to retry failing tests (packages/next-auth/playwright.config.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
packages/next-auth/playwright.config.ts:26 — test retry |
Product & Engineering Maturity
adequate9% of bug fixes add or change a test
adequateOf 154 fixes in the last 24 months, 14 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| 14 of 154 |
6 files still carry code deprecated more than two years ago
adequate6 files were marked deprecated over two years ago and still are, the oldest since Jan 2024. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
packages/core/src/providers/email.ts — deprecated since Jan 2024 |
packages/frameworks-sveltekit/src/lib/types.ts — deprecated since Feb 2024 |
packages/core/src/providers/azure-ad.ts — deprecated since Apr 2024 |
packages/core/src/providers/azure-devops.ts — deprecated since Apr 2024 |
packages/core/src/providers/oauth.ts — deprecated since Apr 2024 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, next-auth@4.24.15, is not on the branch this survey read; the newest release on it is next-auth@4.22.1. The shipped product may differ from what this report describes. Survey the release branch too.
| tag next-auth@4.24.15 |
Security & Reliability Posture
adequate4 credential-shaped strings in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| 4 cited: JWT, where fakes are usual |
The build runs third-party code it does not pin
adequate6 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/broken-link-checker.yml:19 — action pinned by tag |
.github/workflows/release.yml:70 — action pinned by tag |
64 locked dependencies have published vulnerabilities, 12 high or critical in what ships
adequate64 of 3,102 locked dependencies match 141 published advisories in OSV, 64 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.
pnpm-lock.yaml — next 15.5.18: GHSA-2464-fhr4-w9xw (critical), fixed in 15.5.28 |
pnpm-lock.yaml — better-auth 1.6.16: GHSA-965c-763c-88jm (critical), fixed in 1.7.7; a development dependency |
pnpm-lock.yaml — tar 6.2.1: GHSA-23hp-3jrh-7fpw (critical), fixed in 7.5.19; a development dependency |
7 places insert HTML from a variable without sanitising it
adequate7 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.
packages/core/src/lib/pages/error.tsx:88 — HTML from a variable |
packages/core/src/lib/pages/signin.tsx:32 — HTML from a variable |
packages/core/src/lib/pages/signin.tsx:80 — HTML from a variable |
5 advisories against this project in the last 24 months, 2 high or critical
adequateThe newest was published on 2026-07-20. 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 1 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 4.22.1. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 1 record names next-auth with nothing tying it to this repository (CVE-2026-62862).
| 2026-07-20: GHSA-7rqj-j65f-68wh (critical), fixed in 0.41.3: Auth.js: Email normalizer validates the address before Unicode normalization, allowing a homoglyph @ bypass |
| 2026-07-20: GHSA-x445-f3h2-j279 (moderate), fixed in 0.41.3: Auth.js: OAuth state, nonce, and PKCE check cookies are not bound to the provider that created them |
| 2026-07-20: GHSA-xmf8-cvqr-rfgj (high), fixed in 0.41.3: Auth.js: getToken() throws an uncaught exception on malformed Bearer authorization headers |
| 2026-07-20: GHSA-8fpg-xm3f-6cx3 (low), fixed in 5.0.0-beta.32: Configuration errors can cause existence-based auth checks to fail open (auth object populated with an error) |
| 2025-10-27: GHSA-5jpx-9hw9-2fx4 (moderate), fixed in 4.24.12: NextAuthjs Email misdelivery Vulnerability |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 878 readable files references an instrumentation, metrics or error-reporting library. If this system is in production, nobody learns that it broke from the system itself — they learn it from a customer. That is a reliability finding before it is an observability one.
| searched 878 tracked text files for 16 known instrumentation libraries; manifests for metrics, tracing and error-reporting families; locked dependencies for the packages that emit; 0 matched |
No structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| searched 878 files for 10 structured logging libraries; 0 matched |
One request cannot be followed through the logs
adequateNothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.
| no request id, correlation id or tracing found |
No error reporter is wired in
adequateNothing 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.
| no error reporter initialised |
2 of 4 deployed images carry no version, or `latest`
adequate2 images in the deployment configuration are named without a version or as `latest`. A redeploy can change the software without a commit, a rollback has nothing to roll back to, and nobody can say from the repository what is running.
packages/adapter-upstash-redis/docker-compose.yml:3 — image without a version |
packages/adapter-upstash-redis/docker-compose.yml:9 — image without a version |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on nextauthjs/next-auth: 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.