Read 2026-10-04
fatedier/frp: technical due diligence, read from its repository
What Borehole read in fatedier/frp's code and history at d20a232: 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 | 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
strongNo finding.
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v0.71.0, is not on the branch this survey read; the newest release on it is v0.62.1. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v0.71.0 |
Security & Reliability Posture
adequateNone of the standard security guard rails are configured
adequateThere 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.
| checked 5 kinds of guard rail across 525 tracked files; 0 present |
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/build-and-push-image.yml:27 — action pinned by tag |
.github/workflows/build-and-push-image.yml:30 — action pinned by tag |
1 locked dependency has published vulnerabilities
adequate1 of 173 locked dependencies match 3 published advisories in OSV. 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.
go.mod — golang.org/x/crypto v0.54.0: GO-2026-6303 (unrated), fixed in 0.55.0 |
2 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-07-23. 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 0.62.1. Answer lives in: the release you run, set against each fixed version. GHSA-26gq-p25f-99cp (high) is fixed in the surveyed commit; which release carries it cannot be told from this history, which does not place the release users run. Answer lives in: the version you run. The record is incomplete: NVD: 1 record names frp with nothing tying it to this repository (CVE-2019-25053).
| 2026-07-23: GHSA-26gq-p25f-99cp (high), fixed in 0.70.1: frp: Unauthenticated Remote Denial of Service in the frp SSH Tunnel Gateway via Integer Overflow |
| 2026-04-13: GHSA-pq96-pwvg-vrr9 (moderate), fixed in 0.68.1: frp has an authentication bypass in HTTP vhost routing when routeByHTTPUser is used for access control |
Observability & Operations
adequateNo 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 497 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 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on fatedier/frp: 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.