We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This issue is a continuation of #842
With the introduction of package source mapping (https://devblogs.microsoft.com/nuget/introducing-package-source-mapping/) it should now be possible for cyclonedx to determine who the supplier of the nuget package is.
The idea is to read the package source mapping and then set the supplier accordingly.
Assumptions Nuget.Config file exists within either the project directory or the solution direction.
The text was updated successfully, but these errors were encountered:
This issue is stale because it has been open for 3 months with no activity.
Sorry, something went wrong.
No branches or pull requests
This issue is a continuation of #842
With the introduction of package source mapping (https://devblogs.microsoft.com/nuget/introducing-package-source-mapping/) it should now be possible for cyclonedx to determine who the supplier of the nuget package is.
The idea is to read the package source mapping and then set the supplier accordingly.
Assumptions
Nuget.Config file exists within either the project directory or the solution direction.
The text was updated successfully, but these errors were encountered: