ABOUT / BANKS

Why I built Banks.

Banks brings my security tools, technical write-ups, and working notes into one place.

Most of what ends up here starts with a specific problem: a repetitive task, a brittle workflow, a parser I needed, or a technique I wanted to understand properly. I build or test something, then document the parts worth keeping.

Banks is where I publish that work. Some projects are mature; others are still experiments. I document what I tested, what failed, and what remains uncertain so the evidence and limits are clear.

HOW I PUBLISH

What each release should make clear.

01

Show the work

Include the reasoning, tradeoffs, failed paths, and limits that affect the result.

02

State the maturity

Mark whether a project is stable, experimental, in development, or no longer maintained.

03

Stay in scope

Publish offensive material for authorized testing, defensive research, and education.