Contact
Get in touch
Two channels, both of which reach me directly. Use whichever suits you — there is no form to fill in and no sales funnel.
-
For paid work
Security assessments, code review and threat modelling, and automation builds. Fastest on Fiverr, where the order flow is built in.
-
For sponsorship and questions
Questions about a tool, a tier, or whether an engagement fits. Sponsorship itself is set up on GitHub.
-
For everything else
Professional context, background, and a direct route to a conversation.
What to include in an enquiry
It saves a round trip if the first message covers these four points:
- What you need. An assessment, a code review, an automation build, or a sponsorship question.
- The target. For an assessment: the application or API, and roughly how many endpoints or services are in play. For a code review: the repository or the pull requests.
- Authorization. That you own the targets, or are authorized in writing to test them. Testing does not begin before that exists.
- Your deadline. What you need the result by, and anything hard about it — a compliance date, a launch, a production freeze.
Scope is agreed in writing before any testing. If you cannot
confirm ownership or authorization of a target, I will say so and suggest where
to go instead. That is not negotiable, and it is the reason the work has any
value.
Where I am
India, working remotely with clients anywhere. Available for remote and hybrid roles in Delhi NCR as well as contract engagements.
Other ways to see the work
- The GitHub profile — all 30 authored projects.
- The project list — with measured test counts.
- GitHub Sponsors — the tiers and what they fund.