forked from kserve/kserve
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Setup SNYK scan on Upstream repos #43
Labels
kind/security
Indicates that this is a security issue that should be addressed
Comments
On 3rd August we had a discussion with Prod Sec regarding enabling SNYK scan on Upstream repo. |
heyselbi
added
the
kind/security
Indicates that this is a security issue that should be addressed
label
Aug 22, 2023
Jooho
pushed a commit
to Jooho/kserve
that referenced
this issue
Jan 11, 2024
Update makefile to remove DTYPE_STR as it's no longer needed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently SNYK is configured to scan red-hat-data-services org repos but move the security vulnerability fix from upstream to downstream would take long time. So it would be great if we could create new organisation within SNYK, which scan upstream repos so that developer could quickly check the results of their fixes.
following below link to follow this thread :
https://redhat-internal.slack.com/archives/C03UA0RLSQM/p1690524608072849
The text was updated successfully, but these errors were encountered: