pickfit

BrowseDeveloper CLIs

wshm

Self-hosted repo agent that triages issues, analyzes PRs and manages merge queues.

Use it

Before you install: known vulnerabilities

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

  • npm:dompurify 3.4.15 DOMPurify SAFE_FOR_TEMPLATES bypass: split template expressions survive in attached shadow root content on DOM output modes (GHSA-cg2g-xh64-v4q7, critical, fixed in 3.4.17)
  • crates:openssl 0.10.78 rust-openssl has undefined behavior in X509Ref::ocsp_responders for certificates with non-UTF-8 OCSP URLs (GHSA-xp3w-r5p5-63rr, high, fixed in 0.10.79)
See 3 more

Linux x86_64

You need first

  • Keys or accounts: GITHUB_TOKEN, ANTHROPIC_API_KEY
  1. Download install script

    curl -fsSL https://raw.githubusercontent.com/wshm-dev/wshm/main/install.sh -o /tmp/install-wshm.sh
  2. Install wshm via script

    sh /tmp/install-wshm.sh

Check that it works

wshm --version

The output should contain “wshm 0.32.0”.

First thing to try

mkdir -p /tmp/wshm-demo && cd /tmp/wshm-demo && wshm config init

Go to your repository folder and run wshm config init to create a configuration.

What it does

  • Classify and label open issues
    Not tested
  • Analyze and label open pull requests
    Not tested
  • Show a ranked merge queue
    Not tested
  • Generate pull requests from issue descriptions
    Not tested

How far pickfit got

Linux x86_64

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

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

Good for

  • classify and label open issues
  • analyze and label open pull requests
  • show ranked merge queue
  • backup local database
  • send priority summary notifications

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 0.32.0

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.