I work on software security, vulnerability research, developer tooling, privacy-conscious utilities, and practical automation. I am actively moving more of my work into public open source: maintainable tools, tests, hardening changes, reproducible bug fixes, and upstream contributions.
- 🔐 Application security, systems security, secure software development, and vulnerability research
- 🛠️ Building and maintaining open-source security, privacy, and training tooling
- 🧪 Reproducible testing, source review, fuzzing, CI, and defensive hardening
- 🌱 Contributing fixes and tests upstream where they are useful to maintainers
- 🌍 Kashmir, India
- 📫 bhatmuneeb49@gmail.com
A Python CLI for authorized subdomain-reconnaissance workflows. It coordinates established enumeration and probing tools while keeping target input validated and process execution out of the shell.
Maintainer work: safer subprocess execution, domain validation, packaging, automated tests, GitHub Actions CI, contributor/security docs, changelog, and MIT licensing.
A dependency-free local repository security-hygiene scanner for maintainers and CI. It looks for high-signal mistakes such as private-key material, common token formats, risky GitHub Actions settings, hard-coded passwords, and Python subprocess calls that execute through a shell.
Design goals: local-only scanning, text/JSON/SARIF output, CI-friendly exit behavior, transparent rules, tests, and no telemetry.
A privacy-conscious IPv4/IPv6 geolocation CLI that queries a user-supplied local MaxMind database instead of sending addresses to a hosted lookup API.
Design goals: no telemetry, no automatic network requests, validated address input, JSON output, automated tests, CI, and clear limitations around GeoIP accuracy.
I am building a stronger upstream contribution record around work that is useful to real projects:
- security and correctness fixes
- regression tests for real bugs
- parser and input hardening
- build and CI reliability
- dependency and supply-chain security
- privacy-preserving developer tooling
- accessibility and developer documentation tied to substantive changes
Python · Go · C/C++ · Java · JavaScript · TypeScript · Rust · Solidity · Git · Linux
Security interests include source-code auditing, fuzzing, application security, firmware and systems security, cryptography, blockchain security, and software supply-chain hardening.
Useful issues and pull requests are welcome on the projects I maintain. Actively maintained tools include contribution or security-reporting guidance where appropriate.
If you maintain an open-source project with a well-scoped security, testing, build, accessibility, or reliability issue that could use help, feel free to reach out.
I only perform security testing on systems I own or have explicit authorization to assess.