Skip to content

Security: magicdude4eva/btc-fullnode-stack

Security

SECURITY.md

Security Policy

Supported versions

Unless a repository states otherwise, only the latest release (or the main branch for projects without releases) receives security fixes.

Reporting a vulnerability

Please do not report security vulnerabilities through public issues, discussions or pull requests.

Use GitHub's private vulnerability reporting instead:

  1. Open the affected repository on GitHub.
  2. Go to the Security tab.
  3. Click Report a vulnerability.

Please include as much of the following as you can:

  • The affected repository, version / commit and component
  • Steps to reproduce, or a proof of concept
  • The impact you expect (e.g. credential exposure, remote code execution)
  • Any suggested fix or mitigation

What to expect

  • An acknowledgement within 7 days.
  • An assessment and, where confirmed, a fix or mitigation plan as soon as practical.
  • Credit in the advisory once a fix is published, unless you prefer to stay anonymous.

These are personal open-source projects maintained in my spare time, so please allow reasonable time before public disclosure.

Scope notes

Several projects (e.g. Docker images and node stacks) bundle or wrap third-party software. Vulnerabilities in the upstream software itself should be reported to the upstream project; issues in how my projects package, configure or expose it are in scope here.

There aren't any published security advisories