We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
.config/depscan/*.toml
--config-dir
The text was updated successfully, but these errors were encountered:
@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?
Sorry, something went wrong.
No branches or pull requests
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.The text was updated successfully, but these errors were encountered: