Triggering a New Scan

Initiating a Scan

New users are entitled to scan each repository up to five times a day. Existing Mend customers have the scan limitations that are set in their account agreement with mend.  

A scan is initiated via a valid GitHub 'push' command. A valid 'push' command meets at least one of the following requirements:

• One of the commits in the 'push' command include added file(s) that have an extension supported by Mend and/or one of the commits in the 'push' command included a removal of file(s) that have an extension supported by mend. Refer to the Mend Languages page in order to find out whether or not a specific language and its extensions are supported. 

• One of the commits in the 'push' command includes a modification in the package manager configuration file(s). This includes any of the following files, as specified here.
  For Go, Python, JavaScript, or Maven projects, when the manifest file (go.mod, Pipfile, package.json, or pom.xml) is changed, the scan will be triggered only if the dependencies section is changed.

Each time a valid GitHub 'push' command is made for a repository, Mend initiates a scan.

NOTE: The GitHub 'push' command may include multiple commits.