Read 2026-10-22
trufflesecurity/trufflehog: technical due diligence, read from its repository
What Borehole read in trufflesecurity/trufflehog's code and history at c85580b: 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 | strong |
| Fit with the Acquirer | not assessable |
What the repository says
README.md:905: The project does not take pull requests
Architecture & Codebase — including AI provenance
strongpkg/pb/sourcespb/sources.pb.validate.go is 7,321 lines, 69× this codebase's median file
adequateThe median source file here is 105 lines. 12 files exceed 1,050 lines, the largest being 7,321. 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.
pkg/pb/sourcespb/sources.pb.validate.go:1 — 7,321 lines (69× median) |
pkg/pb/source_metadatapb/source_metadata.pb.validate.go:1 — 6,091 lines (58× median) |
pkg/sources/github/github.go:1 — 2,778 lines (26× median) |
pkg/engine/defaults/defaults.go:1 — 1,955 lines (18× median) |
pkg/sources/git/git.go:1 — 1,863 lines (17× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate110 direct dependencies in a single manifest
adequatego.mod declares 110 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.
go.mod — 110 declared |
5 files still carry code deprecated more than two years ago
adequate5 files were marked deprecated over two years ago and still are, the oldest since Jan 2022. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
pkg/pb/source_metadatapb/source_metadata.pb.go — deprecated since Jan 2022 |
pkg/pb/credentialspb/credentials.pb.go — deprecated since Jan 2022 |
pkg/pb/detectorspb/detectors.pb.go — deprecated since Jan 2022 |
pkg/pb/sourcespb/sources.pb.go — deprecated since Jan 2022 |
pkg/pb/custom_detectorspb/custom_detectors.pb.go — deprecated since Nov 2022 |
Security & Reliability Posture
adequate151 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. 28 other matchs set aside: expired tokens, licence tokens a vendor verifies with a public key, or placeholder text where a key would go. None grants access to anything.
| 5 cited: AWS access key, where fakes are usual |
1 Dockerfile runs the application as root
adequateNo 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.
Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate2 steps pipe a download straight into a shell. 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.
scripts/install.sh:40 — download piped into a shell |
4 outbound calls can wait forever
adequate4 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.
pkg/common/http.go:260 — outbound call without a timeout |
pkg/common/http.go:268 — outbound call without a timeout |
pkg/detectors/html2pdf/html2pdf.go:59 — outbound call without a timeout |
2 locked dependencies have published vulnerabilities, 1 high or critical
adequate2 of 310 locked dependencies match 3 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.
2 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-10-08. 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 3.99.4. Answer lives in: the release you run, set against each fixed version.
| 2026-10-08: GHSA-fg8w-m62h-jvvw (moderate), fixed in 3.98.0: Workflow command injection via filenames in --github-actions output |
| 2025-10-20: CVE-2025-41390 (high): An arbitrary code execution vulnerability exists in the git functionality of Truffle Security Co. TruffleHog 3.90.2. A specially crafted repository can lead to |
Observability & Operations
strongNo 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 trufflesecurity/trufflehog: 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.