Skip to content

Security: OneDot-Communications/Onedot-JS

Security

SECURITY.md

Security Policy

Supported Versions

Use this section to tell people about which versions of your project are currently being supported with security updates.

Version Supported
1.0.x ✅
< 1.0 ❌

Reporting a Vulnerability

We take the security of our software seriously. If you believe you've found a security vulnerability in our code, please follow these steps to report it:

  1. Do not disclose the vulnerability publicly.

  2. Email us at security@onedotjs.com with a description of the vulnerability.

  3. Include the following information in your report:

    • Your name and contact information
    • A detailed description of the vulnerability
    • Steps to reproduce the vulnerability
    • Any potential impact of the vulnerability
    • Any suggested fixes or mitigations
  4. We will acknowledge receipt of your report within 3 business days and provide an estimated timeline for a fix.

  5. We will keep you informed of our progress in addressing the vulnerability.

  6. Once the vulnerability is fixed, we will release a security patch and give you credit for the discovery (unless you prefer to remain anonymous).

Security Best Practices

We follow security best practices throughout the development process, including:

  • Regular security audits
  • Dependency scanning
  • Secure coding guidelines
  • Penetration testing
  • Code reviews with a focus on security

We encourage all users to follow security best practices when using our framework, including:

  • Keeping dependencies up to date
  • Using secure coding practices
  • Implementing proper authentication and authorization
  • Validating and sanitizing user input
  • Using HTTPS in production
  • Implementing proper error handling
  • Following the principle of least privilege

Thank you for helping us keep ONEDOT-JS secure!

There aren't any published security advisories