Contact jev-seo
Every channel is a direct line. No forms, no ticket queues, no response-time SLA hidden behind a dashboard.
Bugs and feature requests
The fastest way to reach this project is a GitHub issue. Bug reports, feature requests, and questions are all welcome. Response time on issues is typically within a day.
What to include in a report
A good report ships four things: the exact command you ran, the version (jev-seo --version), your operating system, and the full output or error text. Screenshots help for anything visual. Reports that arrive with this detail can usually be reproduced and fixed on the first pass; issue threads that require three rounds of back-and-forth usually get deprioritized.
Security vulnerabilities
For security problems, open a private security advisory on the repository instead of a public issue, so a fix can ship before the disclosure. Security findings get priority over everything else, including feature work in flight.
Response expectations
This is a single-maintainer open source project, not a support organization. Issues get read, bugs get fixed, and features get built in the order they matter to the most users. If something is blocking you, say so in the issue — urgency is visible in the thread, not assumed by it.
Author
jev-seo is built and maintained by Akash Priyadarshi from Patna, Bihar, India.
- Portfolio: akashpriyadarshi.vercel.app
- GitHub: AkashPriyadarshii
- LinkedIn: Akash Priyadarshi
- X / Twitter: @Akash__ydv001
- Threads: @akash.priyadarshii
- Reddit: DragonfruitWeak2801