Add check for vulnerable NuGet packages #158
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
Replaced vulnerable NuGet packages check with a custom command to list vulnerable packages and log the output.
Updated the workflow to check for vulnerable NuGet packages with improved logging and output handling.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request adds a security check step to the
.github/workflows/dotnet-core.ymlworkflow to automatically scan for vulnerable NuGet packages during the CI process.Security improvements:
elmahio/github-check-vulnerable-nuget-packages-action@v2to check for vulnerable NuGet packages before building the project in the CI workflow (.github/workflows/dotnet-core.yml).