Skip to content

Security: ryandelauz/peptide-library-api

Security

SECURITY.md

Security policy

The Peptide Library API (https://api.peptidelibrary.app/v1) is a hosted, read-only service. API keys are generated server-side, shown once and stored only as a SHA-256 hash.

Reporting a vulnerability

Email support@peptidelibrary.app with "Security" in the subject: what you found, how to reproduce it and the impact you expect. Please don't open a public issue for a security problem. We acknowledge reports within 3 business days.

In scope: the API, the developer portal and dashboard at peptidelibrary.app/developers, and the SDKs in this repository. Please don't run load or denial-of-service tests; the API is rate-limited.

If your key leaks

Rotate or revoke it at once in the developer dashboard. A rotated key stops working immediately.

Design notes

  • Read-only: every endpoint is GET. User text reaches the database only as bound RPC parameters.
  • Keys never appear in responses, logs or error messages; Sentry scrubs API request headers.
  • Errors never include stack traces or internal details. Each response has an X-Request-Id to quote when you contact us.
  • Outbound vendor links go through https://peptidelibrary.app/go/…, which redirects only to links stored server-side (no open redirect).

There aren't any published security advisories