Skip to content

Security: goobits/security

Security

SECURITY.md

Security Policy

Reporting a vulnerability

If you believe you have found a security vulnerability in @goobits/security, please do not open a public GitHub issue.

Instead, use GitHub's private vulnerability reporting:

  1. Open the Security advisories page for this repository.
  2. Click Report a vulnerability.
  3. Provide a clear description of the issue, a minimal reproduction, and the package version affected.

You can also email security@goobits.com if private GitHub reporting is unavailable to you. Please include "security advisory" in the subject line.

We aim to acknowledge new reports within 5 business days and to ship a fix or mitigation guidance within 30 days, depending on severity.

Supported versions

Version Supported
2.x
< 2.0 ❌ (unsupported)

Scope

In scope:

  • Authentication / authorization weaknesses (CSRF, admin-auth, rate-limit bypass)
  • Cryptographic weaknesses (constant-time violations, weak RNG, algorithm confusion)
  • Header-injection or smuggling in cookie / CSP helpers
  • Information leakage (token, secret, or PII surfaced by the library itself)

Out of scope:

  • Vulnerabilities in transitive dependencies (please report upstream to jose, zod, ioredis, etc.)
  • Issues that require an already-compromised host or already-leaked secret
  • Misconfiguration in consumer code (we are happy to document hardening guidance, but it is not a CVE)

Disclosure

After a fix lands, we will publish a GitHub Security Advisory with credit to the reporter (unless anonymity is requested).

There aren't any published security advisories