-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gitlab osv-scanner #33
Comments
We currently don't have support for GitLab unfortunately, but we'd be very happy to take contributions! |
OK, I'd love to |
https://docs.gitlab.com/ee/ci/migration/github_actions.html is probably relevant... |
Adding to this: Integrating a security scanner, with results automatically presented in various places in GitLab, means ensuring the output is in a GitLab-specified format. Integrating external security scanners into your DevSecOps workflow blog post provides an example of using a custom Synk and a script to convert the resulting JSON to the GitLab-specified format. You can find the schemas for existing scanners here: Container Scanning Your output will need to adhere to one of these schemas. The docs provide further details on the available Report Fields in these schemas. |
Let me know who I can send a boatload of ☕️🧋to for your help with making this a reality! |
I just posted how to do it in GitLab. I have had osv-scanner running in GitLab for a few months. |
Thank you @H4x0rcr4x for sharing the configuration file! |
@cuixq you're welcome. Here is the updated configuration to enable osv-scanner in GitLab's .gitlab-ci.yml file.
|
If I want to use osv-scanner on gitlab, how do I configure the yml file? Is there a corresponding tool or plug-in that can be installed?
The text was updated successfully, but these errors were encountered: