Skip to main content

Visual Studio Extension - Changelog

The following table lists of improvements and bug fixes have been implemented for the Visual Studio plugin with the relevant version release.

Notice

See full documentation of this plugin here.

Plugin Version

CLI Version

Improvements

Bug Fixes

2.0.9

2.0.41

  • All references to AST have been changed to use the new product name "Checkmarx One".

  • Fixed problem with automatically opening the relevant files when clicking on an attack vector.

2.0.8

2.0.32

  • We have simplified the integration procedure for IDE plugins. It is no longer required to enter the Base URL or Tenant Name of your Checkmarx One account. Now, you just enter your API Key, and we extract all of the relevant account info from that Key.

  • In the Checkmarx AST settings, there is now a field for adding additional params. This can be used to manually submit the base url and tenant name (in case there is a problem extracting them from the API Key) or to add global params such as --debug or --proxy. To learn more about CLI params, see Global Flags.

2.0.7

2.0.21

The installation VSIX file is now signed with a code signing license.

2.0.6

2.0.21

Clicking on a node in the Attack Vector now takes you to the relevant code in the editor window (as expected).

2.0.5

2.0.21

General improvements and bug fixes

2.0.4

2.0.20

General improvements

Fixed issue that the app was crashing when opening an attack vector.

2.0.3

General improvements

2.0.2

  • Added links to the relevant Codebashing lessons.

2.0.1

General improvements

2.0.0

Initial release of the plugin. Enables you to import results from a Checkmarx One scan directly into your VS Code console.

  • Import Checkmarx One scan results

  • Show results from all scan types (SAST, SCA, and KICS)

  • Group results by file, language, severity, and status

  • Navigate from results directly to the vulnerable code in the editor

  • Vulnerable code is highlighted in the editor

In this section: