Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor: Merging go-dep-parser into Trivy #6105

Closed
knqyf263 opened this issue Feb 12, 2024 · 0 comments · Fixed by #6094
Closed

refactor: Merging go-dep-parser into Trivy #6105

knqyf263 opened this issue Feb 12, 2024 · 0 comments · Fixed by #6094
Assignees
Milestone

Comments

@knqyf263
Copy link
Collaborator

Description

The go-dep-parser library was initially developed as a standalone project, separate from Trivy. This design choice was made with several benefits in mind: it aimed to make the library more reusable for other projects, and it was thought that making go-dep-parser independent would facilitate contributions from individuals who use the library without necessarily using Trivy.

However, more than four years have passed, and it has become evident that go-dep-parser is currently used exclusively within Trivy without leveraging the above advantages of being an independent project. On the contrary, integrating go-dep-parser into Trivy could offer similar benefits to those discussed in issue #5626.

Given this context, this proposal suggests integrating go-dep-parser into Trivy. This integration aims to streamline development processes and improve maintenance efficiency. By consolidating our resources, we can enhance the overall functionality and performance of Trivy, ensuring that go-dep-parser contributes more directly to our core objectives.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant