Skip to main content

Semgrep release notes for December 2023

🔧 OSS Engine​

🌐 Cloud Platform​

Added​

  • Semgrep IDE integrations now cache information about the current repository so that it doesn't traverse the entire repository on every scan to determine if the files are valid targets for scanning; this improves scan times.
  • Users can now ignore findings locally in Semgrep IDE extensions. The changes persist between restarts, though they're not reported back to Semgrep Cloud Platform and don't affect the remote repository or other users. Note that these findings are still detected when Semgrep scans your code, typically when opening a pull request or merge request.
  • The metrics collected now include more granular information to help differentiate scans using different engine capabilities, such as intraprocedural scans without secrets validation versus intraprocedural scans with secrets validation.
  • CLI tool: Added new semgrep test subcommand, which is an alias for semgrep scan --test. Note: If the name of the directory you are scanning is test, use semgrep scan test to avoid confusion with the new semgrep test subcommand.

Changed​

  • OCaml: Switched to a tree-sitter-based parser instead of the Menhir parser.
  • Rust: Updated the parser used for Rust.

Fixed​

  • Fixed an issue where webhooks stopped working.
  • Fixed an issue so that clicking Start Tour now restarts the Getting Started tutorial.
  • Fixed an issue where the Members page doesn't display a user's new role until the page reloads.
  • Fixed an issue where users switching organizations would result in a 404.
  • Fixed the Connect to button under Settings > Source Code Managers so that it displays correctly based on whether the user can connect to a source code manager.
  • CLI tool: Updated CLI error message to clarify that users should log in before running either:
    • semgrep ci
    • semgrep scan --config

💻 Code​

Fixed​

  • Fixed an issue where Semgrep Code findings marked as fixed can be triaged through the rule group. Once a finding is fixed, its triage status can't be changed back to ignored.
  • Fixed an issue where the rule information card and the rule preview are missing for older findings; all findings now display this information.
  • Fixed an issue where the finding's severity displayed doesn't match the rule's severity once the rule has been updated.

⛓️ Semgrep Supply Chain​

Changed​

  • Fixed an issue where empty tables in pyproject.toml files would fail to parse.

🤖 Assistant (beta)​

Added​

  • Added the Analyze button to Semgrep Cloud Platform's Code page, which triggers all Assistant functions on selected findings, including autofix, autotriage, and component tagging. After Assistant performs these functions, users can see their results if they filter for findings based on Recommendation or by Component. Additionally, users who choose No Grouping instead of Group by Rule see false positive and true positive recommendations when viewing their finding details pages.

🔐 Secrets (beta)​

Added​

  • Added support for custom validator rules, which can be written using Semgrep's Rules Editor and run using semgrep ci --allow-untrusted-validators. Note that custom validator rules are private and can't be shared to Semgrep Registry.

Fixed​

  • Fixed an issue where the Ignore button doesn't work when triaging Secrets.

📝 Documentation and knowledge base​

Added​

Changed​

  • Updated overview articles for Semgrep Code and Semgrep Supply Chain.
  • Updated documentation on setting up pull request or merge request comments for GitHub, GitLab, and Bitbucket users.
  • General improvements to API docs, including clarification of usage instructions for Supply Chain and Secrets endpoints.

Fixed​

  • Minor corrections and updates to various articles.

Not finding what you need in this doc? Ask questions in our Community Slack group, or see Support for other ways to get help.