Trending Security repositories

Security tooling splits into four buckets that teams adopt across, not from. Static analysis (semgrep, CodeQL, Bearer, language-specific linters). Software composition analysis (Trivy, Grype, OSV-Scanner, Syft). Secret scanners (Gitleaks, TruffleHog, detect-secrets). And the security-automation layer — SBOM builders, policy engines, IaC linters, the red-team toolbox. Signal patterns are weird here. A critical CVE drop drives huge traffic to whichever scanner detects it first, then settles. Project usage routinely outpaces star counts because enterprises adopt scanners without publicly contributing love. The ranking smooths the spikes by counting sustained mentions alongside GitHub velocity. The unflashy security tools are usually the best ones — projects with a decade of incremental release notes outperform the viral newcomer over any horizon longer than a quarter. When evaluating, signal-to-noise ratio matters more than feature count: every scanner produces false positives, and how the project triages them tells you what working with it will feel like.