Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Support for DVC import dependencies #3662

Closed
sisp opened this issue Feb 21, 2023 · 3 comments
Closed

Support for DVC import dependencies #3662

sisp opened this issue Feb 21, 2023 · 3 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and will be auto-closed.

Comments

@sisp
Copy link

sisp commented Feb 21, 2023

I'd like to be able to generate SBOM for local projects which have data dependencies managed via DVC. DVC is a popular project in the machine learning (ML) community which, among other things, manages data via Git (similar to Git LFS) and supports importing data from other Git repos (similar to Git submodules) in which case a .dvc file with a dependency entry is created. The main use case for data imports is the decoupling of data (typically ML datasets for training and testing) and ML projects (ML algorithms trained and tested on datasets) by managing data in data registries and importing them in ML projects. The data in these data registries should have a license under whose terms it may be used and, thus, it would be beneficial to include this information in the SBOM.

Would you be open to receiving a contribution to Trivy (and the go-dep-parser library) that adds support for .dvc files with dependency entries?

@sisp sisp added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 21, 2023
@nejch
Copy link

nejch commented Feb 21, 2023

This is somewhat related to #3067 and all the related draft PRs, feel free to chime in there @sisp :)

@sisp
Copy link
Author

sisp commented Feb 21, 2023

Thanks, @nejch! 👍

@github-actions
Copy link

This issue is stale because it has been labeled with inactivity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and will be auto-closed. label Apr 23, 2023
@aquasecurity aquasecurity locked and limited conversation to collaborators May 8, 2023
@knqyf263 knqyf263 converted this issue into discussion #4232 May 8, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

2 participants