pickfit

BrowseDeveloper CLIs

lenny-ts/caddy-analyzer

Zero-dependency analyzer for Caddy v2 access logs with threat inspection and TUI dashboard

Tested on Linux

Use it

Linux x86_64

  1. Download install script for reading

    curl -sSfL https://raw.githubusercontent.com/lenny-ts/caddy-analyzer/main/install.sh -o /tmp/caddy-install.sh
  2. Download release tarball pinned version

    curl -sSfL https://github.com/lenny-ts/caddy-analyzer/releases/download/v0.8.1/caddy-analyzer_0.8.1_linux_amd64.tar.gz -o /tmp/ca.tgz
  3. Download checksums for verification

    curl -sSfL https://github.com/lenny-ts/caddy-analyzer/releases/download/v0.8.1/checksums.txt -o /tmp/ca-checksums.txt
  4. Verify checksum with correct filename

    cp /tmp/ca.tgz /tmp/caddy-analyzer_0.8.1_linux_amd64.tar.gz && grep caddy-analyzer_0.8.1_linux_amd64.tar.gz$ /tmp/ca-checksums.txt | (cd /tmp && sha256sum -c)
  5. Extract and install binary to local bin

    tar -xzf /tmp/caddy-analyzer_0.8.1_linux_amd64.tar.gz -C /tmp && install -m 0755 /tmp/caddy-analyze ~/.local/bin/caddy-analyze

Check that it works

caddy-analyze --version

The output should contain “caddy-analyze version 0.8.1”.

First thing to try

curl -sSfL https://raw.githubusercontent.com/lenny-ts/caddy-analyzer/main/testdata/sample.log -o sample.log && wc -l sample.log && head -c 2000 sample.log
caddy-analyze --detect sample.log

Run caddy-analyze --detect <logfile> on a Caddy v2 access log to get a security report.

What it does

  • Detect 26 kinds of attacks in requests
    How to use it
    1. Run caddy-analyze --detect <logfile> on your Caddy access log.
    2. Read the SECURITY THREAT INSPECTION REPORT it prints.
    Tested
  • Analyze Caddy v2 access logs
    How to use it
    1. Run caddy-analyze --detect <logfile> for a security report.
    2. Run caddy-analyze top ip <logfile> to list the top remote IPs.
    3. Run caddy-analyze top country <logfile> to list the top countries.
    Tested
  • Block malicious IPs automatically with the firewall
    Not tested
  • Open an interactive terminal dashboard
    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

  • analyze Caddy logs with security detection
  • generate standalone HTML report
  • compare two log files for regressions

An alternative to goaccess, lnav and grep/awk.

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.8.1

Differences the test machine hit

  • README: curl -sSfL .../install.sh | bash installs to /usr/local/bin (uses sudo when not writable)
    In the test: manually replicate script steps: download tarball + checksums, verify sha256, extract caddy-analyze 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.