Read 2026-10-23
apache/hertzbeat: technical due diligence, read from its repository
What Borehole read in apache/hertzbeat's code and history at c0b4779: 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
CONTRIBUTING.md:90: states a policy on AI-generated contributionsREADME.md:15: names OpenSSFREADME.md:176: names CNCF.gitmodules:1: 1 submodule(s) this survey does not read: script/helm/hertzbeat-helm-chart
Architecture & Codebase — including AI provenance
stronghertzbeat-alerter/src/main/java/org/apache/hertzbeat/alert/expr/AlertExpressionParser.java is 3,353 lines, 35× this codebase's median file
adequateThe median source file here is 95 lines. 18 files exceed 1,000 lines, the largest being 3,353. 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.
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequateFixes are 56% of recent work, up from 23%
adequateIn the last two quarters 56% of commits were fixes, against 23% in the quarters before. Rising fix work usually means quality debt is coming due, and it takes time that new work would have had.
| 51%, 61%, 29%, 30%, 21%, 14%, 21%, 25% |
2 jobs are each done by more than one library
adequateWithin a single package: UI component kits: antd, mui; dates: date-fns, dayjs. Each duplicate is bundle size, two ways of doing the same thing in one codebase, and two upgrade paths to maintain. It is usually the residue of a migration that stopped halfway.
web-app/package.json — several libraries per job |
Security & Reliability Posture
adequate1 credential-shaped string 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.
| private key block, where fakes are usual |
The build runs third-party code it does not pin
adequate3 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; 1 step pipes 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.
.github/workflows/backend-build-test.yml:93 — action pinned by tag |
.github/workflows/doc-deploy.yml:78 — action pinned by tag |
mcp-servers/mcp-bash-server/Dockerfile:43 — download piped into a shell |
19 SQL statements built from strings
adequate19 places in product code build SQL by formatting or joining strings rather than passing parameters. 3 of them put a value into the string; in the rest, what the code shows going in is a table or column name, a constant, or something the line does not show. Ask whether any value reaches these strings, rather than a parameter.
71 locked dependencies have published vulnerabilities, 43 high or critical in what ships
adequate71 of 2,358 locked dependencies match 176 published advisories in OSV, 89 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.
web-app/pnpm-lock.yaml — dompurify 3.4.14: GHSA-cg2g-xh64-v4q7 (critical), fixed in 3.4.17 |
home/pnpm-lock.yaml — swiper 7.4.1: GHSA-hmx5-qpq5-p643 (critical), fixed in 12.1.2 |
home/pnpm-lock.yaml — proxy-addr 2.0.7: GHSA-jqcg-44mw-7w3h (critical), fixed in 2.0.8; reached only by the build |
7 advisories against this project in the last 24 months, 6 high or critical
adequateThe newest was published on 2026-02-10. 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 7 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 1.9.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 7 records name hertzbeat with nothing tying them to this repository (CVE-2022-39337, CVE-2023-51387, CVE-2023-51388, …).
| 2026-02-10: CVE-2026-24343 (high): Improper Neutralization of Data within XPath Expressions ('XPath Injection') vulnerability in Apache HertzBeat. This issue affects Apache HertzBeat: from 1.7.1 |
| 2025-09-09: CVE-2025-24404 (high): XML Injection RCE by parse http sitemap xml response vulnerability in Apache HertzBeat. The attacker needs to have an authenticated account with acc |
| 2025-09-09: CVE-2025-48208 (high): Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection') vulnerability in Apache HertzBeat . The attacker needs to have |
| 2025-04-16: CVE-2024-56736 (moderate): Server-Side Request Forgery (SSRF) vulnerability in Apache HertzBeat. This issue affects Apache HertzBeat (incubating): before 1.7.0. Users are recommended to |
| 2024-11-18: CVE-2024-41151 (high): Deserialization of Untrusted Data vulnerability in Apache HertzBeat. This vulnerability can only be exploited by authorized attackers. This issue affects Apa |
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 9,706 files for 10 structured logging libraries; 0 matched |
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 |
Sends usage data to telemetry.example.test by default
adequateweb-app/src/features/settings/collector/controller/use-collector-controller-test-support.ts sends to telemetry.example.test, and hertzbeat-manager/src/main/java/org/apache/hertzbeat/manager/controller/TopologyController.java leaves reporting on as shipped. Every installation reports to the vendor unless its operator turns this off. For a buyer running it inside their own product, that is an outbound data flow to a third party: ask what is sent, how often, and whether the buyer's customers were told.
web-app/src/features/settings/collector/controller/use-collector-controller-test-support.ts:161 — reports to telemetry.example.test |
hertzbeat-manager/src/main/java/org/apache/hertzbeat/manager/controller/TopologyController.java:73 — the reporting setting is on by default |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on apache/hertzbeat: 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.