microsoft / microsoft/component-detection
Add osv-scanner.toml configuration to verification tests folders
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 553
- Forks
- 135
- Avg merge
- 20h 58m
- Merged PRs (30d)
- 6
Description
For our [OpenSSF Scorecard](https://securityscorecards.dev/viewer/?uri=github.com/microsoft/component-detection), we are consistently flagged for vulnerabilities in code which does not build but are used in our [verification tests](https://github.com/microsoft/component-detection/tree/main/test/Microsoft.ComponentDetection.VerificationTests/resources). Using the documentation at https://google.github.io/osv-scanner/configuration/ we should add exclusions for the detected vulnerabilities.
```[tasklist]
### Tasks
- [ ] cocoapods
- [ ] co
- [ ] conda
- [ ] docker
- [ ] go
- [ ] gradle
- [ ] ivy
- [ ] maven
- [ ] npm
- [ ] nuget
- [ ] pip
- [ ] pnpm
- [ ] poetry
- [ ] ruby
- [ ] rust
- [ ] spd
- [ ] vcpkg
```
Contributor guide
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 in test/Microsoft.ComponentDetection.VerificationTests/resources and review the verification-test folders named in the task list. Read the osv-scanner configuration documentation, identify the vulnerabilities reported for non-building test code, and add osv-scanner.toml exclusions in the relevant folders. Done means the listed ecosystems have appropriate configuration exclusions for the Scorecard findings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, ruby, rust
- Domain
- security, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100