Skip to content
This repository was archived by the owner on Jun 28, 2025. It is now read-only.

Security: buefy/nuxt-buefy

Security

SECURITY.md

Security Policy

Reporting a Vulnerability

Do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.

Instead, use one of the following private channels:

  1. Preferred: use GitHub Security Advisories on the affected repository ("Security" tab → "Report a vulnerability"). This opens a private advisory thread directly with maintainers.
  2. If a repository does not have private reporting enabled, contact the maintainer(s) listed in that repository's .github/CODEOWNERS (or this org's .github/CODEOWNERS as a fallback).

Please include:

  • A description of the vulnerability and its potential impact.
  • Steps to reproduce, or a minimal proof-of-concept.
  • The affected package name(s) and version(s).

Response Process

  • We aim to acknowledge new reports within 5 business days.
  • We aim to provide an initial assessment (severity, affected versions, planned timeline) within 10 business days.
  • Once a fix is available, we will coordinate a disclosure timeline with the reporter and publish a GitHub Security Advisory with credit to the reporter (unless anonymity is requested).

Supported Versions

Only the latest major release of a given package receives security patches, unless a repository's own SECURITY.md states otherwise. Pre-1.0 packages are patched on a best-effort basis.

Status Supported
Latest major release Yes
Older major releases No
Pre-release / next Best effort

Scope

This policy covers vulnerabilities in code published by repositories under the buefy GitHub organization. Vulnerabilities in third-party dependencies should be reported upstream; if a dependency vulnerability is directly exploitable through a buefy package's public API, please still report it to us so we can patch or pin around it.

There aren't any published security advisories