Contact / choose the accountable route
Put the question where the work lives.
Elixpo uses public discussions for public decisions, repository channels for technical work, and email for organization-level or private enquiries. Choosing the right route keeps context, responsibility, and follow-up visible.
Contact routes
One question, one responsible channel.
Please do not send private security reports, account credentials, or sensitive personal information through public Discussions.
Email Elixpo
Use email for organization-level questions, corrections, brand enquiries, and matters that do not belong to one public repository.
hello@elixpo.com 02 / ResearchDiscuss research
Use this address for research publications, reproducibility questions, author corrections, and potential research collaboration.
ayushman.elixpo@gmail.com 03 / OperationsContact operations
Use this address for operational coordination, organization administration, service ownership, and time-sensitive internal routing.
vivek@elixpo.com 04 / Projects and ChaptersStart in public
Use Discussions to propose a Chapter, ask an organization-wide question, or document an idea that benefits from an open response.
Open Discussions 05 / Repository-specific workContact the maintainer
Issues, support requests, and technical proposals should go to the owning repository so its maintainers and evidence remain connected.
Browse repositories 06 / SecurityReport privately
Follow the SECURITY.md and private reporting route in the affected repository. Do not disclose an unpatched vulnerability in a public issue.
Open organization securityEvents and community support
Partnership requests have their own published process.
Sticker quantities, event recognition, venue expectations, artwork access, and the non-monetary support boundary are documented before material is released.
Review community partnerships