Cybersecurity engineer and builder of secure systems, developer tools, and applied research prototypes.
I work across defensive security, privacy-preserving applications, low-level systems, software supply-chain risk, and AI-assisted developer tooling. My repositories are a working portfolio: some are practical utilities, while others are deliberately constrained research artifacts for controlled laboratories.
| Area | Selected work | Engineering focus |
|---|---|---|
| Application defense | SQLi-Blocker-WAF | Request inspection, reverse-proxy behavior, rate limiting, and safe observability. |
| Privacy and secure exchange | Secure-Drop | WebRTC-based peer exchange with a separately hardened signaling layer. |
| Cryptography and local security | VaultDestruct | Local encrypted storage, password-derived keys, and explicit destruction limitations. |
| Supply-chain security | SupplyGuard | Dependency risk analysis, package intelligence, and defensive review workflows. |
| Systems and networking | ZeroCopy-Firewall | eBPF/XDP experimentation, packet filtering, and performance-oriented systems work. |
| AI developer tooling | Voice-to-App | Audio transcription, structured generation, and traversal-safe local output. |
| Learning platforms | PYQ-HUB | A full-stack previous-year-question platform with authentication and study workflows. |
My current interests include secure-by-default application design, vulnerability research in authorized environments, network and kernel observability, software supply-chain defense, privacy-preserving collaboration, and reliable AI-assisted development. I value small, reviewable changes, explicit threat models, reproducible tests, and documentation that states limitations as clearly as capabilities.
| Principle | How it appears in my work |
|---|---|
| Secure defaults | Local-only binding, bounded inputs, explicit origins, timeouts, and secret-safe logs wherever the design permits. |
| Honest claims | Experimental projects are labeled as research or portfolio artifacts instead of being presented as production-ready without evidence. |
| Reproducibility | Repositories include setup guidance, dependency-update configuration, security policies, and lightweight automated checks where appropriate. |
| Responsible use | Security-sensitive code is intended only for systems and environments where the operator has explicit authorization. |
The public repository set spans security research, privacy tools, AI utilities, web applications, and learning projects. Start with the featured projects above, then browse the repository topics and README files for the implementation details, current status, and limitations of each project.
Important: Security-sensitive repositories are provided for education, defensive engineering, authorized testing, and controlled research. Do not use them against systems, accounts, networks, or data without explicit written permission. No repository should be treated as a substitute for a professional security review.
I am also building five focused utilities for common developer workflows:
| Need | Repository |
|---|---|
| Diagnose a broken local project setup | workspace-doctor |
Inspect and redact .env files safely |
envsafe |
| Catch breaking OpenAPI changes in CI | openapi-guard |
| Draft honest release notes from git history | release-craft |
| Manage parallel Git worktrees for branches and AI agents | worktree-flow |
Each project is intentionally small, local-first where practical, and designed to produce a useful result within minutes of cloning. If one solves a real problem for you, a star helps other developers find it.
If you are browsing for a practical project, begin with the repository that matches your goal:
| You want to… | Start with |
|---|---|
| Inspect a defensive web-security pattern | SQLi-Blocker-WAF |
| Send files peer-to-peer without a cloud upload | Secure-Drop |
| Explore local encrypted storage | VaultDestruct |
| Audit MCP server configurations | MCP Audit Scanner |
| Build RAG or LLM tooling | RAG Eval Studio or Tiny RAG |
| Self-host AI and automation services | Self-Host Starter |
I am interested in collaborating on defensive security engineering, secure developer tooling, privacy-preserving applications, systems research, and responsible vulnerability disclosure.
If a repository helps you learn, prototype, or solve a real problem, please star that specific repository. Stars help other developers discover the project; a focused issue, discussion, or pull request is even more useful feedback.
If you discover a vulnerability in one of my projects, please use the repository’s Security tab when private reporting is available. Otherwise, open a minimal issue without exploit details and request a private contact path. Please do not publish credentials, personal data, or weaponized proof-of-concept material.