pickfit

BrowseDeveloper CLIs

oweka

Fast TUI that finds and deletes unwanted artifact directories like node_modules.

Tested on Linux

Use it

Linux x86_64

  1. install oweka via npm global

    npm install -g oweka@0.1.3

Check that it works

which oweka

The output should contain “/.local/bin/oweka”.

First thing to try

which oweka

Run oweka in the directory you want to scan.

What it does

  • Scan for unwanted artifact directories
    Not tested
  • Delete the highlighted artifact folders
    Not tested
  • Open the highlighted folder in your file manager
    Not tested

How far pickfit got

Linux x86_64

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

Good for

  • scan current directory for artifact folders
  • scan a specified directory for artifact folders
  • delete selected artifact directory

An alternative to NPKILL.

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 1 Nov 2026
  • Version 0.1.3

Differences the test machine hit

  • README: npx oweka runs TUI scanning current dir
    In the test: binary downloaded lazily on first run (binary.js suppressLogs) - first invocation triggers download
  • README: expected --help/--version flags
    In the test: oweka has no flags; --help is treated as path and returns '--help does not exist or is not a directory' exit 1
  • README: oweka runs interactively
    In the test: without PTY it errors 'terminal error: No such device or address (os error 6)'; need script(1) pty to capture TUI alternate-screen escape [?1049h

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.