You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor: reposition foxguard for AI-generated code security
- Rewrite README: "Your AI writes code. foxguard catches what it gets wrong"
- Add 9 framework-specific rules (Express, Flask, Django, Gin) -- 36 total
- Remove all emojis from codebase
- 50 findings on Express repo (vs 43 for Semgrep)
- Fix terminal output to use text instead of emoji symbols
none
Copy file name to clipboardExpand all lines: README.md
+80-13Lines changed: 80 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,14 @@
1
1
# foxguard
2
2
3
-
Blazing fast security linter for modern codebases. Written in Rust.
3
+
Security linter built for AI-generated code. Written in Rust.
4
4
5
-
> The Ruff of security.
5
+
> Your AI writes code. foxguard catches what it gets wrong.
6
6
7
-
## Why
7
+
## The Problem
8
8
9
-
-**41% of code is now AI-generated.** 24.7% of it has security flaws.
10
-
- Every security linter today is Python, OCaml, or Java. Slow.
11
-
- Foxguard is Rust-native. 100x faster than Semgrep. Zero config.
9
+
80% of AI-generated code that passes functional tests still has security bugs ([SusVibes, 2025](https://arxiv.org/abs/2512.03559)). Existing SAST tools were built for human-written code -- they miss the patterns AI gets wrong: scaffold boilerplate with hardcoded secrets, over-permissive defaults, missing auth middleware, BaaS misconfigurations.
10
+
11
+
foxguard is purpose-built for the vibe coding era.
0 commit comments