DEV Community: Prince

BLITZ: Kill Processes 10x Faster Than lsof + A Speed Comparison with ps/grep/htop

Prince — Sat, 22 Aug 2026 11:50:36 +0000

I got frustrated with killing processes. Every time I needed to find what's using port 8080, I'd chain together lsof + grep + awk. Every time I wanted to kill something, I'd confirm it manually. Every time I monitored a process, I'd context-switch to htop.

So I built BLITZ. A process manager that actually works the way devs think.

The Speed Problem

Let me show you the actual time difference:

Finding what's on port 8080:

Old way:
$ time lsof -i :8080 | grep LISTEN | awk '{print $2}' | xargs kill -9
real 0m0.847s

BLITZ:
$ time bz port 8080
real 0m0.089s

That's 9.5x faster.

But speed isn't the point. It's clarity. Here's what you get:

$ bz port 8080
Found: node (PID 1234)
Kill? [y/N]:

vs.

$ lsof -i :8080
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
node 1234 prince 45u IPv4 0x123abcd 0t0 TCP localhost:8080 (LISTEN)

One is a question. One is a puzzle.

Speed Comparison: All Methods

Task	BLITZ	ps + grep	lsof	htop
Find process on port 8080	0.089s	1.2s	0.847s	N/A
Kill process safely	1 command	Multiple	Multiple	N/A
List all processes	0.034s	0.041s	N/A	N/A
Top 10 by memory	0.045s	2.3s	N/A	0.8s
Real-time monitor	Built-in	N/A	N/A	Yes

(Tested on 500+ process systems, average of 10 runs)

Why BLITZ exists

The Unix philosophy is "do one thing well." But killing processes isn't one thing. It's:

Finding the process (grep, awk, or lsof syntax)
Confirming you got the right one (human check)
Deciding how to kill it (kill vs kill -9)
Executing without destroying critical processes

BLITZ combines all four into one intuitive command.

How to use it

bz # Show all processes (beautiful, colored)
bz top # Top 10 by memory
bz port 8080 # Find what's on that port
bz kill chrome # Kill by name (asks first)
bz kill chrome -f # Force kill without asking
bz watch java # Real-time monitoring
bz stats # CPU/RAM/disk

Install

git clone https://github.com/hunzo1/blitz.git
cd blitz
pip install -e .
bz # works from anywhere

Works on Linux, macOS, and Termux. Open source. No dependencies except psutil.

The Benchmark Details

If you want to reproduce these numbers:

Speed test: find process on random port

for i in {1..10}; do time bz port $((RANDOM + 2000)); done

Comparison with lsof chain

for i in {1..10}; do time (lsof -i :$((RANDOM + 2000)) | grep LISTEN); done

BLITZ wins on clarity, speed, and UX. The code is 320 lines of Python. Fully open source.

What's next

I'm open to feedback. If you use process management daily (and most developers do), try it out. Let me know what breaks.

Source: https://github.com/hunzo1/Blitz

I built a CVE scanner for Python/Node with zero dependencies. Here's why that matters.

Prince — Wed, 01 Jul 2026 10:21:41 +0000

Most dependency scanners are themselves a dependency problem.
You install safety or pip-audit and suddenly you're pulling in 12 packages just to check if your 3 packages are safe. That always bothered me.
So I built Depheal. It scans your requirements.txt and package.json for known CVEs and abandoned packages — and it has zero dependencies. Pure Python stdlib. Nothing else.

pip install depheal
depwise scan .

What it actually does
Hits the OSV.dev API for real CVE data
Detects abandoned packages (no updates in 3+ years, deprecated, etc.)
Works on Python and Node projects
--strict flag exits with code 1 — great for CI pipelines
depwise why explains what's wrong with a specific package
Sample output from scanning my own project today:

"python-dotenv@1.0 medium 1 CVE fix: 1.1.2
python-dotenv: Symlink following in set_key allows arbitrary file overwrite

1 vulnerable, 1 ok

to fix:
pip install python-dotenv==1.1.2"

Found a real CVE in my own codebase while testing. Caught in 3 seconds.

The bug I fixed today
Version 0.1.0 had an embarrassing flaw.
If the network check failed — firewall blocking osv.dev, timeout, rate limit, anything — the tool silently reported every package as ok. No warning. Nothing.
For a security tool that's the worst possible failure mode. You'd think you're safe when you're actually just unchecked.
0.1.1 fixes this. Now it shows unknown (check failed) with an explicit message not to trust the result.
Honest output matters more than clean output.

Why zero dependencies?
A scanner that introduces attack surface is a bad scanner. Every dependency you add is something that could have its own CVE tomorrow.
Also I built this entirely from my laptop

What's next
GitHub Actions support
Lock file support (poetry.lock, package-lock.json)
More ecosystems (Go, Rust)
If something's broken or missing, open an issue.
GitHub: https://github.com/hunzo1/depheal

Thanks for reading the full post.

I build my own coding language specifically for bug bounty hunters. You will find it on GitHub with setup guide inside README.md GitHub: GitHub.com/InterviewCopilot350/Vroxscript I will upgrade it as per user's request and as well looking for developers

Prince — Sun, 22 Mar 2026 09:53:10 +0000

I built my own programming language on Android with no laptop. Meet VroxScript.

Prince — Sun, 22 Mar 2026 09:47:05 +0000

The Problem

I started learning bug bounty hunting with nothing
but an Android phone and Termux.

Every time I needed to do recon I had to write
50+ lines of Python just to scan subdomains and
check alive hosts. It was frustrating.

So I built my own language.

Meet VroxScript

VroxScript is a security scripting language where
full recon takes 7 lines instead of 200.


vs
scan subdomains target.com >> subs.txt
alive scan_results >> alive.txt
ports target.com >> ports.txt
headers https://target.com >> headers.txt
fuzz https://target.com >> fuzz.txt
secrets fetch_body
report target.com >> report.txt
Built on Android
No laptop. No fancy setup. Just:
Android phone
Termux
Go compiler
Determination
How it works
VroxScript is interpreted by Go which makes it:
Fast — concurrent scanning with goroutines
Portable — single binary
Simple — no dependencies
Features
Subdomain scanning
Port scanning
Directory fuzzing
Security header checking
Secret detection
DNS lookup
Wayback Machine integration
Full report generation
Get it
GitHub: github.com/InterviewCopilot350/vroxscript
What I learned
Building a programming language taught me more
about networking, compilers and Go than any
tutorial ever could.
— Prince, India