Skip to content

No labels!

There aren’t any labels for this repository quite yet.

autorelease: pending
autorelease: pending
backport
backport
Backport PRs
backport-to-release/v0.54
backport-to-release/v0.54
dependencies
dependencies
Pull requests that update a dependency file
docker
docker
Pull requests that update Docker code
github_actions
github_actions
Pull requests that update GitHub Actions code
go
go
Pull requests that update Go code
good first issue
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
help wanted
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/breaking
kind/breaking
Categorizes issue or PR as related to breaking compatibility.
kind/bug
kind/bug
Categorizes issue or PR as related to a bug.
kind/cleanup
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
kind/deprecation
kind/deprecation
Categorizes issue or PR as related to a feature/enhancement marked for deprecation.
kind/documentation
kind/documentation
Categorizes issue or PR as related to documentation.
kind/feature
kind/feature
Categorizes issue or PR as related to a new feature.
kind/integration
kind/integration
Categorizes issue or PR as related to a third party integration of Trivy.
kind/security
kind/security
Categorizes issue or PR as related to Trivy's own security or internal vulnerabilities.
kind/security-advisory
kind/security-advisory
Categorizes issue or PR as related to security advisories.
kind/testing
kind/testing
Categorizes issue or PR as related to a unit/integration test.
lifecycle/active
lifecycle/active
Indicates that an issue or PR is actively being worked on by a contributor.
lifecycle/frozen
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
lifecycle/stale
lifecycle/stale
Denotes an issue or PR has remained open with no activity and will be auto-closed.
priority/awaiting-more-evidence
priority/awaiting-more-evidence
Lowest priority. Possibly useful, but not yet enough support to actually get it done.
priority/backlog
priority/backlog
Higher priority than priority/awaiting-more-evidence.
priority/critical-urgent
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
priority/important-longterm
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
priority/important-soon
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
scan/license
scan/license
Issues relating to license scanning
scan/misconfiguration
scan/misconfiguration
Issues relating to misconfiguration scanning
scan/sbom
scan/sbom
Issues relating to SBOM