Skip to content

SECURITY.md

Latest commit

 

History

History
22 lines (13 loc) · 1.1 KB

SECURITY.md

File metadata and controls

22 lines (13 loc) · 1.1 KB
Raw

Security Policy

Supported versions

Security fixes land on the latest released major version.

Reporting a vulnerability

Do not open a public issue for security problems.

Report privately through GitHub's security advisory form. Include the affected version, a description of the problem, and steps to reproduce it.

You can expect an acknowledgement within a few days. Once a fix is ready it will be released and the advisory published with credit to the reporter, unless you ask to stay anonymous.

Handling credentials

This SDK deals with OAuth2 access and refresh tokens and with financial data.

  • Access and refresh tokens are secrets. Store them server-side, never in client code or version control, and never log them.
  • Refresh tokens rotate on every use. Persist the new token after each refresh.
  • Webhook payloads must be verified with WebhookVerifier (HMAC-SHA256) before you trust them.
  • The OAuth2 state parameter and the PKCE code verifier are the consuming application's responsibility to generate, store, and validate.