pickfit

BrowseDeveloper CLIs

Penthera

Offline rule-based agent that scans apps, dependencies and AI tools for security issues.

Tested on Linux

Use it

Linux x86_64

  1. Install penthera globally via npm

    npm install -g penthera

Check that it works

penthera --version

The output should contain “penthera v2.1.0”.

First thing to try

penthera giants

Run penthera --repo <folder> --offline to scan a project folder.

What it does

  • Scan app URLs and code repositories
    How to use it
    1. Run penthera --repo <folder> --offline to scan a repository.
    2. Review the findings, which are listed by severity (such as HIGH) with the file they were found in.
    Tested
  • Check dependencies for risky capabilities
    How to use it
    1. Run penthera deps <project-folder> in a project that has its dependencies installed.
    2. Review each flagged package, such as one that runs a risky install script.
    Tested
  • Audit AI tool configurations
    How to use it
    1. Run penthera agents <project-folder> on a project with AI tool settings such as .mcp.json.
    2. Review the findings, such as MCP servers with secrets written inline.
    Tested
  • Apply fixes and scan again
    Not shown working

How far pickfit got

Linux x86_64

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

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

Good for

  • scan a localhost or preview URL for misconfigurations
  • vet npm and Python package capabilities
  • audit AI coding tool configuration
  • block secrets at commit time

An alternative to Socket, Snyk, OWASP ZAP, Semgrep and GitHub Dependabot and code scanning.

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 penthera v2.1.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.