pickfit

BrowseDeveloper CLIs

Julius

Fingerprints network endpoints to identify which LLM server software is running.

Tested on Linux

Use it

Linux x86_64

  1. download Linux amd64 binary tarball

    curl -fsSL -o /tmp/julius.tar.gz https://github.com/praetorian-inc/julius/releases/download/v1.6.0/julius_1.6.0_linux_amd64.tar.gz
  2. install binary to ~/.local/bin

    mkdir -p ~/.local/bin && tar -xzf /tmp/julius.tar.gz -C /tmp && cp /tmp/julius ~/.local/bin/julius && chmod +x ~/.local/bin/julius
Where the README and reality differ
  • README: --version or --help check (tool supports only --help)
    What worked: use julius --help; julius --version exits 1 with unknown flag
  • README: julius validate ./probes
    What worked: created ./probes dir and downloaded probes/ollama.yaml from GitHub raw before running julius validate ./probes; binary install ships no ./probes directory

Check that it works

julius --help

The output should contain “Julius is a tool for fingerprinting LLM services”.

First thing to try

julius list

Run julius list to see the probe definitions it knows about.

What it does

  • Identify which LLM server runs on an endpoint
    How to use it
    1. Run julius probe <url> against the endpoint.
    2. Read the service name, confidence and any models in the result table.
    Tested
  • List the models an endpoint offers
    How to use it
    1. Run julius probe -o json <url>.
    2. Look at the "models" field in the JSON output.
    Tested
  • List available probe definitions
    How to use it
    1. Run julius list to see all probe definitions and the total count.
    Tested
  • Check probe definition files for errors
    How to use it
    1. Put your probe YAML files in a folder.
    2. Run julius validate <folder> and read the valid and error counts.
    Tested

How far pickfit got

Linux x86_64

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

Good for

  • probe endpoints to identify LLM services
  • extract available models from identified endpoints
  • list available probe definitions

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 31 Oct 2026
  • Version v1.6.0

Differences the test machine hit

  • README: go install github.com/praetorian-inc/julius/cmd/julius@latest
    In the test: downloaded prebuilt julius_1.6.0_linux_amd64.tar.gz from GitHub releases and copied julius binary to ~/.local/bin

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.