Borehole · Project · free tier
reacherhq/check-if-email-exists
Free reading: not for reliance
7882c65 · 1,431 commits · 175 files
Read 2026-11-03

reacherhq/check-if-email-exists: technical due diligence, read from its repository

What Borehole read in reacherhq/check-if-email-exists's code and history at 7882c65: 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 Maturitystrong
Product & Engineering Maturityadequate
Security & Reliability Postureadequate
Observability & Operationsadequate
Fit with the Acquirernot assessable

What the repository says

  • LICENSE: Relicensed: MIT → GPL-3.0 (2019-05-21) → AGPL-3.0 (2020-05-17) → MIT (2026-10-07)

Architecture & Codebase — including AI provenance

strong

No finding.

Engineering Process & SDLC Maturity

strong
02.6

Almost no process scaffolding exists in the repository

adequate

Of five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — 1 is present: CI workflows. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.

Evidence
1 of 5 markers present across 175 tracked files

Product & Engineering Maturity

adequate
04.19

3% of bug fixes add or change a test

adequate

Of 37 fixes in the last 24 months, 1 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.

Evidence
1 of 37

Security & Reliability Posture

adequate
05.2

None of the standard security guard rails are configured

adequate

There is no disclosure policy, no automated dependency updates, no named code owners and no pre-commit configuration. None of these is load-bearing on its own. Their collective absence says that security posture here is whatever the current team happens to remember to do, which is not a posture that survives the team changing.

Evidence
checked 5 kinds of guard rail across 175 tracked files; 0 present
05.6

1 Dockerfile runs the application as root

adequate

No USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.

Evidence
sqs/Dockerfile — runs as root
05.27

The build runs third-party code it does not pin

adequate

7 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/deploy_backend.yml:27 — action pinned by tag
.github/workflows/deploy_cli.yml:23 — action pinned by tag
05.26

22 locked dependencies have published vulnerabilities, 1 high or critical

adequate

22 of 509 locked dependencies match 28 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.

Evidence
Cargo.lock — hickory-resolver 0.24.4: GHSA-5j98-2g5x-46v6 (high), fixed in 0.26.2
Cargo.lock — bytes 1.9.0: GHSA-434x-w66g-qw3r (moderate), fixed in 1.11.1
Cargo.lock — hickory-proto 0.24.4: GHSA-q2qq-hmj6-3wpp (moderate), fixed in 0.26.1
05.60

Relicensed: MIT → GPL-3.0 (2019-05-21) → AGPL-3.0 (2020-05-17) → MIT (2026-10-07)

adequate

The root licence changed 3 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.

Evidence
LICENSE — MIT from 2017-04-25
LICENSE — GPL-3.0 from 2019-05-21
LICENSE — AGPL-3.0 from 2020-05-17
LICENSE.md — MIT from 2026-10-07

Observability & Operations

adequate
06.8

One request cannot be followed through the logs

adequate

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

Evidence
no request id, correlation id or tracing found
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 reacherhq/check-if-email-exists: 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.