trends.barnas.net

tool · first seen 15 Oct 2026

static application security testing

Also: SAST

Analyzing source code without executing it to detect security vulnerabilities.

Static application security testing (SAST) analyzes source code without running it to find vulnerabilities, and it has been a standard part of application security practice for many years. The recent sources are mostly evaluations and extensions of existing tools. One paper benchmarks CodeQL, Infer and Semgrep across a decade of C/C++ code, another studies SAST on Rust, and a third tests SAST across languages using EV charging protocol implementations. Several papers pair SAST with LLMs to triage, explain or test its findings, among them Snyk's VulnBench comparison with AI security agents. Small GitHub tools package SAST as Claude Code plugins or MCP servers for AI-generated apps.

The idea itself is not new. The active thread is how deterministic SAST is being combined with LLM agents, where the static analyzer stays authoritative for detection and the model handles triage, explanation and coverage gaps.

Analyst note (established), 17 Nov 2026.

Mentions per week

0319 May11 Aug10 NovPapersCodeDiscussion

PapersCodeDiscussion

Rank 53 on 14 Nov 2026 · 7 mentions in 28 days · 7 independent groups · papers → code · first seen 4 weeks ago · acceleration +0.98

Earliest sources

Latest sources

Mentioned together with

model context protocolmetamorphic testingRustmetamorphic mutation testingfalse positive reduction in static analysisAI security agents for code vulnerability detectionVulnBenchlow-rank adaptationprompt injectionrow-level security