projects · open source · how i work · stack · activity

Software developer from Germany, working at a hosting company. Most of my time goes into the parts users never see: APIs, deployment pipelines, database schemas and the automation that keeps all of it running without me. In my own time I build developer tools that do one job properly and show their work – tested, documented, released.

_{Real screenshots, live numbers – rebuilt every 3 hours by this repository's workflow.}

Free proxies that actually work. Scrapes HTTP/SOCKS4/SOCKS5 proxies from 700+ sources and verifies every hit: honeypot filter, catches proxies that inject scripts (one in five does), HTTPS with verified TLS, anonymity, country, provider and spam blocklists – and learns with every run which sources are worth it. Comes with a rotating proxy server (SOCKS5 + HTTP, sticky sessions, Prometheus metrics), an MCP server for AI agents, a live dashboard and a Discord bot.

→ Browse the live list, re-checked every hour by GitHub Actions.

Find the API keys your coding agents spilled into their logs. Claude Code, Codex, Gemini CLI, Cursor and the rest keep every conversation on disk as plain text – including each .env they read and every key you pasted "just to test". spillage reads the logs of thirteen agents, tells you which keys leaked and how (you pasted it, a tool printed it, the model repeated it), links to the page where you rotate each one, scrubs them without breaking --resume, and installs hooks that block the next leak.

• 56 rules that know each key's exact shape – GitHub tokens are checked against their CRC32, JWTs have to decode, placeholders are skipped
• Zero dependencies, zero network – standard library only, secrets are only ever shown masked
• Fits into CI – HTML, JSON, Markdown and SARIF reports, a GitHub Action and a pre-commit hook

brew install maximilianfeix/tap/spillage && spillage

Understand any TypeScript repo in one interactive map. RepoAtlas parses every import with the TypeScript compiler API and turns a project into a standalone architecture map. Unlike a diagram guessed from prose, every connection links to the exact import statement and line that proves it – with a Focus map for direct neighbours, an Impact map for everything that transitively depends on a module, and circular import groups isolated edge by edge.

npx --yes --package=github:maximilianfeix/repoatlas -- repoatlas https://github.com/pmndrs/zustand -o zustand-map.html

Try it on real projects: Zustand _{18 modules} · Ky _{51 modules} · Hono _{247 modules, 676 connections}

See the run before the run. Paste a GitHub Actions workflow and explore it as a job graph: which jobs a push or pull_request would start, what a matrix expands to, how a proposed change reshapes the pipeline – and jump from any job straight back to its YAML line. Everything is parsed in the browser; no account, no upload.

flowchart LR
    dev["Local dev<br/>Vue + Vite"] --> push["git push"]
    push --> ci["GitHub Actions<br/>lint, test, build"]
    ci --> art["Artifact"]
    art --> web["Apache / Node.js"]
    web --> api["API layer<br/>PHP, Node"]
    api --> cache[("Redis<br/>cache, sessions")]
    api --> db[("MariaDB<br/>MongoDB")]
    web --> obs["Logs, metrics,<br/>alerting"]
    obs -.->|"something broke"| dev

    classDef node fill:#1C1C1F,stroke:#C6F36B,stroke-width:1px,color:#EDEBE4
    classDef store fill:#161618,stroke:#A3A29D,stroke-width:1px,color:#EDEBE4
    class dev,push,ci,art,web,api,obs node
    class cache,db store

flowchart TD
    q{"What kind of job?"}
    q -->|"HTTP API, realtime"| n["Node.js"]
    q -->|"classic web app, CMS"| p["PHP"]
    q -->|"CLI tools, scripting, glue"| py["Python"]
    q -->|"user interface"| v["Vue + Vite"]
    n --> d1{"Data shape?"}
    p --> d1
    d1 -->|"relational"| m["MariaDB / MySQL"]
    d1 -->|"documents"| mo["MongoDB"]
    d1 -->|"hot, short-lived"| r["Redis"]
    d1 -->|"single file, embedded"| s["SQLite"]

    classDef node fill:#1C1C1F,stroke:#C6F36B,stroke-width:1px,color:#EDEBE4
    classDef decision fill:#161618,stroke:#A3A29D,stroke-width:1px,color:#EDEBE4
    class n,p,py,v,m,mo,r,s node
    class q,d1 decision

_{Also at home in Figma, Photoshop, After Effects and Blender.}

How this profile updates itself

Workflow	Status	What it does	When
Profile		renders the banner and project cards with live data (text set with HarfBuzz, so it looks the same everywhere), plus Recently shipped and Contributions (script)	every 3 hours
Metrics		activity, languages and calendar via lowlighter/metrics	nightly
Contribution snake		turns the contribution graph into the snake above	nightly
Link check		makes sure every link in this README still works	weekly

_{Open to interesting backend and infrastructure work – the easiest way to reach me is an issue or discussion on one of my repositories.}