Vulnerability management
We run continuous software composition analysis (dependency scanning) and static application security testing (SAST) on our code, patch on a regular cadence, and stay on current, supported runtimes — so known issues are found and fixed early.
What this looks like in practice
- Continuous software composition analysis (dependency scanning) watches every library we ship.
- Static application security testing (SAST) runs on our own code.
- We patch on a regular cadence — not just when something makes the news.
- We stay on current, supported runtimes.
Why it matters
Most breaches start with a known, unpatched issue. Continuous scanning plus a regular patch cadence means known issues are found and fixed early.
- Dependency scanning
- SAST
- Regular patch cadence
- Supported runtimes
Have a security question?
We're happy to walk through our practices in more detail, share documentation, or hear about a concern. A human reads every note.
This page describes our security posture at a high level for transparency; it is not a contractual commitment.