Engineer & founder in South London

OluwasegunOlumbe.

I write software for a living and run BashBop, an events company, on the side. Most of my open-source work started because I hit the same problem twice in my own repos and got tired of guessing.

Oluwasegun Olumbe

Products

All under BashBop Ltd. Events pay the bills; the other two started at my kitchen table.

BashBop events & ticketing

Ticketing for UK diaspora organisers. The tickets part is straightforward; getting money between the UK and Lagos without it falling over is not. I built this because I kept seeing organisers patch together WhatsApp, spreadsheets, and prayer. Stack is Docker Compose, Cloudflare R2, Paystack and Stripe. I'm still the person who gets the 2am call.

Brain Boost Buddy desktop · ks2

A Mac and Windows app that locks the laptop at login until your child passes a short quiz. Maths, English and money, aimed at UK KS2 (ages 9–11). I built it when screen time kept turning into a daily argument. You hold the parent PIN; they earn the unlock. Sold as a one-time purchase.

Snap A Bird mobile · birds

My son Nathan can ID birds by call. The rest of the family cannot. So I built him an app: point the phone, get a species name. It covers 964 UK birds, runs on-device with BirdNET, works offline on walks with no signal, and costs nothing. Sightings feed an open dataset researchers can use under Creative Commons.

Open source

Five packages on npm now. Four of them check one thing each; gate runs all four and gives you a single yes/no. I reach for them in CI before I trust an agent with the same question.

all on npm — gate's also in VS Code and Cursor

gate unified verdict

The four below each check one thing. I got tired of running them one at a time and reading four outputs, so gate runs all four and gives you a single answer: pass, warn, or fail. Same thing in CI, as an MCP server an agent can call, and as a VS Code / Cursor extension that drops the verdict in your status bar and underlines whatever failed.

the four it runs ↓

repoctx repo context

Builds a map of your repo (imports, call paths, tests, permissions) so a reviewer or agent knows what a change actually touches before anyone edits anything. Runs locally; there's an MCP server if you want agents to call it.

tieline contract drift

Checks whether your frontend and backend still agree. You usually find out they don't when something 500s in production; this fails in CI instead. Adapters for a few common stack shapes.

bouncer compliance

Runs your controls against versioned rule packs for the UK Online Safety Act and the ICO Children's Code. The rules are plain files you can diff. Useful when "is this lawful?" is not a question you want a chatbot answering.

aiglare ai governance

Finds places in a JS/TS codebase where model output reaches a user or triggers a side effect (payments, email, writes) without guardrails. Maps findings to SOC 2, EU AI Act, NIST AI RMF, and OWASP LLM Top 10 controls. Outputs ESLint-style lint, Markdown evidence docs, or a branded HTML report for auditors. Fails the build on red; ignores the rest.