Read 2026-10-28
nektos/act: technical due diligence, read from its repository
What Borehole read in nektos/act's code and history at 58317c0: 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 |
Architecture & Codebase — including AI provenance
strongpkg/runner/hashfiles/index.js is 5,104 lines, 62× this codebase's median file
adequateThe median source file here is 82 lines. 3 files exceed 1,000 lines, the largest being 5,104. 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/runner/hashfiles/index.js:1 — 5,104 lines (62× median) |
pkg/runner/run_context.go:1 — 1,185 lines (14× median) |
pkg/container/docker_cli.go:1 — 1,163 lines (14× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequateThe 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.
install.sh:41 — download piped into a shell |
3 advisories against this project in the last 24 months, 2 high or critical
adequateThe newest was published on 2026-03-26. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. The record is incomplete: NVD: its keyword search for 'act' is too broad to read whole (22,182 records); NVD: 2 records name act with nothing tying them to this repository (CVE-2006-4832, CVE-2006-4833).
| 2026-03-26: GHSA-jm9r-836x-3vhh (moderate): CI/CD pipeline vulnerabilities in GitHub Actions workflows |
| 2026-03-25: GHSA-x34h-54cw-9825 (high), fixed in 0.2.86: act: actions/cache server allows malicious cache injection |
| 2026-03-25: GHSA-xmgr-9pqc-h5vw (high), fixed in 0.2.86: act: Unrestricted set-env and add-path command processing enables environment injection |
Observability & Operations
adequateOne 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 nektos/act: 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.