Read 2026-11-03
artilleryio/artillery: technical due diligence, read from its repository
What Borehole read in artilleryio/artillery's code and history at 664806b: 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 | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE-BSL.txt:1: The licence is BUSL-1.1: source available, not open sourceLICENSE.txt: Relicensed: ISC → MPL-2.0 (2016-02-09)
Architecture & Codebase — including AI provenance
strongpackages/artillery/lib/platform/aws-ecs/legacy/run-cluster.ts is 2,115 lines, 39× this codebase's median file
adequateThe median source file here is 53 lines. 3 files exceed 1,000 lines, the largest being 2,115. 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/artillery/lib/platform/aws-ecs/legacy/run-cluster.ts:1 — 2,115 lines (39× median) |
packages/artillery/lib/core/engine_http.ts:1 — 1,307 lines (24× median) |
packages/artillery/types.d.ts:1 — 1,107 lines (20× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate88 direct dependencies in a single manifest
adequatepackages/artillery/package.json declares 88 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.
packages/artillery/package.json — 88 declared |
packages/artillery-plugin-publish-metrics/package.json — 25 declared |
packages/artillery-engine-playwright/package.json — 4 declared |
packages/artillery-plugin-expect/package.json — 4 declared |
14% of bug fixes add or change a test
adequateOf 108 fixes in the last 24 months, 15 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.
| 15 of 108 |
Security & Reliability Posture
adequate2 Dockerfiles run 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.
packages/artillery/Dockerfile — runs as root |
packages/artillery/lib/platform/aws-ecs/worker/Dockerfile — runs as root |
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. 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/docker-publish-artillery.yml:56 — action pinned by tag |
.github/workflows/examples.yml:73 — action pinned by tag |
9 locked dependencies have published vulnerabilities, 21 high or critical in what ships
adequate9 of 437 locked dependencies match 42 published advisories in OSV, 21 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.
package-lock.json — @azure/msal-node 6.0.1: GHSA-xcx6-jx8p-x3h5 (high), fixed in 7.1.0 |
package-lock.json — @grpc/grpc-js 1.14.4: GHSA-m9gg-hp2v-232j (high), fixed in 1.14.5 |
package-lock.json — axios 1.19.0: GHSA-3pq3-5fj3-cg6v (high), fixed in 1.20.0 |
The licence is BUSL-1.1: source available, not open source
adequateLICENSE-BSL.txt grants BUSL-1.1: source available, not open source; production use restricted until the change date. 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-BSL.txt:1 — 65 lines, BUSL-1.1 |
Relicensed: ISC → MPL-2.0 (2016-02-09)
adequateThe root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
LICENSE.txt — ISC from 2016-01-27 |
LICENSE.txt — MPL-2.0 from 2016-02-09 |
Observability & Operations
not assessableNot rated: only 5 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on artilleryio/artillery: 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.