-
Notifications
You must be signed in to change notification settings - Fork 27
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
Add MSCA RoslynAnalyzers for C# #29
Comments
I wanted to let you know that we collaborated with the Roslyn team who implemented a fork of this solution to create a dotnet/code-analysis action: For the github/ossar-action, it is backed by the Microsoft Security Code Analysis CLI which does have Roslyn Analyzers available today. This is what's being leveraged by dotnet's action. To leverage Roslyn Analyzers within OSSAR today,
We know this is a lot of overhead to get Roslyn to run today in w/ OSSAR. Dotnet's solution runs the same code with a better UX from a workflow itself, although with the same parameters configured in a gdnconfig file. Either way, a configuration with these values will be checked into the repository, and it will still run through the MSCA CLI. We are also working on a feature right now to run Roslyn Analyzers automatically, which would allow it to be added to the policy. Unlike other source and artifact based static analysis tools, the difficulty of Roslyn Analyzers is that they are compile time and requiring rerunning the build with the injected analyzers. Due to the complexity, it will always be a best effort but may get added to the default GitHub policy in the near future. Thanks, |
Hi @davidknise , Correct me if I am wrong. As per your comment, my understanding is that the OSSAR action does support the Roslyn analysers, and can be configured as per the given steps to configure the same. While trying to configure the Roslyn analysers, I am stuck at running the |
Add support for https://secdevtools.azurewebsites.net/helpRoslynAnalyzers.html
The text was updated successfully, but these errors were encountered: