Skip to content

Security: sequentech/step

Security

SECURITY.md

Security Policy

Sequent Tech welcomes reports from security researchers, consumers, election auditors and the general public. Our Vulnerability Disclosure Policy explains what is in scope, how we handle your report, the safe harbor we offer and how we credit reporters. It is the authoritative version; this file only summarizes how to reach us.

Reporting a vulnerability

Please do not report security vulnerabilities through public GitHub issues, discussions or pull requests.

Email security@sequentech.io instead. For sensitive details, encrypt your report to the Sequent Security Team OpenPGP key:

Encryption is recommended but not required. Where possible, include the affected component and version, reproduction steps or a safe proof of concept, the potential impact, and whether you wish to be publicly credited.

We acknowledge reports within 5 business days.

Never test against real elections or production environments. Use a local or dedicated test deployment; the Try It Out section explains how to run the platform yourself.

Machine-readable contact

Our RFC 9116 security.txt is published at https://docs.sequentech.io/docusaurus/main/.well-known/security.txt. Its signed master copy is docs/docusaurus/static/.well-known/security.txt.

There aren't any published security advisories