Security engineer — open-source tooling
I build security tools that teams run in their own pipeline.
Vulnerability triage with EPSS and KEV prioritisation, Sigma rule conformance testing, tamper-evident engagement evidence ledgers, and auditing for the AI systems that ship beside them. All 30 published projects are MIT licensed, and every test count quoted here was measured by running that suite.
- 30 open-source projects published
- 2,103 test cases across 28 projects, measured by running them
- 30 of 30 projects MIT licensed
- 15 of 16 Node tools with zero runtime dependencies
Why sponsorship, and why this way
Open-source security tooling has a funding problem that nobody solves by writing more documentation. Sponsorship pays for the parts nobody sees: triage on issues that arrive from strangers, CI maintenance, dependency review of my own tools, and the next release. That is what a sponsor is buying, and it is why the tools stay free and free of telemetry.
All 30 published projects are MIT licensed, 22 of them run a CI workflow, and 28 have a test suite whose size was measured. The tools are free to use without an account. There is no upsell path, no telemetry, and no lock-in. If a sponsor ever stops paying, the tools keep working exactly as before.
Featured tools
These six are featured on the GitHub Sponsors profile. Each one is MIT licensed, runs a working CI pipeline, and ships with a test suite whose size was measured.
-
fixqueue
Merge SARIF, Trivy, Grype and OSV scanner output into one deduplicated, EPSS and KEV prioritised fix queue.
129 testsJavaScript -
rulebench
Sigma rule conformance harness: run rules against events, lint them, and measure coverage against the MITRE knowledge base.
187 testsPython -
opsledger
Tamper-evident evidence ledger for red-team engagements: hash-chained events and a signed manifest.
115 testsJavaScript -
iamosiac
Offline cloud-IAM policy review and permission-relationship visualisation data with least-privilege remediation hints.
39 testsPython -
violet-trace
A safe purple-team validation harness for defensive telemetry and detection-rule tests.
34 testsPython -
accessweave
Offline identity-relationship and directory-permission review from explicitly exported inventory data.
33 testsPython
Two ways to work together
-
Sponsor the open-source tools
Recurring monthly support from 5 dollars, or a one-time contribution that funds a specific bug, feature or release. Prices are published and never change after they are set.
-
Hire me for paid security work
Web and API security assessments, secure code review with threat modelling, and security automation builds. Starting prices are published so you know the floor before you enquire.
How I work
- Read the code path first, before running tools.
- Reproduce the bug with the smallest possible proof.
- Quantify the impact in the business terms the engineer cares about.
- Write the fix as a code suggestion, not just an observation.
- Measure before and after, and quote only the numbers a command produced.