Difference between revisions of "GitLab Dependency Scanning"
Jump to navigation
Jump to search
m (Welcome moved page Dependency Scanning (GitLab) to GitLab Dependency Scanning) |
|||
| Line 5: | Line 5: | ||
== See also == | == See also == | ||
| − | * {{GitLab Auto | + | * {{GitLab Auto DevOps}} |
* {{GitLab}} | * {{GitLab}} | ||
* {{SCA}} | * {{SCA}} | ||
[[Category:GitLab]] | [[Category:GitLab]] | ||
Latest revision as of 04:57, 17 August 2022
- With GitLab 12.7, you can now install a custom version of
pipin Dependency Scanning by using the DS_PIP_VERSION variable. When this is set, it will be passed down to the Dependency Scanning analyzers.
See also[edit]
- GitLab Auto DevOps, GitLab Auto DAST
- GitLab: Install GitLab, Upgrade GitLab Gitlab runner (changelog),
gitlab.rb, .gitlab/, gitlab-ci.yml,gitlab-ctl, gitlab-rake, gitlab-backup, gitlab-rails, GitLab editions, GitLab Security Dashboards, GitLab environments, GitLab environment variables, Auto DevOps, permissions, GitLab Pages,gitlab-rails, GitLab scheduled pipelines, GitLab logs, GitLab changelog , GitLab Release CLI, GitLab Omnibus, GitLab Advanced Search, GitLab container registry, GitLab infrastructure registry - Software Composition Analysis (SCA): Flexera, FOSSA, GitLab Ultimate, JFrog Xray, Snyk, Sonatype, Synopsys: Black Duck, Veracode, WhiteHat Security, WhiteSource, Bill of Materials (BOM), Semgrep, Clair
Advertising:
