Skip to content
CAI
Produce a survey ↗Verify a survey

nektos/act

This system is a Go-based GitHub Actions runner that executes CI/CD workflows by managing containerized steps and action execution. It provides a complete execution environment with local artifact caching, Docker-based container management, and support for Node.js and Docker-based actions. The system handles workflow parsing, expression evaluation, and strict schema validation to ensure reliable and secure automation of software delivery pipelines.

67.4

Adequate · 29 July 2026

14k

lines of production code

Go

with JavaScript

3

bus factor · 216 authors in all

3

measurements over time

CAI band scale
CAI trend line

How it got here

2019–2020 · Core runner and CLI architecture

This period focused on establishing the foundational architecture for the GitHub Actions runner, introducing a modular CLI structure and a Go-based execution engine for processing workflows and actions. The work included implementing container execution via Docker, adding common utilities for authentication and context management, and establishing a robust test suite with various action fixtures.

10 changes

2021–2023 · runner and expression engine enhancements

This period focused on expanding the GitHub Actions compatibility layer, introducing a new expression parser with built-in functions and a local artifact cache for improved performance. The runner was updated to support Node.js 16 and 20 runtimes, while also implementing pre/post step execution and Git metadata utilities.

10 changes

2024–2025 · pkg/filecollector and schema validation

This period focused on modularizing file collection logic into a new package and enforcing strict schema validation for GitHub Actions workflows. The team also expanded test coverage for composite actions, post-step failures, and Docker environment variable handling.

6 changes

CAI lens gauges

Survey your own repository

nektos/act was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.

Survey a repository

About this page

  • The description of this project is derived from its own commit history, not from its README.
  • The score is its highest published measurement, taken on 29 July 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
  • Measured at commit 4f41128141 — the exact code this score is about.
  • Scored under rubric rubric-2026.08.18. Score the same commit under that rubric and you get the same number.
CAI link cards