VIKASHEGDE

With a team of three, found a buffer overflow in a desktop operating system's font loader. Crashes reliably, and can reach code execution.

On my own, found hardcoded root credentials in a consumer IP camera line. Around 86,000 devices were exposed. My school's CCTV ran on them.

Both were reported. Nothing was sold.

A tool server that exposes standard security tooling through one interface, so an agent can run a scan, read the output and decide what to do next.

Built for authorised testing. Used to cut the manual grind out of recon.

Team registration, challenge release, flag submission checked on the server so answers cannot be read from the browser, and a live scoreboard.

Session state runs on serverless key-value storage, so it costs nothing between events.

Patient records, appointments across branches, clinical notes, before and after photos tied to treatment plans, and consent.

Billing and payment reconciliation, stock per branch that decrements per procedure, staff records and payroll, dashboards, and a portal patients log into.

Sole developer. It runs the clinic day to day.

Customers call one standard endpoint. Behind it, the gateway picks a provider on price and health, and switches when one goes down or rate-limits.

Every request is metered by tokens, priced per model, and written to a wallet and ledger. Billing runs on a queue so a slow write never blocks a response.

Also handles tenant keys, usage analytics and containerised deploys.

Catalogue, licensing and orders. Login with JWT, time-based one-time-password two-factor, and third-party sign-in.

Two payment processors with verified webhooks, written so a replayed callback cannot credit an account twice. Resumable uploads up to 2GB.

One script tag installs it. Each business gets its own knowledge base, branding and analytics.

Questions fall through three tiers before reaching a model: cache, then a curated question bank, then the model. That is where the cost saving comes from.

Enter a rank, a category and a location. It uses past cut-offs to show what is realistically reachable, and filters by distance.

No backend, no signup, no data leaving the device. The users are teenagers under real pressure, often on bad connections.

A separate pipeline turns the published cut-off documents into the bundled dataset.

Takes a PDF or a photo of notes, generates interview questions from it, records a 60 second spoken answer and scores it on clarity, accuracy and depth.

Keeps a session history so you can replay old answers.

The old version was Java and Swing. I rewrote the shell in Rust and React and kept the game-side Java alive.

The launcher picks the right build, ships its own Java runtime so users never install one, verifies and updates jars from a release channel, and streams game output into the window for support.

One codebase for Windows, macOS and Linux. I also built its marketing site, which scores 100 on every Lighthouse category.

Covers economy prices, player stats, combat records and guild admin, with a local cache so repeated lookups do not hammer the upstream API.

Read-only and rate-limit aware. Used daily by an active community.