Skip to content

Security: Omnikon-Org/IssuesSwipe

Security

security.md

Security Policy

Supported Versions

The latest version of this project is actively maintained and receives security updates.

Version Supported
Latest (main) ✅ Yes
Older versions ❌ No

Reporting a Vulnerability

The security of this project is important to us. If you discover a potential security vulnerability, please report it responsibly.

Please do not disclose security vulnerabilities publicly until they have been reviewed and addressed.

How to Report

Please include the following information in your report:

  • A clear description of the vulnerability
  • Steps to reproduce the issue
  • Potential impact
  • Proof of concept (if available)
  • Suggested mitigation (optional)

Submit your report through one of the following methods:

  • Open a Private Vulnerability Report using GitHub's security reporting feature (preferred, if enabled).
  • Contact the project maintainers using the project's official contact method.

What to Expect

After receiving a report, maintainers will aim to:

  • Acknowledge receipt within 48 hours.
  • Investigate the reported issue promptly.
  • Keep the reporter informed of significant progress.
  • Release a fix as quickly as reasonably possible.
  • Credit the reporter for responsible disclosure, if they wish.

Response times may vary depending on the severity and complexity of the issue.


Responsible Disclosure

We ask that you:

  • Do not publicly disclose vulnerabilities before a fix is available.
  • Avoid actions that could impact the privacy, integrity, or availability of systems or data.
  • Do not access, modify, or delete data that does not belong to you.
  • Only perform testing necessary to demonstrate the existence of the vulnerability.
  • Act in good faith while reporting security issues.

Security Best Practices

Contributors are encouraged to:

  • Keep dependencies up to date.
  • Never commit secrets, API keys, or credentials.
  • Store sensitive configuration outside the source code.
  • Review third-party dependencies before introducing them.
  • Follow secure coding practices.
  • Report suspicious behavior or potential vulnerabilities promptly.

Security Updates

Security fixes are released through the project's normal development and release process. Critical issues may be addressed outside the regular release cycle when necessary.


Thank you for helping improve the security and reliability of this project through responsible disclosure.

There aren't any published security advisories