Skip to content

Security: RandAOLabs/component-library

Security

docs/security.md

Security Policy

Supported Versions

We release patches for security vulnerabilities. Here are the versions that are currently being supported with security updates.

Version Supported
0.0.x

Reporting a Vulnerability

We take the security of RandAO Component Library seriously. If you believe you have found a security vulnerability, please report it to us as described below.

Please do not report security vulnerabilities through public GitHub issues.

Instead, please report them via email to security@randaolabs.com (if this email is not yet set up, please create a private security advisory in the repository).

You should receive a response within 48 hours. If for some reason you do not, please follow up via email to ensure we received your original message.

Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:

  • Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
  • Full paths of source file(s) related to the manifestation of the issue
  • The location of the affected source code (tag/branch/commit or direct URL)
  • Any special configuration required to reproduce the issue
  • Step-by-step instructions to reproduce the issue
  • Proof-of-concept or exploit code (if possible)
  • Impact of the issue, including how an attacker might exploit it

This information will help us triage your report more quickly.

Preferred Languages

We prefer all communications to be in English.

Policy

We follow the principle of Responsible Disclosure.

Safe Harbor

We support safe harbor for security researchers who:

  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our services
  • Only interact with accounts you own or with explicit permission of the account holder
  • Do not exploit a security issue for purposes other than verification
  • Report any vulnerability you've discovered promptly
  • Follow the process outlined in this policy

PGP Key

For sensitive communications, you can encrypt your message using our PGP key (to be provided).

Bug Bounty Program

We do not currently operate a bug bounty program.

There aren't any published security advisories