If you believe you've discovered a security issue in VAANI — an API key leak, a code-injection vector, a privacy concern, an auth bypass, or anything that could be abused against users of the live deployment — please do not open a public GitHub issue. Instead:
- DM Arun AK on LinkedIn: https://www.linkedin.com/in/arun-ak-thapar/
- Include: a description of the issue, steps to reproduce, and any proof-of-concept if you have one.
- I'll acknowledge within 72 hours and, if the report is valid, credit you in a post-patch note (unless you prefer to remain anonymous).
Please do not publicly disclose the vulnerability until we've had a chance to patch it.
If you see VAANI — code, demo videos, carousel PDF, architecture diagrams, screenshots, or pitch material — being presented as someone else's work, please report it.
Where to report first (depending on the platform):
| Platform | Action |
|---|---|
| LinkedIn post falsely claiming authorship | Click the … on the post → Report post → Intellectual property. Then DM the author (Arun AK) with the post URL. |
| GitHub fork claiming the work | Use the Report abuse link on the fork → DMCA takedown. DMCA template: https://docs.github.com/en/site-policy/content-removal-policies/submitting-notices-of-copyright-infringement |
| Hackathon or competition submission | Email the organizers with: (1) the infringer's submission, (2) this repo's URL with original commit timestamps, (3) a link to the LICENSE.md in this repo. |
| YouTube video claiming the build | YouTube → Report → Infringes my rights → Copyright infringement. |
| Instagram / X / other social posts | Use the respective platform's IP / DMCA reporting flow. |
| Academic / research submission | Contact the journal or conference's ethics committee. |
Also DM the author on LinkedIn (https://www.linkedin.com/in/arun-ak-thapar/) with a link to the infringement — this creates a time-stamped record of your report.
Per LICENSE.md Section 3, the following require written permission from Arun AK and are otherwise prohibited:
- Reproducing, hosting, or redistributing any part of VAANI under another person's or team's name
- Submitting VAANI (or a substantially similar system) to a hackathon, competition, academic project, portfolio, resume, LinkedIn post, startup pitch, or any public material, representing the work as one's own or one's team's
- Using demo videos, carousel slides, screenshots, or pitch assets in presentations without attribution
- Commercial deployment or monetization of VAANI, its derivatives, or its assets
- Training ML models on VAANI's code, documentation, or captured motion-capture data
- Cloning the repo to your own machine to learn how it works
- Quoting up to 10 lines of code with clear attribution (
"VAANI by Arun AK"+ repo URL) - Discussing VAANI in articles, research papers, or portfolio material with attribution
- Forking the repo for personal experimentation that stays private and isn't published under your name
Original engineering author: Arun AK (@Arun07AK)
Canonical repository: https://github.com/Arun07AK/vaani
Original 24-hour build date: 2026-04-18 / 2026-04-19 (Hack Helix 2026)
Dated git commits from that window serve as the primary proof of authorship timeline.
If anyone disputes authorship, GitHub's immutable commit history and timestamps are authoritative.