microsoft / microsoft/sbom-tool
.NET integration follow-up considerations
Open
Nobody has claimed this yet.
.NET
- Dominant language
- C#
- Stars
- 2.1k
- Forks
- 201
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 1
Description
Here is an issue regarding a recent integration effort into the .NET SDK & providing SBOMs for NuGet packages:
- https://github.com/microsoft/sbom-tool/issues/711
- https://github.com/microsoft/sbom-tool/issues/710
- https://github.com/microsoft/sbom-tool/issues/709
- https://github.com/microsoft/sbom-tool/issues/708
- https://github.com/microsoft/sbom-tool/issues/712
- https://github.com/microsoft/sbom-tool/issues/713
- https://github.com/microsoft/sbom-tool/issues/714
- https://github.com/microsoft/sbom-tool/issues/715
- https://github.com/microsoft/sbom-tool/issues/716
- https://github.com/microsoft/sbom-tool/issues/718
- https://github.com/microsoft/sbom-tool/issues/719
WIP / Done
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the unchecked linked issues 708–712, 715, 716, and 718, then inspect the referenced .NET SDK pull request 43151. The issue does not name files, tests, or a single implementation target; completion would require determining which follow-up items remain and resolving the checklist.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100