Skip to content
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

Utilize package mapping to source additional information #845

Open
thompson-tomo opened this issue Jan 28, 2024 · 1 comment
Open

Utilize package mapping to source additional information #845

thompson-tomo opened this issue Jan 28, 2024 · 1 comment
Labels
enhancement New feature or request stale

Comments

@thompson-tomo
Copy link

thompson-tomo commented Jan 28, 2024

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.

@github-actions github-actions bot added the triage Don't know what to do with this yet label Jan 28, 2024
@mtsfoni mtsfoni added enhancement New feature or request and removed triage Don't know what to do with this yet labels Jan 29, 2024
Copy link

github-actions bot commented May 5, 2024

This issue is stale because it has been open for 3 months with no activity.

@github-actions github-actions bot added the stale label May 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale
Projects
None yet
Development

No branches or pull requests

2 participants