CycloneDX / CycloneDX/cyclonedx-dotnet

Scope property is always being set to required

Open
#843 8 comments 1 reaction 0 assignees View on GitHub
bug
Dominant language
C#
Stars
294
Forks
123
PR merge metrics
No merged PRs in 30d

Description

In my project I have a number of packagereference which has the privateAssets/excludedAssets property set to **all** yet when I look at the bom which is generated it has the scope property set to required for all components.

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue with a .NET project whose PackageReference uses privateAssets/excludedAssets set to all, then inspect the generated BOM and the handling of those package properties. Done means dependencies with those settings no longer receive an incorrect required scope, with the behavior covered by a regression test.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.