Security
This page explains the security measures in place on this website and in the Rift repository, and how to report a vulnerability.
Last updated: 14 November 2026.
Source code
Rift and this website are open source. You can inspect both in the LucaPipolo/rift repository on GitHub (opens in a new tab): the website lives in its docs/ folder.
What keeps this website secure
Every page is sent with a Content Security Policy (opens in a new tab) that allows only the scripts and styles the page itself needs, listed by hash, and with the other security headers recommended by the OWASP Secure Headers Project (opens in a new tab). The policy is generated from each built page, so it always matches what the page contains. The website is static: it has no forms, no accounts and no server-side code that handles your input.
Security automation on GitHub
The repository has secret scanning with push protection (opens in a new tab) switched on, which blocks attempts to push credentials or keys into the code, and Dependabot alerts (opens in a new tab), which flag known vulnerabilities in Rift's dependencies.
Reporting a vulnerability
Rift installs a certificate authority in your system's trust store and runs a router that serves your projects, so reports of anything that could weaken that are very welcome. Don't open a public issue. Report it privately instead:
- through GitHub's private vulnerability reporting (opens in a new tab), which stays visible only to the maintainer until it is fixed, or
- by email to dev@lucapipolo.com.
The repository's security policy (opens in a new tab) explains what to include, which versions receive fixes, and what is in scope. The same contact details are published in a machine-readable form at /.well-known/security.txt.