Repository navigation
Hello, Keycloak!
#40036
Replies: 1 comment
|
Moving the discussion from #40685 (comment) to here. @Anchels it sounds like you intend to open issues on a continual basis. I was wondering is there a possibility of someone providing a prototype with maven or github action integration so that we can evaluate how costly / intrusive it would be to perform analysis on per build or per commit basis? |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
We are a team of security development enthusiasts (Linux Verification Center) and we are currently analyzing Keycloak using the Svace static analyzer. We plan to open issues for the alerts that our team has marked as "Confirmed" and in need of correction. For the majority of these issues, we intend to provide pull requests with proposed fixes. However, we very much welcome any additional contributions or assistance from the community to help address these findings more efficiently. In this regard, we would like to create an "epic issue" based on our findings for better tracking and easier access for any volunteers who wish to contribute.
Best regards,
Mikhail Titov
titov.ma@npc-ksb.ru
All reactions