Security

Security and vulnerability reporting

Read Svavyom’s Development Preview security expectations and how to report a vulnerability privately on GitHub.

Development-preview boundaries

What to expect

This is a pre-alpha. Treat it accordingly.

01

Disposable environments only

Keep development exploration in disposable environments. Do not give this pre-alpha production workloads or credentials.

02

Not security-qualified

The safety design limits what services can do, but it is not a security qualification, and release artifacts are not signed yet.

03

Evidence is not proof

Passing scanners and tests reduce known risk; they do not prove safety.

Reporting

Vulnerability reporting

Use GitHub private vulnerability reporting on the repository. Do not publish credentials or exploit details in public issues.

Report a vulnerability privately