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

feat: add fields for json and SBOM formats with info that Trivy doesn't support OS #8256

Open
DmitriyLewen opened this issue Jan 20, 2025 · 0 comments · May be fixed by #7378
Open

feat: add fields for json and SBOM formats with info that Trivy doesn't support OS #8256

DmitriyLewen opened this issue Jan 20, 2025 · 0 comments · May be fixed by #7378
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. scan/vulnerability Issues relating to vulnerability scanning target/container-image Issues relating to container image scanning

Comments

@DmitriyLewen
Copy link
Contributor

Description

Trivy has unsupported OSes (e.g. Fedora).
To avoid cases where the user doesn't see a log about this (e.g. when the -q flag is enabled) and to make machine processing easier, we need to add fields for this information:

  • json format (in OS struct)
  • SBOM formats (in properties)

See more in #6971

Discussed in #6971

@DmitriyLewen DmitriyLewen added kind/feature Categorizes issue or PR as related to a new feature. scan/vulnerability Issues relating to vulnerability scanning target/container-image Issues relating to container image scanning labels Jan 20, 2025
@DmitriyLewen DmitriyLewen self-assigned this Jan 20, 2025
@DmitriyLewen DmitriyLewen linked a pull request Jan 20, 2025 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. scan/vulnerability Issues relating to vulnerability scanning target/container-image Issues relating to container image scanning
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant