Ensure cataloging execution path does not hide potential results
Open
bug
- Dominant language
- Go
- Stars
- 9.6k
- Forks
- 954
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 42
Description
We've adjusted the java cataloger to prefer adding warnings over stopping execution mid-cataloging in order to maximize the number of artifacts found (https://github.com/anchore/syft/pull/348), we should continue this trend and take a close look at the remaining analyzer modules to ensure they follow suit.
Contributor guide
Research direction
Start by reviewing the linked Java cataloger change in PR #348, then inspect the remaining analyzer modules and their cataloging error paths. Done means analyzers add warnings and continue cataloging where possible instead of stopping execution, while maximizing the artifacts found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100