Skip to content

Security: NeuroLift-Technologies/.github

SECURITY.md

Security Policy

Supported Versions

Each repository in the NeuroLift Technologies organization maintains its own list of supported versions. Please refer to the individual repository's documentation for details.

Reporting a Vulnerability

Please do not report security vulnerabilities through public GitHub issues.

If you discover a security vulnerability in any NeuroLift Technologies project, please report it responsibly:

  1. Email: Send details to security@neurolift-technologies.com
  2. GitHub Private Vulnerability Reporting: Use the "Report a vulnerability" button on the affected repository's Security tab.

What to Include

When reporting a vulnerability, please provide:

  • A description of the vulnerability and its potential impact
  • Step-by-step instructions to reproduce the issue
  • Any proof-of-concept code or screenshots (if applicable)
  • The affected repository, version, and environment

What to Expect

  • Acknowledgement: We will acknowledge your report within 48 hours.
  • Assessment: We will assess the vulnerability and keep you updated on our progress.
  • Resolution: We aim to release a fix within 90 days for critical vulnerabilities.
  • Credit: With your permission, we will credit you in the release notes.

Security Best Practices for Contributors

  • Never commit secrets, credentials, or API keys.
  • Use environment variables or secret management tools for sensitive values.
  • Follow the principle of least privilege in code and configuration.
  • Keep dependencies up to date and run dependency audits regularly.

There aren't any published security advisories