💭
Highlights
- Pro
Block or report somethingwithproof
Block user
Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.
You must be logged in to block users.
Close all issues, pull requests, and discussions opened by this user
Content in all repositories owned by your account will be closed.
Add an optional note
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse
Contact GitHub support about this user’s behavior. Learn more about reporting abuse.
Report abuseStaff / senior engineer working across backend systems, observability, and security hardening.
- Go — CLI tooling, CI/CD pipelines, services
- Python — automation, data pipelines, ML tooling
- PHP — upstream contributions to Cacti, phpMyAdmin
- Rust — terminal UIs, performance-sensitive tools
- TypeScript — dashboards, MCP servers
- Infra — Terraform, Kubernetes, GitHub Actions (SHA-pinned), Cloudflare
- Cacti ecosystem — security hardening for core, spine, and 20+ plugins; maintainer of several plugin fixes. See Cacti/cacti, Cacti/spine, and the plugin_* repos.
- Wikipedia / Wikidata — bot-assisted article maintenance, Cherokee Nation and Monticello sourcing projects. All edits follow WP:AISIGNS and MOS.
- Trading / market data — stonktop, trading-platform, veritas-mvp, market-data-hub.
- Genealogical research — gps-genealogy-agents (multi-agent system for GPS-compliant research).
- Developer ergonomics — dotfiles (chezmoi), MacGTD (macOS GTD capture), pipeline-library (CI/CD Go library).
Security issues in my own repos should go through GitHub Security Advisories per the repo-level SECURITY.md. For upstream projects I contribute to, follow that project's disclosure process — I do not publish pre-auth vulnerabilities as public PRs.
- GitHub: @somethingwithproof
- Commits are GPG-signed and DCO sign-off'd.
Pinned Loading
Something went wrong, please refresh the page to try again.
If the problem persists, check the GitHub status page or contact support.
If the problem persists, check the GitHub status page or contact support.