You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I really appreciate this task! Thank you. I think I found the following issue with the example:
The example image shows the value **/*csproj:
Doesn't this mean scan the actual project file as a dependency rather than looking at all of the *.dlls used by the program? When I changed it to check the actual *.dlls, it found some vulnerable dependencies.
The text was updated successfully, but these errors were encountered:
The screenshot is just showing an example how to set the --scan option. Consult the Documentation for the valid options.
Depending on the version of .NET you are using, the .csproj scan may or may not work. In .NET Core, the .csproj files have the list of package references that need to be scanned. The example above is scanning a .NET Core project file format.
Earlier versions use the packages.config file to list the references. Even earlier versions not using the packages.config file need to have the .dll scanned to find the references.
I really appreciate this task! Thank you. I think I found the following issue with the example:
The example image shows the value
**/*csproj
:Doesn't this mean scan the actual project file as a dependency rather than looking at all of the
*.dll
s used by the program? When I changed it to check the actual*.dll
s, it found some vulnerable dependencies.The text was updated successfully, but these errors were encountered: