Skip to content

Latest commit

 

History

History
47 lines (27 loc) · 2.4 KB

SECURITY.md

File metadata and controls

47 lines (27 loc) · 2.4 KB

Security Policy

Supported Versions

We strive to keep Starlopost up-to-date with the latest security patches and improvements. Below are the versions we currently support:

Next.js

  • Supported Versions: 13.x, 14.x, 15.x
  • Unsupported Versions: 11.x, 10.x and below

Node.js

  • Supported Versions: 16.x, 18.x, 20.x
  • Unsupported Versions: 14.x and below

Reporting a Vulnerability

If you discover a security vulnerability in Starlopost, please help us by responsibly disclosing it to us. Here are the steps to report a vulnerability:

  1. Email Us: Send an email to [email protected] with details of the vulnerability. Include as much information as possible to help us understand the issue and how to reproduce it.

  2. Do Not Create an Issue: Please do not create a public issue on GitHub, as this might expose the vulnerability to others before we have a chance to address it.

  3. Expect a Response: We will respond to your email within 48 hours to acknowledge receipt of your report. We will work with you to understand the issue and provide an estimated timeline for a fix.

  4. Coordinated Disclosure: We ask that you give us a reasonable amount of time to address the issue before you disclose it publicly. We are committed to transparency and will provide regular updates on our progress in fixing the issue.

Security Updates

We regularly update Starlopost to include the latest security patches. We recommend that all users keep their installations up-to-date to benefit from the latest security improvements.

Security Best Practices

To further enhance the security of your Starlopost deployment, consider the following best practices:

  • Regular Updates: Regularly update your dependencies, including Node.js and Next.js, to the latest versions.
  • Environment Variables: Use environment variables to store sensitive information such as API keys and database credentials.
  • HTTPS: Always use HTTPS to secure data in transit between your users and the server.
  • Access Controls: Implement proper access controls and authentication mechanisms to protect user data.

Resources

Thank you for helping us keep Starlopost secure!