Skip to main content

GitHub Actions - Changelog

The following table lists the features and changes that have been implemented for GitHub Actions with the relevant version release.

Checkmarx One Version

CLI Version

Improvements

Bug Fixes

2.0.18

2.0.44

  • You can now designate a scan as a "Private Package" and assign a package version to it using the addtional_params options. Once a private package has been scanned, info about the risks affecting that package will be identified by SCA when that package version is used in any of your projects. You can download an article about private packages here.

  • We added the --exploitable-path flag to the additional_params options. This enables you to designate whether or not Exploitable Path will run on this particular scan. When used, this overrides the designation made in the project settings.

    We also added a flag --sca-last-sast-scan-time, which enables you to specify the number of days that SAST scan results are considered valid for use in Exploitable Path (i.e., if there is no current SAST scan, how many days prior to the current SCA scan will Checkmarx One look for a SAST scan to use for analyzing Exploitable Path.)

    Warning

    The --sca-last-sast-scan-time flag is not yet fully supported and may not function as designed.

  • Improved memory usage when uploading zip files.

  • Added file extensions go.mod, go.sum, *.dart, and *.plist to the list of included files (when creating the zip archive for scanning).

2.0.17

2.0.42

  • The scan results summary is now shown in the build summary section on the build page.

  • Added option to generate reports in PDF format by setting --report-format to pdf. For PDF format reports, you can add the following additional flags:

    • Add the --report-pdf-email flag to specify email recipients.

    • Add the --report-pdf-options flag to specify which sections to include in the report. Options are: Iac-Security, Sast,Sca, ScanSummary, ExecutiveSummary, ScanResults.

2.0.16

2.0.41

General improvements and bug fixes.

2.0.15

2.0.40

  • Added option to generate reports in PDF format.

2.0.14

2.0.39

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

  • Fixed issue that the Checkmarx GitHub action had been using an API that was deprecated by GitHub.

2.0.13

2.0.37

  • The KICS scanner is now referred to in Checkmarx One as "IaC Security". All mentions of the scanner and the vulnerabilities identified by it, now refer to IaC Security.

  • The API Security scanner is now supported for use via the CLI. When running the scan create command, you can now add api_security to the list of scanners under --scan-types.

2.0.12

2.0.34

  • The scan ID is now given as an output of the step, so that it can be used to obtain data from the scan for use in subsequent steps.

2.0.11

2.0.29

  • General improvements and bug fixes

2.0.10

2.0.28

  • General improvements and bug fixes

2.0.10

2.0.28

  • General improvements and bug fixes

2.0.9

2.0.27

  • Added a Job Summary with the scan ID to the GitHub Action.

  • The comments for pull requests are now decorated with results from Checkmarx One scans that were triggered by that pull request. The comments show a list of new vulnerabilities introduced by the code change as well as the vulnerabilities that were fixed.

  • All documentation links now point to the new Checkmarx documentation portal at https://checkmarx.com/resource/documentation.

 

2.0.8

2.0.23

  • General improvements and bug fixes

2.0.7

2.0.20

  • General improvements and bug fixes

2.0.6

2.0.19

  • General improvements and bug fixes

2.0.5

2.0.18

  • You can now add filters to the scan create command (to exclude files/folders from the scan) separately for each specific scanner. The flags for the new filters are: --sast-filter <string>, --kics-filter <string>, --sca-filter <string>. See scan create.

    Tip

    The existing flag --file-filter , which sets filters for the entire scan (for all scanners) is still in use.

  • You can now add an ssh key to a scan, using the flag --ssh-key <string> with the path to the ssh private key.

Fixed issue that the branch specified in the settings was not overriding the pull request branch. The pull request branch is now used as the default when no branch is specified.

2.0.4

2.0.16

General improvements and bug fixes

2.0.3

2.0.13

  • Added new --sca-resolver-params flag to the scan create command. See documentation here.

  • The branch name is now shown correctly for Pull requests.

2.0.2

2.0.12

  • In the scan create command, we renamed the format flag as scan-info-format.

  • Renamed the results command as results show command.

  • Fixed a problem with proxy connections.

  • An error is now generated when project name is empty.

2.0.1

2.0.10

  • Added SummaryJSON reports.

  • Added the --scan-timeout <int> flag to the scan create command, enabling users to specify a time limit after which the scan will fail and terminate. See documentation here.

  • Updated UI elements to reflect the new Checkmarx branding (e.g., logo).

2.0.0

2.0.9

  • Added ability to break builds by specifying a threshold for acceptable vulnerabilities.

  • Added support for exporting scan results directly to SonarQube or SonarCloud console. See documentation here.

2.0.29

2.0.4

  • Updated CLI to version 2.0.4

  • Added branch parameter (required)

2.0.19

  • Added tenant support to CLI

  • Added tenant support to Github action and Jenkins

2.0.18

  • Added tenant support.

  • Updated the sources parameter:

    • Removed archive_source and source _directory.

    • Support only -s option

  • Fixed bug with additional parameters and spaces.

  • Fixed Preset – Not mandatory anymore.

2.0.17

  • Updated documentation:

    • Using scan_types instead of project_types

2.0.15

  • Supports SAST Scans.

  • Defines required and non-required parameters.

  • Provide examples for demos.

In this section: