pickfit

BrowseDeveloper CLIs

Task

A cross-platform build tool and task runner inspired by Make that runs tasks defined in a Taskfile.

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.

  • npm:basic-ftp 5.3.1 basic-ftp: Quadratic-time CPU denial of service in Client.list() Unix directory-listing parser (RE_LINE backtracking) (GHSA-c475-qrg2-pj4r, high, fixed in 6.2.1)

Linux x86_64

  1. uv tool install go-task-bin (installs task 3.54.0)

    uv tool install go-task-bin

Check that it works

task --version

The output should contain “3.54.0”.

First thing to try

mkdir -p /tmp/proj /tmp/remote && cat > /tmp/proj/Taskfile.yml <<'EOF'
version: '3'

tasks:
  build:
    desc: Build the project
    cmds:
      - echo "Building {{.NAME}}"
    vars:
      NAME: hello-app
  default:
    deps: [build]
    cmds:
      - echo "All done"
EOF
cat > /tmp/remote/Taskfile.yml <<'EOF'
version: '3'

tasks:
  greet:
    cmds:
      - echo "Hello from remote Taskfile"
EOF
mkdir -p /tmp/proj2 && cat > /tmp/proj2/Taskfile.yml <<'EOF'
version: '3'

includes:
  rem: http://127.0.0.1:8765/Taskfile.yml
EOF
cd /tmp/proj && task

In a folder that contains a Taskfile.yml, run task to run the default task.

What it does

  • Run build tasks defined in a Taskfile
    How to use it
    1. Write your tasks in a Taskfile.yml in your project folder.
    2. In that folder, run task to run the default task and its dependencies.
    Tested
  • Include Taskfiles from a remote URL
    How to use it
    1. Add the remote file under includes: in your Taskfile.yml, for example <name>: <url>.
    2. Run TASK_X_REMOTE_TASKFILES=1 task --yes --insecure <name>:<task> to run a task from the remote Taskfile.
    Tested
  • Use shell completions in five shells
    Not shown working

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 2 of 3 features work
  4. Works offline

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

Good for

  • install and run Task in a GitHub Actions workflow
  • include a remote Taskfile over HTTP

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
  • Works offline
  • Checked on 15 Nov 2026
  • Version 3.54.0+pypi

Differences the test machine hit

  • README: pip install go-task-bin
    In the test: uv tool install go-task-bin (isolated install; it prints the version as 3.54.0+pypi)
  • README: Remote Taskfiles (an experiment in older docs)
    In the test: No TASK_X_REMOTE_TASKFILES needed: task warns 'Experiment "REMOTE_TASKFILES" is released'. A plain http:// include needed --insecure, and --yes to skip the trust prompt.

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.