pickfit

BrowseDeveloper CLIs

Hurl

Command line tool that runs HTTP requests from plain text files and checks responses.

Use it

Before you install: known vulnerabilities

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

  • npm:extract-zip 2.0.1 extract-zip allows arbitrary file writes through symlink archive entries (GHSA-7pqw-9j4j-h8q3, high, no fix yet)
See 1 more

macOS arm64

You need first

  • Needs the network
  1. brew install hurl

    brew install hurl

Check that it works

hurl --version && which hurl

The output should contain “hurl 8.1.0”.

First thing to try

cat > /tmp/server.py <<'PY'
from http.server import HTTPServer, BaseHTTPRequestHandler
import json, urllib.parse

class H(BaseHTTPRequestHandler):
    def do_GET(self):
        path = self.path.split('?')[0]
        if path in ("/api/health", "/api/step1", "/api/step2", "/api/step3", "/"):
            self.send_response(200)
            self.send_header("Content-Type", "application/json")
            self.end_headers()
            body = json.dumps({"status":"ok", "path": path}).encode()
            self.wfile.write(body)
        elif path == "/api/tests":
            self.send_response(200)
            self.send_header("Content-Type", "application/json")
            self.send_header("X-Frame-Options", "SAMEORIGIN")
            self.end_headers()
            body = json.dumps({"status":"RUNNING","tests": list(range(25)), "id":"4568"}).encode()
            self.wfile.write(body)
        elif path == "/html":
            self.send_response(200)
            self.send_header("Content-Type", "text/html")
            self.end_headers()
            self.wfile.write(b"<html><head><title>Hello world!</title></head><body><p>hi</p><p>there</p></body></html>")
        else:
            self.send_response(404)
            self.end_headers()
            self.wfile.write(b"not found")
    def do_POST(self):
        length = int(self.headers.get('Content-Length', 0))
        body = self.rfile.read(length) if length else b''
        # For /api/tests POST, return same
        path = self.path.split('?')[0]
        if path == "/api/tests":
            self.send_response(200)
            self.send_header("Content-Type", "application/json")
            self.send_header("X-Frame-Options", "SAMEORIGIN")
            self.end_headers()
            resp = json.dumps({"status":"RUNNING","tests": list(range(25)), "id":"4568"}).encode()
            self.wfile.write(resp)
        elif path == "/echo":
            self.send_response(200)
            self.send_header("Content-Type", "application/json")
            self.end_headers()
            self.wfile.write(body or b'{}')
        else:
            self.send_response(200)
            self.send_header("Content-Type", "application/json")
            self.end_headers()
            self.wfile.write(b'{"ok":true}')
    def log_message(self, *a, **k): pass

HTTPServer(("127.0.0.1", 8005), H).serve_forever()
PY
cat > /tmp/chain.hurl <<'HURL'
GET http://127.0.0.1:8005/api/health
HTTP 200
[Captures]
health_status: jsonpath "$.status"
GET http://127.0.0.1:8005/api/step1
HTTP 200
GET http://127.0.0.1:8005/api/step2
HTTP 200
GET http://127.0.0.1:8005/api/step3
HTTP 200
HURL
cat /tmp/chain.hurl

cat > /tmp/asserts.hurl <<'HURL'
POST http://127.0.0.1:8005/api/tests
{
    "id": "4568",
    "evaluate": true
}
HTTP 200
[Asserts]
header "X-Frame-Options" == "SAMEORIGIN"
jsonpath "$.status" == "RUNNING"
jsonpath "$.tests" count == 25
jsonpath "$.id" matches /\d{4}/
HURL
cat /tmp/asserts.hurl

cat > /tmp/report.hurl <<'HURL'
GET http://127.0.0.1:8005/api/health
HTTP 200
[Asserts]
jsonpath "$.status" == "ok"
HURL
cat /tmp/report.hurl
python3 /tmp/server.py
hurl --test /tmp/chain.hurl

What it does

  • Chain HTTP requests in plain text
    Tested
  • Test HTTP responses with asserts
    Tested
  • Integrate tests in CI/CD with reports
    Not tested

How far pickfit got

macOS arm64

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

Good for

  • chain multiple HTTP requests
  • test REST and JSON APIs
  • test performance of HTTP endpoints

An alternative to curl.

How pickfit tested it

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

macOS arm64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 4 Nov 2026
  • Version 8.1.0

Differences the test machine hit

  • README: brew install hurl
    In the test: works as documented (owns /opt/homebrew, no sudo needed)
  • README: hurl --test --report-junit expects usage
    In the test: --report-junit takes a FILE path, not a DIR; creating a file path is required

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.