Use `go mod graph` to resolve dependency information for go source
Open
- Dominant language
- Go
- Stars
- 9.6k
- Forks
- 954
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 42
Description
This issue has no description.
Contributor guide
Research direction
Start by tracing Syft's Go-source dependency resolution entry point and compare its current dependency information with the output of `go mod graph`. Confirm the expected behavior and identify the relevant tests before changing anything; done means Go source dependencies are resolved through the module graph.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100