Light WAF is developed on GitHub under Apache-2.0. Issues, pull requests, detection rules and documentation fixes are all welcome.
Open an issue with the config, the request, and the verdict you expected. False positives — legitimate traffic that gets blocked — belong here, with a reproducing request.
Open an issue →Fixes, detection improvements, new corpus cases, docs. Read the contributing guide first — it covers the build, the test suites, and the sign-off.
Contributing guide →Every release is tagged on GitHub with notes, and the changelog lists what changed in each version.
Releases →Light WAF is a security product, so a way to get an attack past it is a vulnerability too. Don't open a public issue for a detection bypass or a flaw in the proxy, control plane, agent or operator — use GitHub's private vulnerability reporting. The security policy explains the scope and what to expect.
Supply chain. GitHub Actions pinned to commit SHAs and image bases to digests, kept fresh by Dependabot; CodeQL and fuzzing on every change; every container image gated on a vulnerability scan and signed with Sigstore, release assets with SLSA provenance. The repository's practices are graded continuously by OpenSSF Scorecard, and the project meets the OpenSSF Best Practices criteria.
Everything in the repository is Apache-2.0, and contributions are accepted under the same license. Read the license.
Every commit carries a Developer Certificate of Origin sign-off — git commit -s. There is no CLA to sign.
The project follows the Contributor Covenant. Be respectful; the code of conduct says how to report a problem.
User-visible changes are recorded in the changelog, following Keep a Changelog and Semantic Versioning.