Abdullah Fathi
Pautan Muat Turun
Gitlab SAST use analyzer to check source code for any known vulnerabilities
include:
- template: Jobs/SAST.gitlab-ci.yml
#Static Application Security Test (SAST)
sast:
stage: test
artifacts:
paths: [gl-sast-report.json]
reports:
sast: gl-sast-report.json
Transform gl-sast-report.json to HTML file for easiness of viewing and analyse the report
.sast_html: &sast_html
services:
- name: docker:dind
command: ["--tls=false"]
after_script:
- sleep 10
- apk add --update docker openrc
- docker pull pcfens/sast-parser
- alias sast-parser="docker run --rm -v \"$(pwd):/reports\" pcfens/sast-parser"
- sast-parser ${INPUT_JSON} > ${OUTPUT_HTML}
artifacts:
paths:
- ${OUTPUT_HTML}
nodejs-scan-sast:
<<: *sast_html
variables:
DOCKER_DRIVER: overlay2
DOCKER_HOST: tcp://docker:2375/
DOCKER_TLS_CERTDIR: ""
INPUT_JSON: "gl-sast-report.json"
OUTPUT_HTML: "nodejs-scan-sast.html"
Scans your repository to help prevent your secrets from being exposed. Secret Detection scanning works on all text files, regardless of the language or framework used
include:
- template: Jobs/Secret-Detection.gitlab-ci.yml
Your feedback matters
There are no secrets to success. It is the result of preparation, hard work, and learning from failure. - Colin Powell