Skip to main content

May 2023

Release notes from May until June 9

These release notes include updates made by Semgrep, Inc. from May 2023 until June 9. Due to the importance of the launch week at the beginning of June 2023, we decided to include the most important updates from the launch also on the release notes page that you are now reading.

Semgrep tiers

  • Semgrep’s Community Tier has been sunsetted. Existing and new users now have access to all Semgrep Team tier features for free, subject to usage limits.

Semgrep Cloud Platform

  • Semgrep Playground Turbo mode is now in beta. This new mode enables users to create rules using the Semgrep OSS engine which will automatically run upon detecting any change in the rule or sample code. There is no need to click a Run button in Turbo mode.
  • Semgrep Zero-config Scanning for is now in beta. Onboard or add many repositories to the Semgrep Cloud Platform without having to commit a CI file for every repository! Reach out to to try it out.
  • Role-based access control (RBAC) is now available to all Team tier users, subject to usage limits.
  • Single Sign-On (SSO) is now available to all Team tier users, subject to usage limits.
  • Improved the UI on the Settings page.

Semgrep OSS Engine

This section of release notes includes upgrades of Semgrep OSS Engine for versions ranging between 1.21.0 and 1.26.0.

  • Kotlin language support update: Kotlin now upgraded from beta support to full GA support! Additionally, as a part of this update for Kotlin:

    • Added named ellipses, as $...X.
    • Added literal metavariables, from patterns like "$FOO". You can still match strings that only contain a single interpolated ident by using the brace notation, e.g. "${FOO}".
    • Interpolated identifiers in strings, such as $foo, are now properly able to match explicitly interpolated expressions, such as ${...}.
  • Added experimental support for the programming language Cairo 1.0. Thanks to Frostweeds (Romain Jufer) for his contribution!

  • Added experimental support for the programming language Julia.

  • Java support improvement: Semgrep OSS Engine now includes heuristics based on the Java standard library and common naming patterns. As a result, Semgrep OSS Engine can now determine more types of Java expressions, for use with Typed Metavariables.

  • We are introducing a new experimental generic matching engine Aliengrep as an alternative to the default generic mode engine (Spacegrep). Generic mode is used for languages that are not supported by Semgrep OSS Engine. Try out Aliengrep and let us know what you think about it!

  • Taint analysis updates:

    • In Java, Semgrep OSS Engine can now track taint through more get and set methods (getters and setters). Before this update, taint analysis of Semgrep OSS Engine could already relate setters to getters (for example: o.setX(taint); o.getX(). With this update, it can relate setters and getters to properties (for example o.setX(taint); o.x).
    • Added experimental options taint_assume_safe_booleans and taint_assume_safe_numbers to avoid propagating taint that comes from expressions with boolean or number (integer, float) types.
    • Semgrep OSS Engine can recognize that an object constructed by new Obj("tainted", "safe") has its x attribute tainted, whereas its y attribute is safe.
    • Extract mode: users can now choose to include or exclude rules to run on, similar to paths:. For example, to only run the rules on example-1 and example-2:
      - id: test-rule
      mode: extract
      - example-1
      - example-2

      To run the rule on everything except example-1 and example-2:
      - id: test-rule
      mode: extract
      - example-1
      - example-2

      (GitHub issue #7858)
  • Semgrep OSS Engine Language Server updates. The following two updates are also related to Semgrep Visual Studio Code extension:

    • Support for search and replace with rule patterns through semgrep/search.
    • Language Server now notifies you about errors and includes a reason for the crash.
  • Relaxed restrictions on symbolic propagation so that symbolic values survive branching statements. Now (with symbolic-propagation enabled) foo(bar()) matches the following code:

    def test():
    x = bar()
    if cond:

The Semgrep OSS Engine section of release notes mentions only selected additions and changes, for specific bug fixes, see Semgrep OSS Engine GitHub changelog and search for Fixed sections under each version.

Semgrep Supply Chain

  • Semgrep Supply Chain’s License compliance feature is now in beta. This feature enables developers to view the licenses of dependencies in all repositories that are scanned by Semgrep Supply Chain. Read the documentation: License compliance.
    • This feature also enables security engineers to Block, leave a Comment, or Allow dependencies when a PR introducing the dependency is first opened, based on the license of the dependency.
    • License compliance supports many popular Copyleft, Weak-copyleft, and Permissive licenses. Other licenses can also be detected. Screenshot of Semgrep Supply Chain Dependencies tab with licenses listed
  • Semgrep Supply Chain is now available for free to Team tier users, subject to usage limits.
  • Improvements to Semgrep Supply Chain Dependencies page.

Semgrep Visual Studio Code

Semgrep Visual Studio Code extension received new updates! Try to scan your code using the extension and let us know what we can improve. See more in Semgrep Visual Studio Code extension documentation. This extension allows you to check your code for vulnerabilities within seconds, with every line of code changed in the editor. The extension is built on Language Server Protocol, so you can hack it for other editors of your choice. The extension also has a dedicated changelog on GitHub so you can always see the latest updates.

Semgrep Code

  • There is a new Policies page that is going to replace the Rule board in Semgrep Code! Switch to the new version by clicking Try new version in the Rule board header. The new page gives the rule overview a noticeable facelift and many optimizations, you can now easily filter for various types of rule metadata, and specific types of rules and make bulk edits which would have been hardly achievable with the old Rule board. Read more in Policies documentation.

    Screenshot of the default state of the Policies page

  • You can now rename Projects in the Semgrep Cloud Platform. Before this update, when you renamed a repository in your Source Code Manager (SCM), for example in GitHub, GitLab, or Bitbucket, all of your previous Semgrep findings and triage data were lost as Semgrep recognized the renamed repository only as a new repository. With this update, you can now manually rename the project in Semgrep Code. This is the first step before we will bring you an automated solution (as this update still requires manual action). But now you can rename a project in Semgrep Code to match the new repository name without losing your findings data! To rename a repository:

    1. On the Projects page of Semgrep Cloud Platform, click the gear icon Settings. of the repository where you want to change the repository name. Screenshot of the settings icon on Projects page
    2. Click the three dots …, and then click Rename project. Screenshot of the three dots options menu on Projects page
    3. Create a name that matches the name in your SCM, and then click Rename.

Pro rules

Recently released rules bring a total of:

  • 61 Pro rules for Kotlin (with support frameworks like Spring and Ktor)
  • 69 Pro rules for Go (with support frameworks such as Gin, Gorilla, gRPC, net/HTTP, and more)

These rules are available through the Semgrep Registry, in rulesets such as p/default and p/comment, as well as language-specific rulesets such as p/kotlin and p/golang. In total, there are now more than 500 Pro rules available.

Semgrep Pro Engine

  • Semgrep Pro Engine now provides cross-function support for Go and Kotlin!
  • Semgrep Pro Engine allows you to visualize the flow of tainted data (dataflow traces) in Semgrep Code. With this update, you can also receive findings with the visualized flow of tainted data in a pull request (PR) or merge request (MR) Semgrep comments. For more information, see the following documentation:
  • Taint analysis:
    • Taint labels now mostly work cross-function (interprocedural) analysis, except for labeled propagators. Note that taint labels are experimental!
    • Taint analysis now supports cross-function (interprocedural) field sensitivity for JavaScript and TypeScript. For example:
      class Obj {
      constructor(x, y) {
      this.x = x;
      this.y = y;
    • Semgrep Pro Engine taint analysis can now perform field-sensitive analysis of class constructors in Java. For example, if the default constructor of a class C sets its field x to a tainted value, given o = new C(), Semgrep knows that o.getX() is tainted.

Documentation updates