You can now use anonymous metavariables when writing or customizing rules, which have the form $_
. These metavariables do not bind in the environment, meaning they also do not unify. As such, patterns like:
foo($_, $_)
can match code like
foo(1, 2)
Happy rule writing!
Users can now select findings and use the "Analyze" button to run all Semgrep Assistant functions (autofix, autotriage, and component tagging) on the selected findings. Once the analysis is completed, users will see results if they:
filter by Fix/Ignore
filter by AI Component Tags
If they select "No Grouping" instead of "Group by Rule" they will see false positive or true positive recommendations directly in their findings.
Semgrep Assistant (Semgrep’s AI integration) can now categorize and tag findings based on the component they are found in. Users can use these tags to prioritize findings (only show findings related to user authentication, PII, etc.).
Semgrep's VSCode extension (v1.6.2+) can run natively on Windows. Semgrep Platform uses LSP.js as a way of supporting Semgrep on Windows.
Go, Java, Javascript, and Typescript’s interfile analysis support is now GA. All cross-functional analysis language support is now GA.
Learn more
Users can now scan C# projects with Semgrep Code’s Pro Engine, leveraging advanced interfile analysis to uncover more complex vulnerabilities while reducing noise.
Use Semgrep’s plugin for IntelliJ products (AppCode, Aqua, CLion, DataSpell, DataGrip, GoLand, IntelliJ IDEA Ultimate, PhpStorm, PyCharm Professional, Rider, RubyMine, RustRover, WebStorm) to scan for Semgrep Code and Supply Chain vulnerabilities.
The findings page, in group by rule view, now has an assistant recommendation filter. When you filter to recommended ignores, we now show Assistant's explanation inline. Pressing 'Agree' there will automatically ignore the finding.
Learn more
Semgrep Assistant (Semgrep’s AI integration) now supports GitLab and GitLab self-managed. Check out the documentation.