-
Notifications
You must be signed in to change notification settings - Fork 307
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
feat(report): added Gitlab SAST report #3432
Conversation
Signed-off-by: Felipe Avelar <[email protected]>
Signed-off-by: Felipe Avelar <[email protected]>
Signed-off-by: Felipe Avelar <[email protected]>
Signed-off-by: Felipe Avelar <[email protected]>
Scan submitted to Checkmarx |
11cd48c
to
9fea141
Compare
Signed-off-by: Felipe Avelar <[email protected]>
Signed-off-by: Felipe Avelar <[email protected]>
Signed-off-by: Felipe Avelar <[email protected]>
Signed-off-by: Felipe Avelar <[email protected]>
Signed-off-by: Felipe Avelar <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Hi all, Gitlabber here! This is really exciting to see shipped! Apologies for missing this earlier but we just noticed a couple minor issues here I wanted to follow-up on:
We are also working on deploying a more accessible schema validator to make these integrations more straightforward. It didn't pick up on the first issue but the second is validated correctly. You can currently find it at https://gitlab-org-security-products-secure-schema-validator.34.127.22.151.sslip.io/ until we spin up a more permanent domain. I opened a follow-up PR here to address these two items: #3460. |
Closes #1986
Proposed Changes
glsast
, which will generate a file to be used with Gitlab SAST integrationI submit this contribution under the Apache-2.0 license.