chore(security): lint
Some checks failed
CI / test-backend (push) Successful in 34s
CI / build-frontend (pull_request) Successful in 2m22s
CI / lint (push) Successful in 2m58s
CI / test-backend (pull_request) Successful in 21s
Build and Publish Docker Image / build (pull_request) Has been skipped
CI / test-lang (pull_request) Successful in 1m4s
OSV-Scanner PR Scan / scan-pr (pull_request) Successful in 32s
Build and Publish Docker Image / build-dev (pull_request) Failing after 6m4s
CI / test-lang (push) Successful in 9m43s
CI / build-frontend (push) Successful in 9m49s
CI / lint (pull_request) Successful in 9m49s
Tests / test (push) Successful in 12m0s
Build Test / Build and Test (pull_request) Successful in 15m12s
Build Test / Build and Test (push) Successful in 16m4s
Tests / test (pull_request) Successful in 19m41s
Benchmarks / benchmark (pull_request) Successful in 33m48s
Benchmarks / benchmark (push) Successful in 33m54s

This commit is contained in:
2026-01-05 11:48:12 -06:00
parent a9e881a095
commit 144cc53cd9

View File

@@ -32,4 +32,3 @@ The project employs continuous security monitoring and testing:
- **Pinned Actions**: All CI/CD workflows use pinned actions with full URLs to forked, vetted actions hosted on our Gitea instance (`git.quad4.io`) to prevent supply chain attacks.
- **Extensive Testing & Fuzzing**: Comprehensive backend benchmarking suite with high-precision timing, memory delta tracking, and extreme stress modes to ensure stability and prevent resource exhaustion.
- **Linting & Code Quality**: Strict linting rules and static analysis are enforced on every push.