Labels

• autoready

  Automatically mark PR as ready for review when all checks pass
• backport

  Backport PRs
• dependencies

  Pull requests that update a dependency file
• go

  Pull requests that update go code
• good first issue

  Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
• help wanted

  Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
• kind/breaking

  Categorizes issue or PR as related to breaking compatibility.
• kind/bug

  Categorizes issue or PR as related to a bug.
• kind/cleanup

  Categorizes issue or PR as related to cleaning up code, process, or technical debt.
• kind/deprecation

  Categorizes issue or PR as related to a feature/enhancement marked for deprecation.
• kind/documentation

  Categorizes issue or PR as related to documentation.
• kind/feature

  Categorizes issue or PR as related to a new feature.
• kind/integration

  Categorizes issue or PR as related to a third party integration of Trivy.
• kind/security

  Categorizes issue or PR as related to Trivy's own security or internal vulnerabilities.
• kind/security-advisory

  Categorizes issue or PR as related to security advisories.
• kind/testing

  Categorizes issue or PR as related to a unit/integration test.
• lifecycle/active

  Indicates that an issue or PR is actively being worked on by a contributor.
• lifecycle/frozen

  Indicates that an issue or PR should not be auto-closed due to staleness.
• lifecycle/stale

  Denotes an issue or PR has remained open with no activity and will be auto-closed.
• priority/awaiting-more-evidence

  Lowest priority. Possibly useful, but not yet enough support to actually get it done.
• priority/backlog

  Higher priority than priority/awaiting-more-evidence.
• priority/critical-urgent

  Highest priority. Must be actively worked on as someone's top priority right now.
• priority/important-longterm

  Important over the long term, but may not be staffed and/or may need multiple releases to complete.
• priority/important-soon

  Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
• scan/license

  Issues relating to license scanning
• scan/misconfiguration

  Issues relating to misconfiguration scanning
• scan/sbom

  Issues relating to SBOM
• scan/secret

  Issues relating to secret scanning
• scan/vulnerability

  Issues relating to vulnerability scanning
• target/cloud

  Issues relating to cloud account scanning