pickfit

BrowseLocal AI tools

Frink

Pure-Rust engine that loads GGUF checkpoints and runs quantized dense and MoE inference.

Use it

Before you install: known vulnerabilities

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

  • npm:zod 4.4.3 Zod can exhaust memory while validating oversized constrained collections (GHSA-mrhx-c7xc-m3w5, high, fixed in 4.6.6)

Linux x86_64

  1. Download install script for reading

    curl -fsSL https://raw.githubusercontent.com/antonellof/frink/main/scripts/install.sh -o /tmp/frink-install.sh
  2. Install frink via release script

    bash /tmp/frink-install.sh

Check that it works

frink --version

The output should contain “0.50.0”.

First thing to try

mkdir -p ~/models && curl -fL -o ~/models/stories260K.gguf https://huggingface.co/ggml-org/test-model-stories260K/resolve/main/stories260K-f32.gguf && ls -l ~/models/stories260K.gguf
FRINK_EXPERT_CACHE_BYTES=536870912 frink serve -m ~/models/stories260K.gguf
curl -s http://127.0.0.1:8383/v1/models

Start the server with a GGUF model file using frink serve -m <model.gguf>, then send requests to http://127.0.0.1:8383.

What it does

  • Serve an OpenAI-compatible API
    How to use it
    1. Start the server with frink serve -m <model.gguf>.
    2. List the loaded model with curl -s http://127.0.0.1:8383/v1/models.
    3. Request a chat completion with `curl -s -X POST http://127.0.0.1:8383/v1/chat/completions -H 'content-type: application/json' -d '{"model":"llama","messages":[{"role":"user","content":"<your text>"}],
    Tested
  • Serve embeddings and reranking
    How to use it
    1. Start the server with frink serve -m <model.gguf>.
    2. Get an embedding with curl -s -X POST http://127.0.0.1:8383/v1/embeddings -H 'content-type: application/json' -d '{"model":"llama","input":"<your text>"}'.
    Tested
  • Run inference on GGUF checkpoints
    Not tested
  • Run Mixture-of-Experts models
    Not tested

How far pickfit got

Linux x86_64

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

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

Good for

  • serve a GGUF model via OpenAI-compatible API
  • run a GGUF checkpoint for text completion
  • benchmark inference against llama.cpp on same host

An alternative to llama.cpp.

How pickfit tested it

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

Linux x86_64

It produces model output

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 0.50.0

Differences the test machine hit

  • README: curl -fsSL .../install.sh | bash
    In the test: download to /tmp/frink-install.sh, read it, then run bash /tmp/frink-install.sh
  • README: frink -m <model> -p ... -n ... runs directly
    In the test: run with FRINK_EXPERT_CACHE_BYTES=536870912 on this 2GiB box
  • README: frink -m ... -dev metal -ngl all
    In the test: omit -dev metal -ngl all on Linux CPU; run without device flags

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.