pickfit

BrowseDeveloper CLIs

InferCrane

Evidence-gated system to deploy and manage vLLM/SGLang inference behind one OpenAI-compatible endpoint.

Use it

Before you install: known vulnerabilities

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

  • go:github.com/go-jose/go-jose/v3 v3.0.5 Go JOSE: DoS when parsing JWKs that contain RSA keys (GHSA-mgcc-cww5-fp2q, high, no fix yet)
  • npm:undici 7.29.1 undici vulnerable to TLS certificate validation bypass via dropped tls options in Agent (GHSA-2m5v-pch6-74hx, high, fixed in 7.30.1)
See 4 more

Linux x86_64

  1. download and inspect CLI archive

    curl -sL -o /tmp/infercrane.tar.gz 'https://github.com/infercrane/infercrane/releases/download/v1.0.0-rc.1/infercrane_1.0.0-rc.1_linux_amd64.tar.gz' && mkdir -p ~/.local/bin && tar -xzf /tmp/infercrane.tar.gz -C /tmp/
  2. install CLI binary and check version

    cp /tmp/infercrane ~/.local/bin/infercrane && chmod +x ~/.local/bin/infercrane && infercrane --help
Where the README and reality differ
  • README: npm install '@infercrane/sdk@1.0.0-rc.1' and pip install infercrane wheel install the CLI
    What worked: Linux CLI binary from release archive infercrane_1.0.0-rc.1_linux_amd64.tar.gz extracted and copied to ~/.local/bin/infercrane

Check that it works

infercrane --version

The output should contain “infercrane version 1.0.0-rc.1”.

First thing to try

infercrane workload init ./support --recipe qwen3-8b

Run infercrane --help to see the available commands, or start a workload with infercrane workload init <directory> --recipe <recipe>.

What it does

  • Optimize existing inference workloads
    Not tested
  • Adopt existing inference endpoints
    Not tested

How far pickfit got

Linux x86_64

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

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

Good for

  • deploy open-weight models into your cloud or Kubernetes
  • optimize workload performance and cost on exact hardware
  • run agent tasks in persistent sandbox
  • trace production inference failures and latency

An alternative to Raw vLLM and Kubernetes.

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 30 Oct 2026
  • Version 1.0.0-rc.1

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.