pickfit

BrowseInfra & DevOps tools

act

Command-line tool that runs GitHub Actions workflows locally in Docker containers.

Use it

Before you install: known vulnerabilities

pickfit found 1 known high or critical vulnerability in the packages a fresh install brings (OSV.dev, 16 Nov 2026). Weigh this before you install it.

  • go:github.com/klauspost/compress v1.18.7 Panic on two-block frames in github.com/klauspost/compress (GO-2026-6865, high, fixed in 1.20.2)

Linux x86_64

You need first

  • Runtimes: go (to build from source)
  • System packages: docker
  1. Download the act_Linux_x86_64 release tarball and install the act binary into ~/.local/bin

    mkdir -p ~/.local/bin /tmp/act && curl -fsSL -o /tmp/act/act.tar.gz https://github.com/nektos/act/releases/latest/download/act_Linux_x86_64.tar.gz && tar -xzf /tmp/act/act.tar.gz -C /tmp/act && install -m755 /tmp/act/act ~/.local/bin/act
Where the README and reality differ
  • README: (not mentioned)
    What worked: On the first run without -P or ~/.config/act/actrc, act asks you to choose a default image and waits for input (it hung in non-interactive mode). Pass -P to skip the prompt

Check that it works

act --version

The output should contain “act version”.

First thing to try

mkdir -p /tmp/demo/.github/workflows && cd /tmp/demo && git init -q && cat > .github/workflows/ci.yml <<'EOF'
name: CI
on: push
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - run: echo "hello from act $GITHUB_WORKSPACE"
  test:
    runs-on: ubuntu-latest
    needs: build
    steps:
      - run: echo testing
EOF
cd /tmp/demo && act push -P ubuntu-latest=-self-hosted

Go to a Git repository that has workflow files in .github/workflows and run act push -P ubuntu-latest=-self-hosted.

What it does

  • Run GitHub Actions workflows on your own machine
    How to use it
    1. Go to a Git repository with a workflow file in .github/workflows.
    2. Run act push -P ubuntu-latest=-self-hosted to run the workflows triggered by a push.
    3. Check the output for a "Job succeeded" line for each job.
    Tested
  • Use workflow jobs in place of a Makefile
    How to use it
    1. Define the tasks you want as jobs in a workflow file in .github/workflows.
    2. Run a single job with act -j <job> -P ubuntu-latest=-self-hosted.
    Tested
  • Use the same environment variables and files as GitHub
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 2 of 3 features work
  4. Needs the network

macOS and Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • test changes to GitHub workflow files without pushing
  • use GitHub Actions workflows as a local task runner instead of a Makefile

An alternative to make.

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its main function works

  • Replayed from scratch
  • Needed the network
  • Checked on 15 Nov 2026
  • Version 0.2.97

Differences the test machine hit

  • README: Install Go, git clone git@github.com:nektos/act.git, make install
    In the test: Prebuilt release binary from https://github.com/nektos/act/releases/latest/download/act_Linux_x86_64.tar.gz (no Go needed). The SSH clone URL also needs a GitHub SSH key; HTTPS would be needed for anonymous cloning
  • README: act uses the Docker API to run containers for each action
    In the test: No Docker in this box: container runs fail with 'failed to connect to the docker API'. Running with -P ubuntu-latest=-self-hosted runs the jobs on the host instead

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.