veracode/Veracode Static Analysis Pipeline Scan and SARIF import

Initiate a Veracode Static Analysis Pipeline Scan and convert the results file to a valid SARIF file

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
scan-typeThe scan type for which a SARIF report needs to be generated can be either a pipeline scan or a policy scanyespipeline
results-jsonThe location of the JSON result file for the policy or pipelineyesfiltered_results.json
pipeline-results-jsonlocation of the pipeline json result fileyesresults.json
output-results-sarifthe path to the SARIF file as an output of the transformationyesveracode-results.sarif
source-base-path-1a path prefix conversion before publish in the SARIF fileno""
source-base-path-2a path prefix conversion before publish in the SARIF fileno""
source-base-path-3a path prefix conversion before publish in the SARIF fileno""
finding-rule-levelThe conversion rule of Veracode findings to GitHub levelyes4:3:0
repo_ownerThe account owner of the repository. The name is not case sensitive.no
repo_nameThe name of the repository without the .git extension. The name is not case sensitive.no
githubTokenGitHub token is a secure token that allows the workflow to interact with the GitHub API and perform actions on behalf of the repository or useryes${{ github.token }}
refThe full Git referenceyes${{ github.ref }}
commitSHAThe SHA of the commit to which the analysis you are uploading relates.yes${{ github.sha }}
nouploadDo not upload the SARIF file to the GitHub repositorynofalse

no outputs