Skip to main content

December 2022

Semgrep Supply Chain

Additions

  • Semgrep Supply chain now supports PR or MR comments within GitHub and GitLab repositories. This feature is enabled by default and sends comments to both GitHub and GitLab users when Semgrep Supply Chain detects reachable vulnerabilities.
  • Improved load time for the Supply Chain > Vulnerabilities page for users with many vulnerabilities.
  • Vulnerabilities are now automatically marked as fixed if a semgrep ci scan detects that the lockfile or reachable usages were fixed.
  • Vulnerability cards (records that appear in Supply Chain > Vulnerabilities) now link to the source rule or advisory that detected the vulnerability. To view the source rule from the record, click the </> icon: Screenshot of the source rule option

Changes

  • Fixing a vulnerability’s reachable usages now causes the original vulnerability card to be marked as fixed, and a separate card will appear for unreachable usages which can be triaged separately.
  • Improved responsiveness of search bars within Supply Chain > Vulnerabilities and Supply Chain > Advisories.

Semgrep App

Additions

On the Findings page, you can now filter by rule category and rule confidence level.

Semgrep CLI

These release notes include upgrades for versions ranging between 1.0.0 and 1.2.1.

Additions

  • JSON output: Added a max_memory_bytes field to the output of the semgrep --json --time which corresponds to the amount of memory allocated during the OCaml phase of Semgrep. This is useful for telemetry purposes.
  • DeepSemgrep: If you have a Team tier account in Semgrep App, and you enable the DeepSemgrep setting, then semgrep ci automatically runs the DeepSemgrep engine instead of the regular Semgrep CLI engine on full scans (but not in PR scans). See the DeepSemgrep documentation for installation details.

Changes

  • Semgrep CLI does not print a summary of blocking rules unless it is invoked with semgrep ci subcommand. (Issue #6651)

Documentation updates

Additions

Changes