Skip to content

Security: manirajyadav-1/billingsdk

Security

.github/SECURITY.md

Security Policy

We take the security of our users and their data seriously. Thank you for responsibly disclosing any vulnerabilities you may find.

Reporting a Vulnerability

Please report security issues through GitHub's private advisory workflow:

Do not create a public issue for security reports. Using the private advisory keeps details confidential until a fix is available.

What to Include

Provide enough information to help us reproduce and triage the issue:

  • Affected version or commit SHA
  • Environment details (OS, Node.js/PNPM/NPM versions, browser if applicable)
  • Minimal reproducible steps or proof-of-concept
  • Impact assessment and potential severity
  • Any suggested mitigations

You may optionally include your preferred contact and whether you would like public credit after remediation.

Our Commitment and SLAs

We aim to:

  • Acknowledge your report within 48 hours
  • Provide a triage update within 5 business days
  • Work on a fix and coordinated disclosure as quickly as possible, typically within 90 days depending on severity and complexity

We will keep you informed of progress and proposed disclosure timelines via the advisory thread.

Coordinated Disclosure

Once a fix or mitigation is available, we will:

  • Publish an advisory with CVSS-based severity
  • Release patched versions and upgrade guidance
  • Credit reporters who wish to be acknowledged

If you discover that details have become public before a fix is available, please notify us immediately via the advisory so we can expedite mitigation.

Supported Versions

We generally provide security fixes for:

  • The latest stable release
  • The current main branch

When feasible, we may backport critical fixes to recent minor versions, but we encourage all users to stay up to date.

Scope

This policy covers vulnerabilities in this repository's source code and release artifacts. Vulnerabilities in third-party dependencies should be reported upstream; however, if a dependency issue critically impacts this project, you may still open an advisory here and we will coordinate as needed.

Safe Harbor

We will not pursue or support legal action against researchers who:

  • Make a good-faith effort to comply with this policy
  • Avoid privacy violations, data destruction, and service degradation
  • Do not access or modify data without authorization
  • Give us reasonable time to remediate before public disclosure

Thank you for helping keep the ecosystem secure.

There aren’t any published security advisories