Read 2026-11-03
inkeep/agents: technical due diligence, read from its repository
What Borehole read in inkeep/agents's code and history at d6d91ed: 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 | adequate |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
What the repository says
AGENTS.md:157: This repository is a mirror; development happens elsewhereLICENSE.md:1: The licence is Elastic-2.0: source available, not open source
Architecture & Codebase — including AI provenance
strongpackages/agents-core/src/validation/schemas.ts is 4,110 lines, 47× this codebase's median file
adequateThe median source file here is 86 lines. 33 files exceed 1,000 lines, the largest being 4,110. 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.
packages/agents-core/src/validation/schemas.ts:1 — 4,110 lines (47× median) |
agents-manage-ui/src/lib/api/signoz-stats.ts:1 — 3,563 lines (41× median) |
agents-api/src/domains/run/session/AgentSession.ts:1 — 2,197 lines (25× median) |
packages/agents-core/src/data-access/manage/agentFull.ts:1 — 2,178 lines (25× median) |
agents-api/src/domains/manage/routes/scheduledTriggers.ts:1 — 1,952 lines (22× median) |
Engineering Process & SDLC Maturity
adequateTests are retried until they pass
adequateThe suite is configured to retry failing tests (agents-cli/src/commands/pull-v4/__tests__/credential-generator.test.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.
agents-cli/src/commands/pull-v4/__tests__/credential-generator.test.ts:146 — test retry |
6% of recent commits change more than 2,000 lines
adequate142 of 2319 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.
| 142 commits over 2,000 lines |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate20 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 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: Slack token, where fakes are usual |
The build runs third-party code it does not pin
adequate1 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.
.ai-dev/Dockerfile:35 — download piped into a shell |
39 SQL statements built from strings
adequate39 places in product code build SQL by formatting or joining strings rather than passing parameters, and in 35 of them a value, not a table or column name, goes into the string. Where any of those values comes from a request, it is an injection point. Each site needs a look; the fix, parameters, is small.
packages/agents-core/src/data-access/manage/projectLifecycle.ts:254 — SQL built from a string |
packages/agents-core/src/db/manage/dolt-cleanup.ts:31 — SQL built from a string |
packages/agents-core/src/db/manage/dolt-cleanup.ts:61 — SQL built from a string |
75 locked dependencies have published vulnerabilities, 69 high or critical in what ships
adequate75 of 3,795 locked dependencies match 185 published advisories in OSV, 80 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.
create-agents-template/pnpm-lock.yaml — next 16.3.8: GHSA-2464-fhr4-w9xw (critical), fixed in 16.4.1 |
create-agents-template/pnpm-lock.yaml — piscina 4.9.2: GHSA-67c8-pqhq-4rmx (critical), fixed in 4.9.4 |
create-agents-template/pnpm-lock.yaml — tinypool 1.1.1: GHSA-5gmw-xhrv-c9v3 (critical), fixed in 2.1.1 |
The licence is Elastic-2.0: source available, not open source
adequateLICENSE.md grants Elastic-2.0: source available, not open source; offering it as a managed service is not allowed. The reading comes from the licence's own title and clauses. Whether the terms fit the buyer's intended use, and whether any paid licence transfers with the code, is a question for counsel and the licensor.
LICENSE.md:1 — 49 lines, Elastic-2.0 |
1 advisory against this project in the last 24 months
adequateThe newest was published on 2026-05-11. 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.68.4. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 272 records name agents with nothing tying them to this repository (CVE-1999-1355, CVE-2001-0134, CVE-2001-0728, …).
| 2026-05-11: CVE-2026-8321 (moderate): A vulnerability was detected in inkeep agents 0.58.14. This vulnerability affects the function createDevContext of the file agents-api/src/middleware/runAuth.ts |
Observability & Operations
strong2 of 11 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.
docker-compose.isolated.yml:17 — image without a version |
docker-compose.isolated.yml:75 — 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 inkeep/agents: 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.