Security Policy

Reporting a vulnerability

Please do not open a public GitHub issue for security vulnerabilities. Public issues are world-readable and would expose the report before a fix is available.

Report security vulnerabilities through GitHub’s Private Vulnerability Reporting flow. Reports go directly to repository maintainers, are not visible to other users, and provide a private channel for coordinating disclosure.

Please include in your report:

We will acknowledge receipt within five business days and provide an update on remediation timing once we have assessed the report.

Scope

This site is a Jekyll-built static marketing site for the C3 Lab. Reports we treat as in-scope:

Reports we treat as out-of-scope:

What this site stores

The site is a static-rendered Jekyll build. It does not collect form input, process authentication, or store any visitor data server-side. There is no backend database and no user-supplied content surfaced on the site.

Coordinated disclosure

We aim to issue a fix and a public security advisory within 90 days of a confirmed report, and to credit reporters who wish to be credited. If you need to coordinate disclosure timing with a conference or publication, mention this in your report and we will work with you.