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

Support for suppression #110

Open
prabhu opened this issue Jul 1, 2023 · 1 comment
Open

Support for suppression #110

prabhu opened this issue Jul 1, 2023 · 1 comment

Comments

@prabhu
Copy link
Member

prabhu commented Jul 1, 2023

A tool like dep-scan inevitably produces false positives due to aliasing and SBoM generation lifecycle.

While tools like trivy offer ignore files and rego policies to support advanced filtering, depscan could offer a toml based solution instead.

Regarding file naming and folder structure, it might be wise to adopt dot-config instead of spoiling the root folders of every repo.

https://dot-config.github.io

So suppression lists could be kept under .config/depscan/*.toml with an optional --config-dir to override this directory for integration use cases.

@cerrussell
Copy link
Collaborator

@prabhu Is there a purpose for the depscan folder under .config since dot-config is talking about a .config directory at the repository level?

To clarify the --config-dir option, should this be to not use a suppression list or do you mean an alternative toml path to load?

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

No branches or pull requests

2 participants