Skip to content

Security: jargonsdev/jargons.dev

SECURITY.md

jargons.dev Security Policy

If you believe you have discovered a potential security issue or vulnerability in jargons.dev, one of the jargons.dev experimental products, our systems, services we use, or anything that may compromise the integrity and well-being of our platform, please disclose it to us by submitting this form at hi.new/ola. Please do not report security vulnerabilities through public GitHub issues, pull requests, discussions, or any other public forum. Only report issues via the form at hi.new/ola. Someone will be in touch with you as soon as possible.

What to Include in Your Report?

Your report should include:

  • A clear description of the issue, including steps to reproduce it.
  • Any details you think would help us understand the potential impact of the vulnerability.
  • Information about your system, the software you are using (such as Chrome, Firefox, Safari, etc.), and how you discovered the vulnerability.

What to Expect After Reporting a Vulnerability?

Once submitted, your report will be reviewed. We will then work with you to understand more about the issue and, if verified, make all efforts to address the vulnerability promptly.

We appreciate your efforts in keeping our community, users, and products safe. Thank you for your support in responsibly disclosing any issues.

There aren’t any published security advisories