feat(k8s): add support for vulnerability detection (#5268)

Signed-off-by: knqyf263 <knqyf263@gmail.com>
Signed-off-by: chenk <hen.keinan@gmail.com>
Co-authored-by: DmitriyLewen <dmitriy.lewen@smartforce.io>
Co-authored-by: chenk <hen.keinan@gmail.com>

.github/DISCUSSION_TEMPLATE/adopters.yml

@@ -0,0 +1,31 @@
+title: "<company name>"
+labels: ["adopters"]
+body:
+  - type: textarea
+    id: info
+    attributes:
+      label: "[Optional] How do you use Trivy?"
+    validations:
+      required: false
+  - type: checkboxes
+    attributes:
+      label: "[Optional] Which targets are you scanning with Trivy?"
+      options:
+        - label: "Container Image"
+        - label: "Filesystem"
+        - label: "Git Repository"
+        - label: "Virtual Machine Image"
+        - label: "Kubernetes"
+        - label: "AWS"
+        - label: "SBOM"
+    validations:
+      required: false
+  - type: checkboxes
+    attributes:
+      label: "[Optional] What kind of issues are scanning with Trivy?"
+      options:
+        - label: "Software Bill of Materials (SBOM)"
+        - label: "Known vulnerabilities (CVEs)"
+        - label: "IaC issues and misconfigurations"
+        - label: "Sensitive information and secrets"
+        - label: "Software licenses"

.github/DISCUSSION_TEMPLATE/bugs.yml

@@ -121,4 +121,4 @@ body:
   - type: markdown
     attributes:
       value: |
-        We would be happy if you could share how you are using Trivy [here](https://github.com/aquasecurity/trivy/discussions/new?category=show-and-tell).
+        We would be happy if you could share how you are using Trivy [here](https://github.com/aquasecurity/trivy/discussions/new?category=adopters).

.github/DISCUSSION_TEMPLATE/false-detection.yml

@@ -93,4 +93,4 @@ body:
   - type: markdown
     attributes:
       value: |
-        We would be happy if you could share how you are using Trivy [here](https://github.com/aquasecurity/trivy/discussions/new?category=show-and-tell).
+        We would be happy if you could share how you are using Trivy [here](https://github.com/aquasecurity/trivy/discussions/new?category=adopters).

.github/DISCUSSION_TEMPLATE/ideas.yml

@@ -44,4 +44,4 @@ body:
   - type: markdown
     attributes:
       value: |
-        We would be happy if you could share how you are using Trivy [here](https://github.com/aquasecurity/trivy/discussions/new?category=show-and-tell).
+        We would be happy if you could share how you are using Trivy [here](https://github.com/aquasecurity/trivy/discussions/new?category=adopters).

.github/DISCUSSION_TEMPLATE/q-a.yml

@@ -81,4 +81,4 @@ body:
   - type: markdown
     attributes:
       value: |
-        We would be happy if you could share how you are using Trivy [here](https://github.com/aquasecurity/trivy/discussions/new?category=show-and-tell).
+        We would be happy if you could share how you are using Trivy [here](https://github.com/aquasecurity/trivy/discussions/new?category=adopters.

.github/DISCUSSION_TEMPLATE/show-and-tell.yml

@@ -1,53 +0,0 @@
-title: "<company name> "
-labels: ["adopters"]
-body:
-  - type: textarea
-    id: links
-    attributes:
-      label: "Share Links"
-      description: "If you would like to share a link to your project or company, please paste it below 🌐"
-      value: |
-        ...
-    validations:
-      required: false
-  - type: textarea
-    id: logo
-    attributes:
-      label: "Share Logo"
-      description: "If you have a link to your logo, please provide it in the following text-box 🌐"
-      value: |
-        ...
-    validations:
-      required: false
-  - type: checkboxes
-    attributes:
-      label: Please select all the scan targets that you are using
-      options:
-        - label: Container Images
-        - label: Filesystem
-        - label: Git Repository
-        - label: Virtual Machine Images
-        - label: Kubernetes
-        - label: AWS
-    validations:
-      required: false
-  - type: checkboxes
-    attributes:
-      label: Which scanners are you using on those scan targets?
-      options:
-        - label: OS packages and software dependencies in use (SBOM)
-        - label: Known vulnerabilities (CVEs)
-        - label: IaC issues and misconfigurations
-        - label: Sensitive information and secrets
-        - label: Software licenses
-    validations:
-      required: false
-  - type: textarea
-    id: info
-    attributes:
-      label: "Additional Information"
-      description: "Please tell us more about your use case of Trivy -- anything that you would like to share 🎉"
-      value: |
-        ...
-    validations:
-      required: false

.github/workflows/auto-close-issue.yaml

@@ -0,0 +1,46 @@
+name: Auto-close issues
+
+on:
+  issues:
+    types: [opened]
+
+jobs:
+  close_issue:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Close issue if user does not have write or admin permissions
+        uses: actions/github-script@v6
+        with:
+          script: |
+            // Get the issue creator's username
+            const issueCreator = context.payload.issue.user.login;
+            
+            // Check the user's permissions for the repository
+            const repoPermissions = await github.rest.repos.getCollaboratorPermissionLevel({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              username: issueCreator
+            });
+            
+            const permission = repoPermissions.data.permission;
+            
+            // If the user does not have write or admin permissions, leave a comment and close the issue
+            if (permission !== 'write' && permission !== 'admin') {
+              const commentBody = "Please see https://aquasecurity.github.io/trivy/latest/community/contribute/issue/";
+              await github.rest.issues.createComment({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                issue_number: context.payload.issue.number,
+                body: commentBody
+              });
+            
+              await github.rest.issues.update({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                issue_number: context.payload.issue.number,
+                state: 'closed',
+                state_reason: 'not_planned'
+              });
+            
+              console.log(`Issue #${context.payload.issue.number} closed because ${issueCreator} does not have sufficient permissions.`);
+            }

.github/workflows/auto-update-labels.yaml

@@ -0,0 +1,30 @@
+name: Auto-update labels
+on:
+  push:
+    paths:
+      - 'misc/triage/labels.yaml'
+    branches:
+      - main
+
+jobs:
+  deploy:
+    name: Auto-update labels
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout main
+        uses: actions/checkout@v4.1.0
+
+      - name: Set up Go
+        uses: actions/setup-go@v4
+        with:
+          go-version-file: go.mod
+
+      - name: Install aqua tools
+        uses: aquaproj/aqua-installer@v2.1.2
+        with:
+          aqua_version: v1.25.0
+
+      - name: update labels
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: mage label

.github/workflows/canary.yaml

@@ -25,7 +25,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Restore Trivy binaries from cache
-        uses: actions/cache@v3.3.1
+        uses: actions/cache@v3.3.2
         with:
           path: dist/
           key: ${{ runner.os }}-bins-${{github.workflow}}-${{github.sha}}

.github/workflows/check-go-versions.yaml

@@ -0,0 +1,31 @@
+name: Check Go versions of dependencies
+on:
+  pull_request:
+    paths:
+      - 'go.mod'
+  workflow_dispatch:
+
+jobs:
+  check-go-versions:
+    name: Check Go versions of dependencies
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out code into the Go module directory
+        uses: actions/checkout@v4.1.0
+
+      - name: Set up Go
+        uses: actions/setup-go@v4
+        with:
+          go-version: stable
+
+      # This workflow is a workaround before the "old stable" version becomes Go 1.21.
+      # To avoid updating dependencies that require Go 1.21, we use this workflow
+      # Example of wrong update:
+      # https://github.com/aquasecurity/trivy/discussions/5323#discussioncomment-7186321
+      - name: Check that dependencies doesn't require Go 1.21
+        run: |
+          go mod tidy
+          if grep -q "go 1.21" go.mod; then
+            echo "One of new dependencies requires Go '1.21'. Use 'go get go@1.20' to fix this."
+            exit 1
+          fi

.github/workflows/mkdocs-dev.yaml

@@ -12,7 +12,7 @@ jobs:
     runs-on: ubuntu-22.04
     steps:
       - name: Checkout main
-        uses: actions/checkout@v3.5.3
+        uses: actions/checkout@v4.1.0
         with:
           fetch-depth: 0
           persist-credentials: true

.github/workflows/mkdocs-latest.yaml

@@ -14,7 +14,7 @@ jobs:
     runs-on: ubuntu-22.04
     steps:
       - name: Checkout main
-        uses: actions/checkout@v3.5.3
+        uses: actions/checkout@v4.1.0
         with:
           fetch-depth: 0
           persist-credentials: true

.github/workflows/publish-chart.yaml

@@ -22,7 +22,7 @@ jobs:
     runs-on: ubuntu-20.04
     steps:
       - name: Checkout
-        uses: actions/checkout@v3.5.3
+        uses: actions/checkout@v4.1.0
         with:
           fetch-depth: 0
       - name: Install Helm
@@ -55,7 +55,7 @@ jobs:
     runs-on: ubuntu-20.04
     steps:
       - name: Checkout
-        uses: actions/checkout@v3.5.3
+        uses: actions/checkout@v4.1.0
         with:
           fetch-depth: 0
       - name: Install chart-releaser

.github/workflows/release.yaml

@@ -19,12 +19,12 @@ jobs:
     runs-on: ubuntu-22.04
     steps:
       - name: Checkout code
-        uses: actions/checkout@v3.5.3
+        uses: actions/checkout@v4.1.0
         with:
           fetch-depth: 0
 
       - name: Restore Trivy binaries from cache
-        uses: actions/cache@v3.3.1
+        uses: actions/cache@v3.3.2
         with:
           path: dist/
           key: ${{ runner.os }}-bins-${{github.workflow}}-${{github.sha}}
@@ -35,7 +35,7 @@ jobs:
           sudo apt-get -y install rpm reprepro createrepo-c distro-info
 
       - name: Checkout trivy-repo
-        uses: actions/checkout@v3.5.3
+        uses: actions/checkout@v4.1.0
         with:
           repository: ${{ github.repository_owner }}/trivy-repo
           path: trivy-repo

.github/workflows/reusable-release.yaml

@@ -27,7 +27,7 @@ jobs:
       contents: read  # Not required for public repositories, but for clarity
     steps:
       - name: Maximize build space
-        uses: easimon/maximize-build-space@v7
+        uses: easimon/maximize-build-space@v8
         with:
           root-reserve-mb: 35840 # The Go cache (`~/.cache/go-build` and `~/go/pkg`) requires a lot of storage space.
           remove-android: 'true'
@@ -36,40 +36,40 @@ jobs:
           remove-haskell: 'true'
 
       - name: Cosign install
-        uses: sigstore/cosign-installer@a5d81fb6bdbcbb3d239e864d6552820420254494
+        uses: sigstore/cosign-installer@4a861528be5e691840a69536975ada1d4c30349d
 
       - name: Set up QEMU
-        uses: docker/setup-qemu-action@v2
+        uses: docker/setup-qemu-action@v3
 
       - name: Set up Docker Buildx
         id: buildx
-        uses: docker/setup-buildx-action@v2
+        uses: docker/setup-buildx-action@v3
 
       - name: Show available Docker Buildx platforms
         run: echo ${{ steps.buildx.outputs.platforms }}
 
       - name: Login to docker.io registry
-        uses: docker/login-action@v2
+        uses: docker/login-action@v3
         with:
           username: ${{ secrets.DOCKERHUB_USER }}
           password: ${{ secrets.DOCKERHUB_TOKEN }}
 
       - name: Login to ghcr.io registry
-        uses: docker/login-action@v2
+        uses: docker/login-action@v3
         with:
           registry: ghcr.io
           username: ${{ env.GH_USER }}
           password: ${{ secrets.GITHUB_TOKEN }}
 
       - name: Login to ECR
-        uses: docker/login-action@v2
+        uses: docker/login-action@v3
         with:
           registry: public.ecr.aws
           username: ${{ secrets.ECR_ACCESS_KEY_ID }}
           password: ${{ secrets.ECR_SECRET_ACCESS_KEY }}
 
       - name: Checkout code
-        uses: actions/checkout@v3.5.3
+        uses: actions/checkout@v4.1.0
         with:
           fetch-depth: 0
 
@@ -93,7 +93,7 @@ jobs:
       - name: GoReleaser
         uses: goreleaser/goreleaser-action@v4
         with:
-          version: v1.16.2
+          version: v1.20.0
           args: release -f=${{ inputs.goreleaser_config}} ${{ inputs.goreleaser_options}}
         env:
           GITHUB_TOKEN: ${{ secrets.ORG_REPO_TOKEN }}
@@ -121,7 +121,7 @@ jobs:
             public.ecr.aws/aquasecurity/trivy:canary
 
       - name: Cache Trivy binaries
-        uses: actions/cache@v3.3.1
+        uses: actions/cache@v3.3.2
         with:
           path: dist/
           # use 'github.sha' to create a unique cache folder for each run.

.github/workflows/scan.yaml

@@ -10,7 +10,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout code
-        uses: actions/checkout@v3.5.3
+        uses: actions/checkout@v4.1.0
 
       - name: Run Trivy vulnerability scanner and create GitHub issues
         uses: knqyf263/trivy-issue-action@v0.0.5

.github/workflows/semantic-pr.yaml

@@ -73,6 +73,8 @@ jobs:
             c\+\+
             elixir
             dart
+            swift
+            bitnami
 
             os
             lang
@@ -93,6 +95,7 @@ jobs:
             cyclonedx
             spdx
             purl
+            vex
 
             helm
             report

.github/workflows/stale-issues.yaml

@@ -1,4 +1,4 @@
-name: "Stale issues"
+name: "Stale PR's"
 on:
   schedule:
     - cron: '0 0 * * *'
@@ -10,11 +10,10 @@ jobs:
     - uses: actions/stale@v8
       with:
         repo-token: ${{ secrets.GITHUB_TOKEN }}
-        stale-issue-message: 'This issue is stale because it has been labeled with inactivity.'
         stale-pr-message: 'This PR is stale because it has been labeled with inactivity.'
-        exempt-issue-labels: 'lifecycle/frozen,lifecycle/active,priority/critical-urgent,priority/important-soon,priority/important-longterm,priority/backlog,priority/awaiting-more-evidence'
         exempt-pr-labels: 'lifecycle/active'
         stale-pr-label: 'lifecycle/stale'
-        stale-issue-label: 'lifecycle/stale'
         days-before-stale: 60
+        days-before-issue-stale: '-1'
         days-before-close: 20
+        days-before-issue-close: '-1'

.github/workflows/test-docs.yaml

@@ -10,7 +10,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
     - name: Checkout
-      uses: actions/checkout@v3.5.3
+      uses: actions/checkout@v4.1.0
       with:
         fetch-depth: 0
         persist-credentials: true

.github/workflows/test.yaml

@@ -1,14 +1,5 @@
 name: Test
 on:
-  push:
-    branches-ignore:
-      - 'main'
-      - 'gh-readonly-queue/**'
-    paths-ignore:
-      - '**.md'
-      - 'docs/**'
-      - 'mkdocs.yml'
-      - 'LICENSE'
   pull_request:
       paths-ignore:
       - '**.md'
@@ -24,7 +15,7 @@ jobs:
       matrix:
         operating-system: [ubuntu-latest, windows-latest, macos-latest]
     steps:
-      - uses: actions/checkout@v3.5.3
+      - uses: actions/checkout@v4.1.0
 
       - name: Set up Go
         uses: actions/setup-go@v4
@@ -41,13 +32,20 @@ jobs:
         if: matrix.operating-system == 'ubuntu-latest'
 
       - name: Lint
-        uses: golangci/golangci-lint-action@v3.6.0
+        id: lint
+        uses: golangci/golangci-lint-action@v3.7.0
         with:
-          version: v1.52
-          args: --deadline=30m
+          version: v1.54
+          args: --deadline=30m --out-format=line-number
           skip-cache: true # https://github.com/golangci/golangci-lint-action/issues/244#issuecomment-1052197778
         if: matrix.operating-system == 'ubuntu-latest'
 
+      - name: Check if linter failed
+        run: |
+          echo "Linter failed, running 'mage lint:fix' might help to correct some errors"
+          exit 1
+        if: ${{ failure() && steps.lint.conclusion == 'failure' }}
+
       - name: Install tools
         uses: aquaproj/aqua-installer@v2.1.2
         with:
@@ -71,7 +69,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Check out code into the Go module directory
-        uses: actions/checkout@v3.5.3
+        uses: actions/checkout@v4.1.0
 
       - name: Set up Go
         uses: actions/setup-go@v4
@@ -91,7 +89,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Check out code into the Go module directory
-        uses: actions/checkout@v3.5.3
+        uses: actions/checkout@v4.1.0
 
       - name: Set up Go
         uses: actions/setup-go@v4
@@ -111,7 +109,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout
-        uses: actions/checkout@v3.5.3
+        uses: actions/checkout@v4.1.0
 
       - name: Set up Go
         uses: actions/setup-go@v4
@@ -132,8 +130,17 @@ jobs:
     name: VM Integration Test
     runs-on: ubuntu-latest
     steps:
+      - name: Maximize build space
+        uses: easimon/maximize-build-space@v8
+        with:
+          root-reserve-mb: 35840 # The Go cache (`~/.cache/go-build` and `~/go/pkg`) requires a lot of storage space.
+          remove-android: 'true'
+          remove-docker-images: 'true'
+          remove-dotnet: 'true'
+          remove-haskell: 'true'
+
       - name: Checkout
-        uses: actions/checkout@v3.5.3
+        uses: actions/checkout@v4.1.0
 
       - name: Set up Go
         uses: actions/setup-go@v4
@@ -156,8 +163,18 @@ jobs:
     env:
       DOCKER_CLI_EXPERIMENTAL: "enabled"
     steps:
+    - name: Maximize build space
+      uses: easimon/maximize-build-space@v8
+      with:
+        root-reserve-mb: 35840 # The Go cache (`~/.cache/go-build` and `~/go/pkg`) requires a lot of storage space.
+        remove-android: 'true'
+        remove-docker-images: 'true'
+        remove-dotnet: 'true'
+        remove-haskell: 'true'
+      if: matrix.operating-system == 'ubuntu-latest'
+
     - name: Checkout
-      uses: actions/checkout@v3.5.3
+      uses: actions/checkout@v4.1.0
 
     - name: Set up Go
       uses: actions/setup-go@v4
@@ -179,5 +196,5 @@ jobs:
     - name: Run GoReleaser
       uses: goreleaser/goreleaser-action@v4
       with:
-        version: v1.16.2
+        version: v1.20.0
         args: build --snapshot --clean --timeout 90m ${{ steps.goreleaser_id.outputs.id }}

.golangci.yaml

@@ -17,14 +17,54 @@ linters-settings:
     min-occurrences: 3
   misspell:
     locale: US
-  goimports:
-    local-prefixes: github.com/aquasecurity
+    ignore-words:
+      - licence
   gosec:
     excludes:
       - G101
       - G114
       - G204
       - G402
+  gci:
+    sections:
+      - standard
+      - default
+      - prefix(github.com/aquasecurity/)
+      - blank
+      - dot
+  gomodguard:
+    blocked:
+      modules:
+        - github.com/hashicorp/go-version:
+            recommendations:
+              - github.com/aquasecurity/go-version
+            reason: "`aquasecurity/go-version` is designed for our use-cases"
+        - github.com/Masterminds/semver:
+            recommendations:
+              - github.com/aquasecurity/go-version
+            reason: "`aquasecurity/go-version` is designed for our use-cases"
+  gocritic:
+    disabled-checks:
+      - appendAssign
+      - unnamedResult
+      - whyNoLint
+      - indexAlloc
+      - octalLiteral
+      - hugeParam
+      - rangeValCopy
+      - regexpSimplify
+      - sloppyReassign
+      - commentedOutCode
+    enabled-tags:
+      - diagnostic
+      - style
+      - performance
+      - experimental
+      - opinionated
+    settings:
+      ruleguard:
+        failOn: all
+        rules: '${configDir}/misc/lint/rules.go'
 
 linters:
   disable-all: true
@@ -39,14 +79,18 @@ linters:
     - goconst
     - gocyclo
     - gofmt
-    - goimports
     - misspell
+    - bodyclose
+    - gci
+    - gomodguard
+    - tenv
+    - gocritic
 
 run:
-  go: 1.19
+  go: '1.20'
   skip-files:
-    - ".*._mock.go$"
-    - ".*._test.go$"
+    - ".*_mock.go$"
+    - ".*_test.go$"
     - "integration/*"
     - "examples/*"
 

Dockerfile

@@ -1,4 +1,4 @@
-FROM alpine:3.18.2
+FROM alpine:3.18.4
 RUN apk --no-cache add ca-certificates git
 COPY trivy /usr/local/bin/trivy
 COPY contrib/*.tpl contrib/

Dockerfile.canary

@@ -1,4 +1,4 @@
-FROM alpine:3.18.2
+FROM alpine:3.18.4
 RUN apk --no-cache add ca-certificates git
 
 # binaries were created with GoReleaser

Dockerfile.protoc

@@ -1,13 +1,18 @@
-FROM --platform=linux/amd64 golang:1.19
+FROM --platform=linux/amd64 golang:1.20
 
-# Install protoc (cf. http://google.github.io/proto-lens/installing-protoc.html)
+# Set environment variable for protoc
 ENV PROTOC_ZIP=protoc-3.19.4-linux-x86_64.zip
-RUN apt-get update && apt-get install -y unzip
+
+# Install unzip for protoc installation and clean up cache
+RUN apt-get update && apt-get install -y unzip && rm -rf /var/lib/apt/lists/*
+
+# Download and install protoc
 RUN curl --retry 5 -OL https://github.com/protocolbuffers/protobuf/releases/download/v3.19.4/$PROTOC_ZIP \
     && unzip -o $PROTOC_ZIP -d /usr/local bin/protoc \
-    && unzip -o $PROTOC_ZIP -d /usr/local 'include/*' \ 
+    && unzip -o $PROTOC_ZIP -d /usr/local 'include/*' \
     && rm -f $PROTOC_ZIP
 
+# Install Go tools
 RUN go install github.com/twitchtv/twirp/protoc-gen-twirp@v8.1.0
 RUN go install google.golang.org/protobuf/cmd/protoc-gen-go@v1.27.1
 RUN go install github.com/magefile/mage@v1.14.0

README.md

@@ -139,7 +139,7 @@ Please ensure to abide by our [Code of Conduct][code-of-conduct] during all inte
 
 [Installation]:https://aquasecurity.github.io/trivy/latest/getting-started/installation/
 [Ecosystem]: https://aquasecurity.github.io/trivy/latest/ecosystem/
-[Scanning Coverage]: https://aquasecurity.github.io/trivy/latest/getting-started/coverage/
+[Scanning Coverage]: https://aquasecurity.github.io/trivy/latest/docs/coverage/
 
 [alpine]: https://ariadne.space/2021/06/08/the-vulnerability-remediation-lifecycle-of-alpine-containers/
 [rego]: https://www.openpolicyagent.org/docs/latest/#rego

aqua.yaml

@@ -5,6 +5,6 @@ registries:
 - type: standard
   ref: v3.157.0 # renovate: depName=aquaproj/aqua-registry
 packages:
-- name: tinygo-org/tinygo@v0.27.0
+- name: tinygo-org/tinygo@v0.29.0
 - name: WebAssembly/binaryen@version_112
 - name: magefile/mage@v1.14.0

ci/deploy-deb.sh

@@ -7,12 +7,14 @@ cd trivy-repo/deb
 
 for release in ${DEBIAN_RELEASES[@]} ${UBUNTU_RELEASES[@]}; do
   echo "Removing deb package of $release"
+  reprepro -A i386 remove $release trivy
   reprepro -A amd64 remove $release trivy
   reprepro -A arm64 remove $release trivy
 done
 
 for release in ${DEBIAN_RELEASES[@]} ${UBUNTU_RELEASES[@]}; do
   echo "Adding deb package to $release"
+  reprepro includedeb $release ../../dist/*Linux-32bit.deb
   reprepro includedeb $release ../../dist/*Linux-64bit.deb
   reprepro includedeb $release ../../dist/*Linux-ARM64.deb
 done

cmd/trivy/main.go

@@ -13,10 +13,6 @@ import (
 	_ "modernc.org/sqlite" // sqlite driver for RPM DB and Java DB
 )
 
-var (
-	version = "dev"
-)
-
 func main() {
 	if err := run(); err != nil {
 		log.Fatal(err)
@@ -35,7 +31,7 @@ func run() error {
 		return nil
 	}
 
-	app := commands.NewApp(version)
+	app := commands.NewApp()
 	if err := app.Execute(); err != nil {
 		return err
 	}

contrib/asff.tpl

@@ -91,7 +91,7 @@
             "Severity": {
                 "Label": "{{ $severity }}"
             },
-            "Title": "Trivy found a misconfiguration in {{ $target }}: {{ .Title }}",
+            "Title": "Trivy found a misconfiguration in {{ $target }}: {{ escapeString .Title }}",
             "Description": {{ escapeString $description | printf "%q" }},
             "Remediation": {
                 "Recommendation": {

contrib/html.tpl

@@ -85,7 +85,7 @@
     <h1>{{- escapeXML ( index . 0 ).Target }} - Trivy Report - {{ now }}</h1>
     <table>
     {{- range . }}
-      <tr class="group-header"><th colspan="6">{{ escapeXML .Type }}</th></tr>
+      <tr class="group-header"><th colspan="6">{{ .Type | toString | escapeXML }}</th></tr>
       {{- if (eq (len .Vulnerabilities) 0) }}
       <tr><th colspan="6">No Vulnerabilities found</th></tr>
       {{- else }}
@@ -128,7 +128,7 @@
         <td>{{ escapeXML .ID }}</td>
         <td class="misconf-check">{{ escapeXML .Title }}</td>
         <td class="severity">{{ escapeXML .Severity }}</td>
-        <td class="link" data-more-links="off"  style="white-space:normal;"">
+        <td class="link" data-more-links="off"  style="white-space:normal;">
           {{ escapeXML .Message }}
           <br>
             <a href={{ escapeXML .PrimaryURL | printf "%q" }}>{{ escapeXML .PrimaryURL }}</a>

docs/community/contribute/issue.md

@@ -1,4 +1,7 @@
 # Issues
 Thank you for taking interest in contributing to Trivy!
 
-Trivy uses [GitHub Discussion](./discussion.md) for bug reports, feature requests, and questions.
+Trivy uses [GitHub Discussion](./discussion.md) for bug reports, feature requests, and questions.
+
+!!! warning
+    Issues created by non-maintainers will be immediately closed.

docs/community/contribute/pr.md

@@ -27,7 +27,7 @@ $ ./trivy -h
 You must pass the linter checks:
 
 ```shell
-$ mage lint
+$ mage lint:run
 ```
 
 Additionally, you need to have run `go mod tidy`, so execute the following command as well:
@@ -36,6 +36,11 @@ Additionally, you need to have run `go mod tidy`, so execute the following comma
 $ mage tidy
 ```
 
+To autofix linters use the following command:
+```shell
+$ mage lint:fix
+```
+
 ### Unit tests
 Your PR must pass all the unit tests. You can test it as below.
 

docs/docs/advanced/air-gap.md

@@ -139,4 +139,4 @@ $ trivy conf --skip-policy-update /path/to/conf
 [allowlist]: ../references/troubleshooting.md
 [oras]: https://oras.land/cli/
 
-[^1]: This is only required to scan `jar` files. More information about `Java index db` [here](../scanner/vulnerability/language/java.md)
+[^1]: This is only required to scan `jar` files. More information about `Java index db` [here](../coverage/language/java.md)

docs/docs/advanced/private-registries/acr.md

@@ -12,16 +12,16 @@ export SP_DATA=$(az ad sp create-for-rbac --name TrivyTest --role AcrPull --scop
 # Usage
 ```bash
 # must set TRIVY_USERNAME empty char
-export AZURE_CLIENT_ID$(echo $SP_DATA | jq -r .appId)
-export AZURE_CLIENT_SECRET$(echo $SP_DATA | jq -r .password)
-export AZURE_TENANT_ID$(echo $SP_DATA | jq -r .tenant)
+export AZURE_CLIENT_ID=$(echo $SP_DATA | jq -r '.appId')
+export AZURE_CLIENT_SECRET=$(echo $SP_DATA | jq -r '.password')
+export AZURE_TENANT_ID=$(echo $SP_DATA | jq -r '.tenant')
 ```
 
 # Testing
 You can test credentials in the following manner.
 
 ```bash
-docker run -it --rm -v /tmp:/tmp\
-  -e AZURE_CLIENT_ID=${AZURE_CLIENT_ID} -e AZURE_CLIENT_SECRET=${AZURE_CLIENT_SECRET} \
-  -e AZURE_TENANT_ID=${AZURE_TENANT_ID} aquasec/trivy image your_special_project.azurecr.io/your_special_image:your_special_tag
+docker run -it --rm -v /tmp:/tmp \
+  -e AZURE_CLIENT_ID -e AZURE_CLIENT_SECRET -e AZURE_TENANT_ID \
+  aquasec/trivy image your_special_project.azurecr.io/your_special_image:your_special_tag
 ```

docs/docs/configuration/db.md

@@ -8,7 +8,7 @@
 |     License      |           |
 
 The vulnerability database and the Java index database are needed only for vulnerability scanning.
-See [here](../scanner/vulnerability/index.md) for the detail.
+See [here](../scanner/vulnerability.md) for the detail.
 
 ## Vulnerability Database
 
@@ -64,6 +64,9 @@ Downloading the Java index DB from an external OCI registry can be done by using
 $ trivy image --java-db-repository registry.gitlab.com/gitlab-org/security-products/dependencies/trivy-java-db --download-java-db-only
 ```
 
+!!! Note
+    In [Client/Server](../references/modes/client-server.md) mode, `Java index DB` is currently only used on the `client` side.
+
 ## Remove DBs
 The `--reset` flag removes all caches and databases.
 

docs/docs/configuration/filtering.md

@@ -68,7 +68,7 @@ Total: 527 (UNKNOWN: 0, LOW: 276, MEDIUM: 83, HIGH: 158, CRITICAL: 10)
 
 !!! tip
     To skip all unfixed vulnerabilities, you can use the `--ignore-unfixed` flag .
-    It is a shorthand of `-ignore-status affected,will_not_fix,fix_deferred,end_of_life`.
+    It is a shorthand of `--ignore-status affected,will_not_fix,fix_deferred,end_of_life`.
     It displays "fixed" vulnerabilities only.
 
 ```bash
@@ -204,6 +204,10 @@ See https://avd.aquasec.com/misconfig/avd-aws-0081
 
 ## By Finding IDs
 
+Trivy supports the [.trivyignore](#trivyignore) and [.trivyignore.yaml](#trivyignoreyaml) ignore files.
+
+### .trivyignore
+
 |     Scanner      | Supported |
 |:----------------:|:---------:|
 |  Vulnerability   |     ✓     |
@@ -211,7 +215,6 @@ See https://avd.aquasec.com/misconfig/avd-aws-0081
 |      Secret      |     ✓     |
 |     License      |           |
 
-Use `.trivyignore`.
 
 ```bash
 $ cat .trivyignore
@@ -251,6 +254,92 @@ Total: 0 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 0, CRITICAL: 0)
 
 </details>
 
+### .trivyignore.yaml
+
+|     Scanner      | Supported |
+|:----------------:|:---------:|
+|  Vulnerability   |     ✓     |
+| Misconfiguration |     ✓     |
+|      Secret      |     ✓     |
+|     License      |     ✓     |
+
+!!! warning "EXPERIMENTAL"
+    This feature might change without preserving backwards compatibility.
+
+When the extension of the specified ignore file is either `.yml` or `.yaml`, Trivy will load the file as YAML.
+For the `.trivyignore.yaml` file, you can set ignored IDs separately for `vulnerabilities`, `misconfigurations`, `secrets`, or `licenses`[^1].
+
+Available fields:
+
+| Field      | Required | Type                | Description                                                                                                |
+|------------|:--------:|---------------------|------------------------------------------------------------------------------------------------------------|
+| id         |    ✓     | string              | The identifier of the vulnerability, misconfiguration, secret, or license[^1].                             |
+| paths      |          | string array        | The list of file paths to be ignored. If `paths` is not set, the ignore finding is applied to all files.   |
+| expired_at |          | date (`yyyy-mm-dd`) | The expiration date of the ignore finding. If `expired_at` is not set, the ignore finding is always valid. |
+| statement  |          | string              | The reason for ignoring the finding. (This field is not used for filtering.)                               |
+
+```bash
+$ cat .trivyignore.yaml
+vulnerabilities:
+  - id: CVE-2022-40897
+    paths:
+      - "usr/local/lib/python3.9/site-packages/setuptools-58.1.0.dist-info/METADATA"
+    statement: Accept the risk
+  - id: CVE-2023-2650
+  - id: CVE-2023-3446
+  - id: CVE-2023-3817
+  - id: CVE-2023-29491
+    expired_at: 2023-09-01
+
+misconfigurations:
+  - id: AVD-DS-0001
+  - id: AVD-DS-0002
+    paths:
+      - "docs/Dockerfile"
+    statement: The image needs root privileges
+
+secrets:
+  - id: aws-access-key-id
+  - id: aws-secret-access-key
+    paths:
+      - "foo/bar/aws.secret"
+
+licenses:
+  - id: GPL-3.0 # License name is used as ID
+    paths:
+      - "usr/share/gcc/python/libstdcxx/v6/__init__.py"
+```
+
+Since this feature is experimental, you must explicitly specify the YAML file path using the `--ignorefile` flag.
+Once this functionality is stable, the YAML file will be loaded automatically.
+
+```bash
+$ trivy image --ignorefile ./.trivyignore.yaml python:3.9.16-alpine3.16
+```
+
+<details>
+<summary>Result</summary>
+
+```bash
+2023-08-31T11:10:27.155+0600	INFO	Vulnerability scanning is enabled
+2023-08-31T11:10:27.155+0600	INFO	Secret scanning is enabled
+2023-08-31T11:10:27.155+0600	INFO	If your scanning is slow, please try '--scanners vuln' to disable secret scanning
+2023-08-31T11:10:27.155+0600	INFO	Please see also https://aquasecurity.github.io/trivy/dev/docs/scanner/secret/#recommendation for faster secret detection
+2023-08-31T11:10:29.164+0600	INFO	Detected OS: alpine
+2023-08-31T11:10:29.164+0600	INFO	Detecting Alpine vulnerabilities...
+2023-08-31T11:10:29.169+0600	INFO	Number of language-specific files: 1
+2023-08-31T11:10:29.170+0600	INFO	Detecting python-pkg vulnerabilities...
+
+python:3.9.16-alpine3.16 (alpine 3.16.5)
+========================================
+Total: 0 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 0, CRITICAL: 0)
+
+
+```
+
+</details>
+
+
 ## By Vulnerability Target
 |     Scanner      | Supported |
 |:----------------:|:---------:|
@@ -425,3 +514,5 @@ resource "google_container_cluster" "one_off_test" {
   location = var.region
 }
 ```
+
+[^1]: license name is used as id for `.trivyignore.yaml` files

docs/docs/configuration/reporting.md

@@ -8,6 +8,7 @@ Trivy supports the following formats:
 - [SARIF](https://docs.github.com/en/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning)
 - Template
 - SBOM
+- GitHub dependency snapshot
 
 ### Table (Default)
 
@@ -62,6 +63,8 @@ The following packages/languages are currently supported:
     - Modules: go.mod
 - PHP
     - Composer
+- Java
+    - Maven: pom.xml
 
 This tree is the reverse of the npm list command.
 However, if you want to resolve a vulnerability in a particular indirect dependency, the reversed tree is useful to know where that dependency comes from and identify which package you actually need to update.
@@ -246,7 +249,7 @@ $ trivy image -f json -o results.json golang:1.12-alpine
 |  Vulnerability   |     ✓     |
 | Misconfiguration |     ✓     |
 |      Secret      |     ✓     |
-|     License      |           |
+|     License      |     ✓     |
 
 [SARIF][sarif] can be generated with the `--format sarif` flag.
 
@@ -256,6 +259,20 @@ $ trivy image --format sarif -o report.sarif  golang:1.12-alpine
 
 This SARIF file can be uploaded to GitHub code scanning results, and there is a [Trivy GitHub Action][action] for automating this process.
 
+### GitHub dependency snapshot
+Trivy supports the following packages.
+
+- [OS packages][os_packages]
+- [Language-specific packages][language_packages]
+
+[GitHub dependency snapshots][github-sbom] can be generated with the `--format github` flag.
+
+```
+$ trivy image --format github -o report.gsbom alpine
+```
+
+This snapshot file can be [submitted][github-sbom-submit] to your GitHub repository.
+
 ### Template
 
 |     Scanner      | Supported |
@@ -387,3 +404,8 @@ $ trivy convert --format table --severity CRITICAL result.json
 [asff]: ../../tutorials/integrations/aws-security-hub.md
 [sarif]: https://docs.github.com/en/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-results-from-code-scanning
 [sprig]: http://masterminds.github.io/sprig/
+[github-sbom]: https://docs.github.com/en/rest/dependency-graph/dependency-submission?apiVersion=2022-11-28#about-dependency-submissions
+[github-sbom-submit]: https://docs.github.com/en/rest/dependency-graph/dependency-submission?apiVersion=2022-11-28#create-a-snapshot-of-dependencies-for-a-repository
+
+[os_packages]: ../scanner/vulnerability.md#os-packages
+[language_packages]: ../scanner/vulnerability.md#language-specific-packages

docs/docs/coverage/iac/azure-arm.md

@@ -0,0 +1,33 @@
+# Azure ARM Template
+Trivy supports the scanners listed in the table below.
+
+|      Scanner       | Supported |
+| :----------------: | :-------: |
+| [Misconfiguration] |     ✓     |
+|      [Secret]      |     ✓     |
+
+It supports the following configurations:
+
+|    Format    | Supported |
+| :----------: | :-------: |
+| ARM template |     ✓     |
+|    Bicep     |   ✓[^1]   |
+
+To scan Bicep codes, you need to convert them into ARM templates first.
+
+```
+az bicep build -f main.bicep
+or
+bicep build main.bicep
+```
+
+## Misconfiguration
+Trivy recursively searches directories and scans all found Azure ARM templates.
+
+## Secret
+The secret scan is performed on plain text files, with no special treatment for Azure ARM templates.
+
+[Misconfiguration]: ../../scanner/misconfiguration/index.md
+[Secret]: ../../scanner/secret.md
+
+[^1]: Bicep is not natively supported. It needs to be converted into Azure ARM templates.

docs/docs/coverage/iac/cloudformation.md

@@ -0,0 +1,24 @@
+# CloudFormation
+Trivy supports the scanners listed in the table below.
+
+|      Scanner       | Supported |
+| :----------------: | :-------: |
+| [Misconfiguration] |     ✓     |
+|      [Secret]      |     ✓     |
+
+It supports the following formats.
+
+| Format | Supported |
+| :----: | :-------: |
+|  JSON  |     ✓     |
+|  YAML  |     ✓     |
+
+## Misconfiguration
+Trivy recursively searches directories and scans all found CloudFormation files.
+It evaluates properties, functions, and other elements within CloudFormation files to detect misconfigurations.
+
+## Secret
+The secret scan is performed on plain text files, with no special treatment for CloudFormation.
+
+[Misconfiguration]: ../../scanner/misconfiguration/index.md
+[Secret]: ../../scanner/secret.md

docs/docs/coverage/iac/docker.md

@@ -0,0 +1,24 @@
+# Docker
+Trivy supports the scanners listed in the table below.
+
+|      Scanner       | Supported |
+| :----------------: | :-------: |
+| [Misconfiguration] |     ✓     |
+|      [Secret]      |     ✓     |
+
+It supports the following configurations.
+
+|    Config     | Supported |
+| :-----------: | :-------: |
+|  Dockerfile   |     ✓     |
+| Containerfile |     ✓     |
+|    Compose    |     -     |
+
+## Misconfiguration
+Trivy recursively searches directories and scans all found Docker files.
+
+## Secret
+The secret scan is performed on plain text files, with no special treatment for Dockerfile.
+
+[Misconfiguration]: ../../scanner/misconfiguration/index.md
+[Secret]: ../../scanner/secret.md

docs/docs/coverage/iac/helm.md

@@ -0,0 +1,60 @@
+# Helm
+Trivy supports two types of Helm scanning, templates and packaged charts.
+The following scanners are supported.
+
+| Format   | [Misconfiguration] | [Secret] |
+| -------- | :----------------: | :------: |
+| Template |         ✓          |    ✓     |
+| Chart    |         ✓          |    -     |
+
+## Misconfiguration
+Trivy recursively searches directories and scans all found Helm files.
+
+It evaluates variables, functions, and other elements within Helm templates and resolve the chart to Kubernetes manifests then run the Kubernetes checks.
+See [here](../../scanner/misconfiguration/policy/builtin.md) for more details on the built-in policies.
+
+### Value overrides
+There are a number of options for overriding values in Helm charts.
+When override values are passed to the Helm scanner, the values will be used during the Manifest rendering process and will become part of the scanned artifact.
+
+#### Setting inline value overrides
+Overrides can be set inline on the command line
+
+```bash
+trivy conf --helm-set securityContext.runAsUser=0 ./charts/mySql
+```
+
+#### Setting value file overrides
+Overrides can be in a file that has the key=value set.
+
+```yaml
+# Example override file (overrides.yaml)
+
+securityContext:
+  runAsUser: 0
+```
+
+```bash
+trivy conf --helm-values overrides.yaml ./charts/mySql
+``` 
+
+#### Setting value as explicit string
+the `--helm-set-string` is the same as `--helm-set` but explicitly retains the value as a string
+
+```bash
+trivy config --helm-set-string name=false ./infrastructure/tf
+```
+
+#### Setting specific values from files
+Specific override values can come from specific files
+
+```bash
+trivy conf --helm-set-file environment=dev.values.yaml ./charts/mySql
+```
+
+## Secret
+The secret scan is performed on plain text files, with no special treatment for Helm.
+Secret scanning is not conducted on the contents of packaged Charts, such as tar or tar.gz.
+
+[Misconfiguration]: ../../scanner/misconfiguration/index.md
+[Secret]: ../../scanner/secret.md

docs/docs/coverage/iac/index.md

@@ -0,0 +1,21 @@
+# Infrastructure as Code
+
+## Scanner
+Trivy scans Infrastructure as Code (IaC) files for 
+
+- [Misconfigurations][misconf]
+- [Secrets][secret]
+
+## Supported configurations
+
+| Config type                         | File patterns                 |
+| ----------------------------------- | ----------------------------- |
+| [Kubernetes](kubernetes.md)         | *.yml, *.yaml, *.json         |
+| [Docker](docker.md)                 | Dockerfile, Containerfile     |
+| [Terraform](terraform.md)           | *.tf, *.tf.json, *.tfvars,    |
+| [CloudFormation](cloudformation.md) | *.yml, *.yaml, *.json         |
+| [Azure ARM Template](azure-arm.md)  | *.json                        |
+| [Helm](helm.md)                     | *.yaml, *.tpl, *.tar.gz, etc. |
+
+[misconf]: ../../scanner/misconfiguration/index.md
+[secret]: ../../scanner/secret.md

docs/docs/coverage/iac/kubernetes.md

@@ -0,0 +1,31 @@
+# Kubernetes
+Trivy supports the scanners listed in the table below.
+
+|      Scanner       | Supported |
+| :----------------: | :-------: |
+| [Misconfiguration] |     ✓     |
+|      [Secret]      |     ✓     |
+
+In addition to raw YAML and JSON, it supports the following templates:
+
+|    Template     | Supported |
+| :-------------: | :-------: |
+| [Helm](helm.md) |     ✓     |
+|    Kustomize    |   ✓[^1]   |
+
+!!! note
+    Trivy does not support Kustomize overlays, so it scans files defined in the base.
+    Or, you can scan the output of `kustomize build`.
+
+## Misconfiguration
+Trivy recursively searches directories and scans all found Kubernetes files.
+
+## Secret
+The secret scan is performed on plain text files, with no special treatment for Kubernetes.
+This means that Base64 encoded secrets are not scanned, and only secrets written in plain text are detected.
+
+
+[Misconfiguration]: ../../scanner/misconfiguration/index.md
+[Secret]: ../../scanner/secret.md
+
+[^1]: Kustomize is not natively supported.

docs/docs/coverage/iac/terraform.md

@@ -0,0 +1,45 @@
+# Terraform
+Trivy supports the scanners listed in the table below.
+
+|     Scanner      | Supported |
+| :--------------: | :-------: |
+| Misconfiguration |     ✓     |
+|      Secret      |     ✓     |
+
+It supports the following formats:
+
+|  Format   | Supported |
+| :-------: | :-------: |
+|   JSON    |     ✓     |
+|    HCL    |     ✓     |
+| Plan JSON |     ✓     |
+
+Trivy can scan the results of `terraform plan`.
+You can scan by passing the file generated as shown below to Trivy:
+
+```
+$ terraform plan --out tfplan.binary
+$ terraform show -json tfplan.binary > tfplan.json
+```
+
+## Misconfiguration
+Trivy recursively searches directories and scans all found Terraform files.
+It also evaluates variables, imports, and other elements within Terraform files to detect misconfigurations.
+
+### Value Overrides
+You can provide `tf-vars` files to Trivy to override default values specified in the Terraform HCL code.
+
+```bash
+trivy conf --tf-vars dev.terraform.tfvars ./infrastructure/tf
+```
+
+### Exclude Downloaded Terraform Modules
+By default, downloaded modules are also scanned.
+If you don't want to scan modules downloaded into the `.terraform` directory, you can use the `--tf-exclude-downloaded-modules` flag.
+
+```bash
+trivy conf --tf-exclude-downloaded-modules ./configs
+```
+
+## Secret
+The secret scan is performed on plain text files, with no special treatment for Terraform.

docs/docs/coverage/index.md

@@ -0,0 +1,9 @@
+# Scanning Coverage
+Trivy can detect security issues in many different platforms, languages and configuration files.
+This section gives a general overview of that coverage, and can help answer the frequently asked question "Does Trivy support X?".
+For more detailed information about the specific platforms and languages, check the relevant documentation.
+
+- [OS Packages](os/index.md)
+- [Language-specific Packages](language/index.md)
+- [IaC files](iac/index.md)
+- [Kubernetes clusters](./kubernetes.md)

docs/docs/coverage/kubernetes.md

@@ -0,0 +1,22 @@
+# Kubernetes
+
+When scanning a Kubernetes cluster, Trivy differentiates between the following:
+
+1. Cluster infrastructure (e.g api-server, kubelet, addons)
+1. Cluster configuration (e.g Roles, ClusterRoles). 
+1. Application workloads (e.g nginx, postgresql).
+
+Whenever Trivy scans either of these Kubernetes resources, the container image is scanned separately to the Kubernetes resource definition (the YAML manifest) that defines the resource.
+When scanning any of the above, the container image is scanned separately to the Kubernetes resource definition (the YAML manifest) that defines the resource.
+
+Container image is scanned for:
+- Vulnerabilities
+- Misconfigurations
+- Exposed secrets
+
+Kubernetes resource definition is scanned for:
+- Vulnerabilities - partially supported through [KBOM scanning](#KBOM)
+- Misconfigurations
+- Exposed secrets
+
+To learn more, please see the [documentation for Kubernetes scanning](../target/kubernetes.md)

docs/docs/coverage/language/c.md

@@ -0,0 +1,23 @@
+# C/C++
+
+Trivy supports [Conan][conan] C/C++ Package Manager.
+
+The following scanners are supported.
+
+| Package manager | SBOM  | Vulnerability | License |
+| --------------- | :---: | :-----------: | :-----: |
+| Conan           |   ✓   |       ✓       |    -    |
+
+The following table provides an outline of the features Trivy offers.
+
+| Package manager | File           | Transitive dependencies | Dev dependencies | [Dependency graph][dependency-graph] | Position |
+| --------------- | -------------- | :---------------------: | :--------------: | :----------------------------------: | :------: |
+| Conan           | conan.lock[^1] |            ✓            |     Excluded     |                  ✓                   |    ✓     |
+
+## Conan
+In order to detect dependencies, Trivy searches for `conan.lock`[^1].
+
+[conan]: https://docs.conan.io/1/index.html
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies
+
+[^1]: `conan.lock` is default name. To scan a custom filename use [file-patterns](../../configuration/skipping.md#file-patterns)

docs/docs/coverage/language/dart.md

@@ -0,0 +1,26 @@
+# Dart
+
+Trivy supports [Dart][dart].
+
+The following scanners are supported.
+
+| Package manager         | SBOM  | Vulnerability | License |
+|-------------------------| :---: | :-----------: |:-------:|
+| [Dart][dart-repository] |   ✓   |       ✓       |    -    |
+
+The following table provides an outline of the features Trivy offers.
+
+
+| Package manager         | File         | Transitive dependencies | Dev dependencies | [Dependency graph][dependency-graph] | Position |
+|-------------------------|--------------|:-----------------------:|:----------------:|:------------------------------------:|:--------:|
+| [Dart][dart-repository] | pubspec.lock |            ✓            |     Included     |                  -                   |    -     |
+
+## Dart
+In order to detect dependencies, Trivy searches for `pubspec.lock`.
+
+Trivy marks indirect dependencies, but `pubspec.lock` file doesn't have options to separate root and dev transitive dependencies.
+So Trivy includes all dependencies in report.
+
+[dart]: https://dart.dev/
+[dart-repository]: https://pub.dev/
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies

docs/docs/coverage/language/dotnet.md

@@ -0,0 +1,47 @@
+# .NET
+
+Trivy supports `.NET core` and `NuGet` package managers.
+
+The following scanners are supported.
+
+| Artifact  | SBOM | Vulnerability | License |
+|-----------|:----:|:-------------:|:-------:|
+| .Net Core |  ✓   |       ✓       |    -    |
+| NuGet     |  ✓   |       ✓       |    ✓    |
+
+The following table provides an outline of the features Trivy offers.
+
+| Package manager | File               | Transitive dependencies | Dev dependencies | [Dependency graph][dependency-graph] | Position |
+|:---------------:|--------------------|:-----------------------:|:----------------:|:------------------------------------:|:--------:|
+|    .Net Core    | *.deps.json        |            ✓            |     Excluded     |                  -                   |    ✓     |
+|      NuGet      | packages.config    |            ✓            |     Excluded     |                  -                   |    -     |
+|      NuGet      | packages.lock.json |            ✓            |     Included     |                  ✓                   |    ✓     |
+
+## *.deps.json
+Trivy parses `*.deps.json` files. Trivy currently excludes dev dependencies from the report.
+
+## packages.config
+Trivy only finds dependency names and versions from `packages.config` files. To build dependency graph, it is better to use `packages.lock.json` files.
+
+### license detection
+`packages.config` files don't have information about the licenses used.
+Trivy uses [*.nuspec][nuspec] files from [global packages folder][global-packages] to detect licenses.
+!!! note
+    The `licenseUrl` field is [deprecated][license-url]. Trivy doesn't parse this field and only checks the [license] field (license `expression` type only).
+Currently only the default path and `NUGET_PACKAGES` environment variable are supported.
+
+## packages.lock.json
+Don't forgot to [enable][enable-lock] lock files in your project.
+
+!!! tip
+    Please make sure your lock file is up-to-date after modifying dependencies.
+
+### license detection
+Same as [packages.config](#license-detection)
+
+[enable-lock]: https://learn.microsoft.com/en-us/nuget/consume-packages/package-references-in-project-files#enabling-the-lock-file
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies
+[nuspec]: https://learn.microsoft.com/en-us/nuget/reference/nuspec
+[global-packages]: https://learn.microsoft.com/en-us/nuget/consume-packages/managing-the-global-packages-and-cache-folders
+[license]: https://learn.microsoft.com/en-us/nuget/reference/nuspec#license
+[license-url]: https://learn.microsoft.com/en-us/nuget/reference/nuspec#licenseurl

docs/docs/coverage/language/elixir.md

@@ -0,0 +1,27 @@
+# Elixir
+
+Trivy supports [Hex][hex] repository for [Elixir][elixir].
+
+The following scanners are supported.
+
+| Package manager | SBOM  | Vulnerability | License |
+|-----------------| :---: | :-----------: |:-------:|
+| [hex][hex]        |   ✓   |       ✓       |    -    |
+
+The following table provides an outline of the features Trivy offers.
+
+
+| Package manager | File         | Transitive dependencies | Dev dependencies | [Dependency graph][dependency-graph] | Position |
+|-----------------|--------------|:-----------------------:|:----------------:|:------------------------------------:|:--------:|
+| [hex][hex]      | mix.lock[^1] |            ✓            |     Excluded     |                  -                   |    ✓     |
+
+## Hex
+In order to detect dependencies, Trivy searches for `mix.lock`[^1].
+
+[Configure](https://hexdocs.pm/mix/Mix.Project.html#module-configuration) your project to use `mix.lock`[^1] file.
+
+[elixir]: https://elixir-lang.org/
+[hex]: https://hex.pm/
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies
+
+[^1]: `mix.lock` is default name. To scan a custom filename use [file-patterns](../../configuration/skipping.md#file-patterns)

docs/docs/coverage/language/golang.md

@@ -2,12 +2,20 @@
 
 ## Features
 Trivy supports two types of Go scanning, Go Modules and binaries built by Go.
-The following table provides an outline of the features Trivy offers.
 
-| Artifact | Offline[^1] | Dev dependencies | License | Dependency graph |
-|----------|:-----------:|:-----------------|:-------:|:----------------:|
-| Modules  |      ✅      | Include          |  ✅[^2]  |      ✅[^2]       |
-| Binaries |      ✅      | Exclude          |    -    |        -         |
+The following scanners are supported.
+
+| Artifact | SBOM  | Vulnerability | License |
+| -------- | :---: | :-----------: | :-----: |
+| Modules  |   ✓   |       ✓       |  ✓[^2]  |
+| Binaries |   ✓   |       ✓       |    -    |
+
+The table below provides an outline of the features Trivy offers.
+
+| Artifact | Offline[^1] | Dev dependencies | [Dependency graph][dependency-graph] |
+|----------|:-----------:|:-----------------|:----------------------------------:|
+| Modules  |      ✅      | Include          |               ✅[^2]                |
+| Binaries |      ✅      | Exclude          |                 -                  |
 
 !!! note
     Trivy scans only dependencies of the Go project.
@@ -18,7 +26,7 @@ The following table provides an outline of the features Trivy offers.
 Depending on Go versions, the required files are different.
 
 | Version | Required files | Offline |
-|---------|:--------------:|:-------:|
+| ------- | :------------: | :-----: |
 | \>=1.17 |     go.mod     |    ✅    |
 | <1.17   | go.mod, go.sum |    ✅    |
 
@@ -63,5 +71,10 @@ Also, you can scan your local binaries.
 $ trivy fs ./your_binary
 ```
 
+!!! note
+    It doesn't work with UPX-compressed binaries.
+
 [^1]: It doesn't require the Internet access.
-[^2]: Need to download modules to local cache beforehand
+[^2]: Need to download modules to local cache beforehand
+
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies

docs/docs/coverage/language/index.md

@@ -0,0 +1,67 @@
+# Programming Language
+
+Trivy supports programming languages for 
+
+- [SBOM][sbom]
+- [Vulnerabilities][vuln]
+- [Licenses][license]
+
+## Supported languages
+The files analyzed vary depending on the target.
+This is because Trivy primarily categorizes targets into two groups:
+
+- Pre-build
+- Post-build
+
+If the target is a pre-build project, like a code repository, Trivy will analyze files used for building, such as lock files.
+On the other hand, when the target is a post-build artifact, like a container image, Trivy will analyze installed package metadata like `.gemspec`, binary files, and so on.
+
+| Language             | File                                                                                       | Image[^5] | Rootfs[^6] | Filesystem[^7] | Repository[^8] |
+|----------------------|--------------------------------------------------------------------------------------------|:---------:|:----------:|:--------------:|:--------------:|
+| [Ruby](ruby.md)      | Gemfile.lock                                                                               |     -     |     -      |       ✅        |       ✅        |
+|                      | gemspec                                                                                    |     ✅     |     ✅      |       -        |       -        |
+| [Python](python.md)  | Pipfile.lock                                                                               |     -     |     -      |       ✅        |       ✅        |
+|                      | poetry.lock                                                                                |     -     |     -      |       ✅        |       ✅        |
+|                      | requirements.txt                                                                           |     -     |     -      |       ✅        |       ✅        |
+|                      | egg package[^1]                                                                            |     ✅     |     ✅      |       -        |       -        |
+|                      | wheel package[^2]                                                                          |     ✅     |     ✅      |       -        |       -        |
+|                      | conda package[^3]                                                                          |     ✅     |     ✅      |       -        |       -        |
+| [PHP](php.md)        | composer.lock                                                                              |     ✅     |     ✅      |       ✅        |       ✅        |
+| [Node.js](nodejs.md) | package-lock.json                                                                          |     -     |     -      |       ✅        |       ✅        |
+|                      | yarn.lock                                                                                  |     -     |     -      |       ✅        |       ✅        |
+|                      | pnpm-lock.yaml                                                                             |     -     |     -      |       ✅        |       ✅        |
+|                      | package.json                                                                               |     ✅     |     ✅      |       -        |       -        |
+| [.NET](dotnet.md)    | packages.lock.json                                                                         |     ✅     |     ✅      |       ✅        |       ✅        |
+|                      | packages.config                                                                            |     ✅     |     ✅      |       ✅        |       ✅        |
+|                      | .deps.json                                                                                 |     ✅     |     ✅      |       ✅        |       ✅        |
+| [Java](java.md)      | JAR/WAR/PAR/EAR[^4]                                                                        |     ✅     |     ✅      |       -        |       -        |
+|                      | pom.xml                                                                                    |     -     |     -      |       ✅        |       ✅        |
+|                      | *gradle.lockfile                                                                           |     -     |     -      |       ✅        |       ✅        |
+| [Go](golang.md)      | Binaries built by Go                                                                       |     ✅     |     ✅      |       -        |       -        |
+|                      | go.mod                                                                                     |     -     |     -      |       ✅        |       ✅        |
+| [Rust](rust.md)      | Cargo.lock                                                                                 |     ✅     |     ✅      |       ✅        |       ✅        |
+|                      | Binaries built with [cargo-auditable](https://github.com/rust-secure-code/cargo-auditable) |     ✅     |     ✅      |       -        |       -        |
+| [C/C++](c.md)        | conan.lock                                                                                 |     -     |     -      |       ✅        |       ✅        |
+| [Elixir](elixir.md)  | mix.lock[^10]                                                                              |     -     |     -      |       ✅        |       ✅        |
+| [Dart](dart.md)      | pubspec.lock                                                                               |     -     |     -      |       ✅        |       ✅        |
+| [Swift](swift.md)    | Podfile.lock                                                                               |     -     |     -      |       ✅        |       ✅        |
+|                      | Package.resolved                                                                           |     -     |     -      |       ✅        |       ✅        |
+
+The path of these files does not matter.
+
+Example: [Dockerfile](https://github.com/aquasecurity/trivy-ci-test/blob/main/Dockerfile)
+
+[sbom]: ../../supply-chain/sbom.md
+[vuln]: ../../scanner/vulnerability.md
+[license]: ../../scanner/license.md
+
+[^1]: `*.egg-info`, `*.egg-info/PKG-INFO`, `*.egg` and `EGG-INFO/PKG-INFO`
+[^2]: `.dist-info/META-DATA`
+[^3]: `envs/*/conda-meta/*.json`
+[^4]: `*.jar`, `*.war`, `*.par` and `*.ear`
+[^5]: ✅ means "enabled" and `-` means "disabled" in the image scanning
+[^6]: ✅ means "enabled" and `-` means "disabled" in the rootfs scanning
+[^7]: ✅ means "enabled" and `-` means "disabled" in the filesystem scanning
+[^8]: ✅ means "enabled" and `-` means "disabled" in the git repository scanning
+[^9]: ✅ means that Trivy detects line numbers where each dependency is declared in the scanned file. Only supported in [json](../../configuration/reporting.md#json) and [sarif](../../configuration/reporting.md#sarif) formats. SARIF uses `startline == 1 and endline == 1` for unsupported file types
+[^10]: To scan a filename other than the default filename use [file-patterns](../../configuration/skipping.md#file-patterns)

docs/docs/coverage/language/java.md

@@ -1,14 +1,21 @@
 # Java
-
 Trivy supports three types of Java scanning: `JAR/WAR/PAR/EAR`, `pom.xml` and `*gradle.lockfile` files.
+
+Each artifact supports the following scanners:
+
+| Artifact         | SBOM  | Vulnerability | License |
+| ---------------- | :---: | :-----------: | :-----: |
+| JAR/WAR/PAR/EAR  |   ✓   |       ✓       |    -    |
+| pom.xml          |   ✓   |       ✓       |    ✓    |
+| *gradle.lockfile |   ✓   |       ✓       |    -    |
+
 The following table provides an outline of the features Trivy offers.
 
-
-| Artifact         |    Internet access    | Dev dependencies | License |
-|------------------|:---------------------:|:-----------------|:-------:|
-| JAR/WAR/PAR/EAR  |     Trivy Java DB     | Include          |    -    |
-| pom.xml          | Maven repository [^1] | Exclude          |    ✅   |
-| *gradle.lockfile |           -           | Exclude          |     -   |
+| Artifact         |    Internet access    | Dev dependencies | [Dependency graph][dependency-graph] |
+|------------------|:---------------------:|:----------------:|:------------------------------------:|
+| JAR/WAR/PAR/EAR  |     Trivy Java DB     |     Include      |                  -                   |
+| pom.xml          | Maven repository [^1] |     Exclude      |                  ✓                   |
+| *gradle.lockfile |           -           |     Exclude      |                  -                   |
 
 These may be enabled or disabled depending on the target.
 See [here](./index.md) for the detail.
@@ -18,7 +25,7 @@ To find information about your JAR[^2] file, Trivy parses `pom.properties` and `
 
 If those files don't exist or don't contain enough information - Trivy will try to find this JAR[^2] file in [trivy-java-db](https://github.com/aquasecurity/trivy-java-db).
 The Java DB will be automatically downloaded/updated when any JAR[^2] file is found.
-It is stored in [the cache directory](../../../configuration/cache.md#cache-directory).
+It is stored in [the cache directory](../../configuration/cache.md#cache-directory).
 
 !!! warning "EXPERIMENTAL"
     Finding JARs in `trivy-java-db` is an experimental function.
@@ -39,7 +46,7 @@ If your machine doesn't have the necessary files - Trivy tries to find the infor
 
 !!! Note
     Trivy only takes information about packages. We don't take a list of vulnerabilities for packages from the `maven repository`.
-    Information about data sources for Java you can see [here](./index.md#data-sources).
+    Information about data sources for Java you can see [here](../../scanner/vulnerability.md#data-sources_1).
 
 You can disable connecting to the maven repository with the `--offline-scan` flag.
 The `--offline-scan` flag does not affect the Trivy database.
@@ -59,4 +66,6 @@ It doesn't require the internet access.
 [^3]: `ArtifactID`, `GroupID` and `Version`
 [^4]: e.g. when parent pom.xml file has `../pom.xml` path
 [^5]: When you use dependency path in `relativePath` field in pom.xml file
-[^6]: `/Users/<username>/.m2/repository` (for Linux and Mac) and `C:/Users/<username>/.m2/repository` (for Windows) by default
+[^6]: `/Users/<username>/.m2/repository` (for Linux and Mac) and `C:/Users/<username>/.m2/repository` (for Windows) by default
+
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies

docs/docs/coverage/language/nodejs.md

@@ -1,18 +1,27 @@
 # Node.js
 
 Trivy supports three types of Node.js package managers: `npm`, `Yarn` and `pnpm`.
+
+The following scanners are supported.
+
+| Artifact | SBOM  | Vulnerability | License |
+| -------- | :---: | :-----------: | :-----: |
+| npm      |   ✓   |       ✓       |    ✓    |
+| Yarn     |   ✓   |       ✓       |    ✓    |
+| pnpm     |   ✓   |       ✓       |    -    |
+
 The following table provides an outline of the features Trivy offers.
 
-| Package manager | File              | Transitive dependencies | Dev dependencies  | Dependency graph | Position | License |
-|:---------------:|-------------------|:-----------------------:|:-----------------:|:----------------:|:--------:|:-------:|
-|       npm       | package-lock.json |            ✅            | [Excluded](#npm)  |        ✅         |    ✅     |    ✅    |
-|      Yarn       | yarn.lock         |            ✅            | [Excluded](#yarn) |        ✅         |    ✅     |    -    |
-|      pnpm       | pnpm-lock.yaml    |            ✅            |     Excluded      |        ✅         |    -     |    -    |
+| Package manager | File              | Transitive dependencies | Dev dependencies  | [Dependency graph][dependency-graph] | Position |
+|:---------------:|-------------------|:-----------------------:|:-----------------:|:------------------------------------:|:--------:|
+|       npm       | package-lock.json |            ✓            | [Excluded](#npm)  |                  ✓                   |    ✓     |
+|      Yarn       | yarn.lock         |            ✓            | [Excluded](#yarn) |                  ✓                   |    ✓     |
+|      pnpm       | pnpm-lock.yaml    |            ✓            |     Excluded      |                  ✓                   |    -     |
 
 In addition, Trivy scans installed packages with `package.json`.
 
 | File         | Dependency graph | Position | License |
-|--------------|:----------------:|:--------:|:-------:|
+| ------------ | :--------------: | :------: | :-----: |
 | package.json |        -         |    -     |    ✅    |
 
 These may be enabled or disabled depending on the target.
@@ -33,12 +42,13 @@ By default, Trivy doesn't report development dependencies. Use the `--include-de
 
 ### Yarn
 Trivy parses `yarn.lock`, which doesn't contain information about development dependencies.
-To exclude devDependencies, `package.json` also needs to be present next to `yarn.lock`.
+To exclude devDependencies, `package.json` also needs to be present next to `yarn.lock`. 
+Trivy analyzes `.yarn` (Yarn 2+) or `node_modules` (Yarn Classic) folder next to the yarn.lock file to detect licenses.
 
 By default, Trivy doesn't report development dependencies. Use the `--include-dev-deps` flag to include them.
 
 ### pnpm
-Trivy parses `pnpm-lock.yaml`, then finds production dependencies and builds a [tree] of dependencies with vulnerabilities.
+Trivy parses `pnpm-lock.yaml`, then finds production dependencies and builds a [tree][dependency-graph] of dependencies with vulnerabilities.
 
 ## Packages
 Trivy parses the manifest files of installed packages in container image scanning and so on.
@@ -47,5 +57,4 @@ Trivy parses the manifest files of installed packages in container image scannin
 Trivy searches for `package.json` files under `node_modules` and identifies installed packages.
 It only extracts package names, versions and licenses for those packages.
 
-
-[tree]: ../../../configuration/reporting.md#show-origins-of-vulnerable-dependencies 
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies

docs/docs/coverage/language/php.md

@@ -1,12 +1,19 @@
 # PHP
 
 Trivy supports [Composer][composer], which is a tool for dependency management in PHP.
+
+The following scanners are supported.
+
+| Package manager | SBOM  | Vulnerability | License |
+| --------------- | :---: | :-----------: | :-----: |
+| Composer        |   ✓   |       ✓       |    ✓    |
+
 The following table provides an outline of the features Trivy offers.
 
 
-| Package Manager | File          | Transitive dependencies | Dev dependencies | Dependency graph | Position | License |
-|-----------------|---------------|:-----------------------:|:----------------:|:----------------:|:--------:|:-------:|
-| Composer        | composer.lock |            ✅            |     Excluded     |        ✅         |    ✅     |    ✅    |
+| Package manager | File          | Transitive dependencies | Dev dependencies | [Dependency graph][dependency-graph] | Position |
+|-----------------|---------------|:-----------------------:|:----------------:|:------------------------------------:|:--------:|
+| Composer        | composer.lock |            ✓            |     Excluded     |                  ✓                   |    ✓     |
 
 ## Composer
 In order to detect dependencies, Trivy searches for `composer.lock`.
@@ -15,4 +22,5 @@ Trivy also supports dependency trees; however, to display an accurate tree, it n
 Since this information is not included in `composer.lock`, Trivy parses `composer.json`, which should be located next to `composer.lock`.
 If you want to see the dependency tree, please ensure that `composer.json` is present.
 
-[composer]: https://getcomposer.org/
+[composer]: https://getcomposer.org/
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies

docs/docs/coverage/language/python.md

@@ -1,20 +1,37 @@
 # Python
 
 Trivy supports three types of Python package managers: `pip`, `Pipenv` and `Poetry`.
+The following scanners are supported for package managers.
+
+| Package manager | SBOM  | Vulnerability | License |
+| --------------- | :---: | :-----------: | :-----: |
+| pip             |   ✓   |       ✓       |    -    |
+| Pipenv          |   ✓   |       ✓       |    -    |
+| Poetry          |   ✓   |       ✓       |    -    |
+
+In addition, Trivy supports three formats of Python packages: `egg`, `wheel` and `conda`.
+The following scanners are supported for Python packages.
+
+| Packaging | SBOM  | Vulnerability | License |
+| --------- | :---: | :-----------: | :-----: |
+| Egg       |   ✓   |       ✓       |    ✓    |
+| Wheel     |   ✓   |       ✓       |    ✓    |
+| Conda     |   ✓   |       -       |    -    |
+
+
 The following table provides an outline of the features Trivy offers.
 
-| Package manager | File             | Transitive dependencies | Dev dependencies | Dependency graph | Position | License |
-|-----------------|------------------|:-----------------------:|:----------------:|:----------------:|:--------:|:-------:|
-| pip             | requirements.txt |            -            |     Include      |        -         |    -     |    -    |
-| Pipenv          | Pipfile.lock     |            ✅            |     Include      |        -         |    ✅     |    -    |
-| Poetry          | poetry.lock      |            ✅            |     Exclude      |        ✅         |          |    -    |
+| Package manager | File             | Transitive dependencies | Dev dependencies | [Dependency graph][dependency-graph] | Position |
+|-----------------|------------------|:-----------------------:|:----------------:|:------------------------------------:|:--------:|
+| pip             | requirements.txt |            -            |     Include      |                  -                   |    -     |
+| Pipenv          | Pipfile.lock     |            ✓            |     Include      |                  -                   |    ✓     |
+| Poetry          | poetry.lock      |            ✓            |     Exclude      |                  ✓                   |          |
 
-In addition, Trivy supports two formats of Python packages: `egg` and `wheel`.
 
-| Packaging | License |
-|-----------|:-------:|
-| Egg       |    ✅    |
-| Wheel     |    ✅    |
+| Packaging | Dependency graph |
+| --------- | :--------------: |
+| Egg       |        ✓         |
+| Wheel     |        ✓         |
 
 These may be enabled or disabled depending on the target.
 See [here](./index.md) for the detail.
@@ -73,3 +90,5 @@ Trivy looks for `*.egg-info`, `*.egg-info/PKG-INFO`, `*.egg` and `EGG-INFO/PKG-I
 
 ### Wheel
 Trivy looks for `.dist-info/META-DATA` to identify Python packages.
+
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies

docs/docs/coverage/language/ruby.md

@@ -0,0 +1,30 @@
+# Ruby
+
+Trivy supports [Bundler][bundler] and [RubyGems][rubygems].
+The following scanners are supported for Cargo.
+
+| Package manager | SBOM | Vulnerability | License |
+|-----------------|:----:|:-------------:|:-------:|
+| Bundler         |  ✓   |       ✓       |    -    |
+| RubyGems        |  ✓   |       ✓       |    ✓    |
+
+
+The following table provides an outline of the features Trivy offers.
+
+| Package manager | File         | Transitive dependencies | Dev dependencies | [Dependency graph][dependency-graph] | Position |
+|-----------------|--------------|:-----------------------:|:-----------------|:------------------------------------:|:--------:|
+| Bundler         | Gemfile.lock |            ✓            | Included         |                  ✓                   |    ✓     |
+| RubyGems        | .gemspec     |            -            | Included         |                  -                   |    -     |
+
+
+### Bundler
+Trivy searches for `Gemfile.lock` to detect dependencies. 
+
+
+### RubyGems
+`.gemspec` files doesn't contains transitive dependencies. You need to scan each `.gemspec` file separately.
+
+[bundler]: https://bundler.io
+[rubygems]: https://rubygems.org/
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies
+

docs/docs/coverage/language/rust.md

@@ -1,18 +1,29 @@
 # Rust
 
-## Features
 Trivy supports [Cargo](https://doc.rust-lang.org/stable/cargo/), which is the Rust package manager.
-The following table provides an outline of the features Trivy offers.
+The following scanners are supported for Cargo.
 
-| Package manager | File       | Transitive dependencies | Dev dependencies | License | Dependency graph | Position |
-|-----------------|------------|:-----------------------:|:-----------------|:-------:|:----------------:|:--------:|
-| Cargo           | Cargo.lock |            ✅            | Excluded[^1]     |    -    |        ✅         |    ✅     |
+| Package manager | SBOM  | Vulnerability | License |
+| --------------- | :---: | :-----------: | :-----: |
+| Cargo           |   ✓   |       ✓       |    -    |
 
 In addition, it supports binaries built with [cargo-auditable](https://github.com/rust-secure-code/cargo-auditable).
 
-| Artifact | Transitive dependencies | Dev dependencies | License | Dependency graph | Position |
-|----------|:-----------------------:|:-----------------|:-------:|:----------------:|:--------:|
-| Binaries |            ✅            | Excluded         |    -    |        -         |    -     |
+| Artifact | SBOM  | Vulnerability | License |
+| -------- | :---: | :-----------: | :-----: |
+| Binaries |   ✓   |       ✓       |    -    |
+
+## Features
+The following table provides an outline of the features Trivy offers.
+
+| Package manager | File       | Transitive dependencies | Dev dependencies | [Dependency graph][dependency-graph] | Position |
+|-----------------|------------|:-----------------------:|:-----------------|:------------------------------------:|:--------:|
+| Cargo           | Cargo.lock |            ✓            | Excluded[^1]     |                  ✓                   |    ✓     |
+
+
+| Artifact | Transitive dependencies | Dev dependencies | Dependency graph | Position |
+| -------- | :---------------------: | :--------------- | :--------------: | :------: |
+| Binaries |            ✓            | Excluded         |        -         |    -     |
 
 
 ### Cargo
@@ -28,4 +39,6 @@ Scan `Cargo.lock` and `Cargo.toml` together also removes developer dependencies.
 Trivy scans binaries built with [cargo-auditable](https://github.com/rust-secure-code/cargo-auditable).
 If such a binary exists, Trivy will identify it as being built with cargo-audit and scan it.
 
-[^1]: When you scan Cargo.lock and Cargo.toml together.
+[^1]: When you scan Cargo.lock and Cargo.toml together.
+
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies

docs/docs/coverage/language/swift.md

@@ -0,0 +1,44 @@
+# Swift
+
+Trivy supports [CocoaPods][cocoapods] and [Swift][swift] package managers.
+
+The following scanners are supported.
+
+| Package manager | SBOM | Vulnerability | License |
+|-----------------|:----:|:-------------:|:-------:|
+| Swift           |  ✓   |       ✓       |    -    |
+| CocoaPods       |  ✓   |       ✓       |    -    |
+
+The following table provides an outline of the features Trivy offers.
+
+| Package manager | File             | Transitive dependencies | Dev dependencies | [Dependency graph][dependency-graph] | Position |
+|:---------------:|------------------|:-----------------------:|:----------------:|:------------------------------------:|:--------:|
+|      Swift      | Package.resolved |            ✓            |     Included     |                  -                   |    ✓     |
+|    CocoaPods    | Podfile.lock     |            ✓            |     Included     |                  ✓                   |    -     |
+
+These may be enabled or disabled depending on the target.
+See [here](./index.md) for the detail.
+
+## Swift
+Trivy parses [Package.resolved][package-resolved] file to find dependencies.
+Don't forget to update (`swift package update` command) this file before scanning.
+
+## CocoaPods
+CocoaPods uses package names in `PodFile.lock`, but [GitHub Advisory Database (GHSA)][ghsa] Trivy relies on uses Git URLs. 
+We parse [the CocoaPods Specs][cocoapods-specs] to match package names and links.
+
+!!! note "Limitation"
+    Since [GHSA][ghsa] holds only Git URLs, such as github.com/apple/swift-nio, 
+    Trivy can't identify affected submodules, and detect all submodules maintained by the same URL.
+    For example, [SwiftNIOHTTP1][niohttp1] and [SwiftNIOWebSocket][niowebsocket] both are maintained under `github.com/apple/swift-nio`,
+    and Trivy detect CVE-2022-3215 for both of them, even though only [SwiftNIOHTTP1][niohttp1] is actually affected.
+
+[cocoapods]: https://cocoapods.org/
+[cocoapods-specs]: https://github.com/CocoaPods/Specs
+[ghsa]: https://github.com/advisories?query=type%3Areviewed+ecosystem%3Aswift
+[swift]: https://www.swift.org/package-manager/
+[package-resolved]: https://github.com/apple/swift-package-manager/blob/4a42f2519e3f7b8a731c5ed89b47ed577df8f86c/Documentation/Usage.md#resolving-versions-packageresolved-file
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies
+
+[niohttp1]: https://cocoapods.org/pods/SwiftNIOHTTP1
+[niowebsocket]: https://cocoapods.org/pods/SwiftNIOWebSocket

docs/docs/coverage/os/alma.md

@@ -0,0 +1,73 @@
+# AlmaLinux
+Trivy supports the following scanners for OS packages.
+
+|    Scanner    | Supported |
+| :-----------: | :-------: |
+|     SBOM      |     ✓     |
+| Vulnerability |     ✓     |
+|    License    |     ✓     |
+
+Please see [here](index.md#supported-os) for supported versions.
+
+The table below outlines the features offered by Trivy.
+
+|               Feature                | Supported |
+|:------------------------------------:|:---------:|
+|       Unfixed vulnerabilities        |     -     |
+| [Dependency graph][dependency-graph] |     ✓     |
+
+## SBOM
+Trivy detects packages that have been installed through package managers such as `dnf` and `yum`.
+
+## Vulnerability
+AlmaLinux offers its own security advisories, and these are utilized when scanning AlmaLinux for vulnerabilities.
+
+### Data Source
+See [here](../../scanner/vulnerability.md#data-sources).
+
+### Fixed Version
+When looking at fixed versions, it's crucial to consider the patches supplied by AlmaLinux.
+For example, for CVE-2023-0464, the fixed version for AlmaLinux 9 is listed as `3.0.7-16.el9_2` in [their advisory][ALSA-2023:3722].
+Note that this is different from the upstream fixed version, which is `3.0.9`, `3.1.1`, and son on.
+Typically, only the upstream information gets listed on [NVD], so it's important not to get confused.
+
+### Severity
+Trivy calculates the severity of an issue based on the severity provided by AlmaLinux.
+If the severity is not provided or defined yet by AlmaLinux, the severity from the NVD is taken into account.
+
+Using CVE-2023-0464 as an example, while it is rated as "High" in NVD, AlmaLinux has marked as ["moderate"][ALSA-2023:3722].
+As a result, Trivy will display it as "Medium".
+
+The table below is the mapping of AlmaLinux's severity to Trivy's severity levels.
+
+| AlmaLinux |  Trivy   |
+| :-------: | :------: |
+|    Low    |   Low    |
+| Moderate  |  Medium  |
+| Important |   High   |
+| Critical  | Critical |
+
+### Status
+Trivy supports the following [vulnerability statuses] for AlmaLinux.
+
+|       Status        | Supported |
+| :-----------------: | :-------: |
+|        Fixed        |     ✓     |
+|      Affected       |     ✓     |
+| Under Investigation |           |
+|    Will Not Fix     |           |
+|    Fix Deferred     |           |
+|     End of Life     |           |
+
+
+## License
+Trivy identifies licenses by examining the metadata of RPM packages.
+
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies
+
+[errata]: https://errata.almalinux.org/
+
+[ALSA-2023:3722]: https://errata.almalinux.org/9/ALSA-2023-3722.html
+[NVD]: https://nvd.nist.gov/vuln/detail/CVE-2023-0464
+
+[vulnerability statuses]: ../../configuration/filtering.md#by-status

docs/docs/coverage/os/alpine.md

@@ -0,0 +1,59 @@
+# Alpine Linux
+Trivy supports the following scanners for OS packages.
+
+|    Scanner    | Supported |
+| :-----------: | :-------: |
+|     SBOM      |     ✓     |
+| Vulnerability |     ✓     |
+|    License    |     ✓     |
+
+Please see [here](index.md#supported-os) for supported versions.
+
+The table below outlines the features offered by Trivy.
+
+|               Feature                | Supported |
+|:------------------------------------:|:---------:|
+|       Unfixed vulnerabilities        |     -     |
+| [Dependency graph][dependency-graph] |     ✓     |
+
+## SBOM
+Trivy detects packages that have been installed through `apk`.
+
+## Vulnerability
+Alpine Linux offers its own security advisories, and these are utilized when scanning Alpine for vulnerabilities.
+
+### Data Source
+See [here](../../scanner/vulnerability.md#data-sources).
+
+### Fixed Version
+When looking at fixed versions, it's crucial to consider the patches supplied by Alpine.
+For example, for CVE-2023-0464, the fixed version for Alpine Linux is listed as `3.1.0-r1` in [the secfixes][CVE-2023-0464].
+Note that this is different from the upstream fixed version, which is `3.1.1`.
+Typically, only the upstream information gets listed on [NVD], so it's important not to get confused.
+
+### Severity
+For Alpine vulnerabilities, the severity is determined using the values set by NVD.
+
+### Status
+Trivy supports the following [vulnerability statuses] for Alpine.
+
+|       Status        | Supported |
+| :-----------------: | :-------: |
+|        Fixed        |     ✓     |
+|      Affected       |     ✓     |
+| Under Investigation |           |
+|    Will Not Fix     |           |
+|    Fix Deferred     |           |
+|     End of Life     |           |
+
+## License
+Trivy identifies licenses by examining the metadata of APK packages.
+
+
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies
+[secdb]: https://secdb.alpinelinux.org/
+
+[CVE-2023-0464]: https://gitlab.alpinelinux.org/alpine/aports/-/blob/dad5b7380ab3be705951ce6fd2d7bba513d6a744/main/openssl/APKBUILD#L36-37
+[NVD]: https://nvd.nist.gov/vuln/detail/CVE-2023-0464
+
+[vulnerability statuses]: ../../configuration/filtering.md#by-status

docs/docs/coverage/os/amazon.md

@@ -0,0 +1,72 @@
+# Amazon Linux
+Trivy supports the following scanners for OS packages.
+
+|    Scanner    | Supported |
+| :-----------: | :-------: |
+|     SBOM      |     ✓     |
+| Vulnerability |     ✓     |
+|    License    |     ✓     |
+
+Please see [here](index.md#supported-os) for supported versions.
+
+The table below outlines the features offered by Trivy.
+
+|               Feature                | Supported |
+|:------------------------------------:|:---------:|
+|       Unfixed vulnerabilities        |     -     |
+| [Dependency graph][dependency-graph] |     ✓     |
+
+## SBOM
+Trivy detects packages that have been installed through package managers such as `dnf` and `yum`.
+
+## Vulnerability
+Amazon Linux offers its own security advisories, and these are utilized when scanning Amazon Linux for vulnerabilities.
+
+### Data Source
+See [here](../../scanner/vulnerability.md#data-sources).
+
+### Fixed Version
+When looking at fixed versions, it's crucial to consider the patches supplied by Amazon.
+For example, for CVE-2023-0464, the fixed version for Amazon Linux 2023 is listed as `3.0.8-1.amzn2023.0.2` in [ALAS2023-2023-181].
+Note that this is different from the upstream fixed version, which is `3.0.9`, `3.1.1`, and so on.
+Typically, only the upstream information gets listed on [NVD], so it's important not to get confused.
+
+### Severity
+Trivy determines vulnerability severity based on the severity metric provided by Amazon.
+For example, the security patch for [CVE-2023-0464] in Amazon Linux 2023 is provided as [ALAS2023-2023-181].
+Its severity is rated as "Medium".
+Thus, even though it's evaluated as "HIGH" in the NVD, Trivy displays it with a severity of "MEDIUM".
+
+The table below is the mapping of Amazon's severity to Trivy's severity levels.
+
+|  Amazon   |  Trivy   |
+| :-------: | :------: |
+|    Low    |   Low    |
+|  Medium   |  Medium  |
+| Important |   High   |
+| Critical  | Critical |
+
+### Status
+Trivy supports the following [vulnerability statuses] for Amazon Linux.
+
+|       Status        | Supported |
+| :-----------------: | :-------: |
+|        Fixed        |     ✓     |
+|      Affected       |     ✓     |
+| Under Investigation |           |
+|    Will Not Fix     |           |
+|    Fix Deferred     |           |
+|     End of Life     |           |
+
+## License
+Trivy identifies licenses by examining the metadata of RPM packages.
+
+
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies
+[center]: https://alas.aws.amazon.com/
+
+[CVE-2023-0464]: https://alas.aws.amazon.com/cve/html/CVE-2023-0464.html
+[ALAS2023-2023-181]: https://alas.aws.amazon.com/AL2023/ALAS-2023-181.html
+[NVD]: https://nvd.nist.gov/vuln/detail/CVE-2023-0464
+
+[vulnerability statuses]: ../../configuration/filtering.md#by-status

docs/docs/coverage/os/bitnami.md

@@ -0,0 +1,63 @@
+# Bitnami Images
+
+!!! warning "EXPERIMENTAL"
+    Scanning results may be inaccurate.
+
+While it is not an OS, this page describes the details of the [container images provided by Bitnami](https://github.com/bitnami/containers).
+Bitnami images are based on [Debian](debian.md).
+Please see [the Debian page](debian.md) for OS packages.
+
+Trivy supports the following scanners for Bitnami packages.
+
+|    Scanner    | Supported |
+| :-----------: | :-------: |
+|     SBOM      |     ✓     |
+| Vulnerability |     ✓     |
+|    License    |     ✓     |
+
+The table below outlines the features offered by Trivy.
+
+|               Feature                | Supported |
+| :----------------------------------: | :-------: |
+|       Unfixed vulnerabilities        |     -     |
+| [Dependency graph][dependency-graph] |     -     |
+
+## SBOM
+Trivy analyzes the SBOM information contained within the container images provided by Bitnami.
+The SBOM files are located at `/opt/bitnami/<component>/.spdx-<component>.spdx`.
+
+## Vulnerability
+Since Bitnami has its [own vulnerability database][vulndb], it uses these for vulnerability detection of applications and packages distributed by Bitnami.
+
+!!! note
+    Trivy does not support vulnerability detection of independently compiled binaries, so even if you scan container images like `nginx:1.15.2`, vulnerabilities in Nginx cannot be detected.
+    This is because main applications like Nginx are [not installed by the package manager](https://github.com/nginxinc/docker-nginx/blob/321a13a966eeff945196ddd31a629dad2aa85eda/mainline/debian/Dockerfile).
+    However, in the case of Bitnami images, since these SBOMs are stored within the image, scanning `bitnami/nginx:1.15.2` allows for the detection of vulnerabilities in Nginx.
+
+### Fixed Version
+Trivy refers to the [Bitnami database][vulndb]. Please note that these may differ from the upstream fixed versions.
+
+### Severity
+Similar to Fixed versions, it follows Bitnami's vulnerability database.
+
+### Status
+Trivy supports the following [vulnerability statuses] for Bitnami packages.
+
+|       Status        | Supported |
+| :-----------------: | :-------: |
+|        Fixed        |     ✓     |
+|      Affected       |     ✓     |
+| Under Investigation |           |
+|    Will Not Fix     |           |
+|    Fix Deferred     |           |
+|     End of Life     |           |
+
+
+
+## License
+If licenses are included in the SBOM distributed by Bitnami, they will be used for scanning.
+
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies
+
+[vulndb]: https://github.com/bitnami/vulndb
+[vulnerability statuses]: ../../configuration/filtering.md#by-status

docs/docs/coverage/os/cbl-mariner.md

@@ -0,0 +1,66 @@
+# CBL-Mariner
+Trivy supports the following scanners for OS packages.
+
+| Version          | SBOM  | Vulnerability | License |
+| ---------------- | :---: | :-----------: | :-----: |
+| 1.0              |   ✔   |       ✔       |    ✔    |
+| 1.0 (Distroless) |   ✔   |       ✔       |         |
+| 2.0              |   ✔   |       ✔       |    ✔    |
+| 2.0 (Distroless) |   ✔   |       ✔       |         |
+
+
+The following table provides an outline of the targets Trivy supports.
+
+| Version | Container image | Virtual machine |     Arch     |
+| ------- | :-------------: | :-------------: | :----------: |
+| 1.0     |        ✔        |        ✔        | amd64, arm64 |
+| 2.0     |        ✔        |        ✔        | amd64, arm64 |
+
+The table below outlines the features offered by Trivy.
+
+|               Feature                | Supported |
+|:------------------------------------:|:---------:|
+|    Detect unfixed vulnerabilities    |     ✓     |
+| [Dependency graph][dependency-graph] |     ✓     |
+
+## SBOM
+Trivy detects packages that have been installed through package managers such as `dnf` and `yum`.
+
+## Vulnerability
+CBL-Mariner offers its own security advisories, and these are utilized when scanning CBL-Mariner for vulnerabilities.
+
+### Data Source
+See [here](../../scanner/vulnerability.md#data-sources).
+
+### Fixed Version
+Trivy takes fixed versions from [CBL-Mariner OVAL][oval].
+
+### Severity
+Trivy calculates the severity of an issue based on the severity provided in [CBL-Mariner OVAL][oval].
+
+### Status
+Trivy supports the following [vulnerability statuses] for CBL-Mariner.
+
+|       Status        | Supported |
+| :-----------------: | :-------: |
+|        Fixed        |     ✓     |
+|      Affected       |     ✓     |
+| Under Investigation |           |
+|    Will Not Fix     |           |
+|    Fix Deferred     |           |
+|     End of Life     |           |
+
+
+## License
+Trivy identifies licenses by examining the metadata of RPM packages.
+
+!!! note
+    License detection is not supported for CBL-Mariner Distroless.
+
+
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies
+[cbl-mariner]: https://github.com/microsoft/CBL-Mariner
+
+[oval]: https://github.com/microsoft/CBL-MarinerVulnerabilityData/
+
+[vulnerability statuses]: ../../configuration/filtering.md#by-status

docs/docs/coverage/os/centos.md

@@ -0,0 +1,38 @@
+# CentOS
+Trivy supports the following scanners for OS packages.
+
+|    Scanner    | Supported |
+| :-----------: | :-------: |
+|     SBOM      |     ✓     |
+| Vulnerability |     ✓     |
+|    License    |     ✓     |
+
+Please see [here](index.md#supported-os) for supported versions.
+
+The table below outlines the features offered by Trivy.
+
+|                Feature                | Supported |
+| :-----------------------------------: | :-------: |
+|        Unfixed vulnerabilities        |     ✓     |
+| [Dependency graph][dependency-graph] |     ✓     |
+
+## SBOM
+Same as [RHEL](rhel.md#sbom).
+
+## Vulnerability
+CentOS does not provide straightforward machine-readable security advisories.
+As a result, Trivy utilizes the security advisories from [Red Hat Enterprise Linux (RHEL)](rhel.md#vulnerability) for detecting vulnerabilities in CentOS.
+This approach might lead to situations where, even though Trivy displays a fixed version, CentOS might not have the patch available yet.
+Since patches released for RHEL often become available in CentOS after some time, it's usually just a matter of waiting.
+
+!!! note
+    The case for CentOS Stream, which is not supported by Trivy, is entirely different from CentOS.
+
+As Trivy relies on Red Hat's advisories, please refer to [Red Hat](rhel.md) for details regarding vulnerability severity and status.
+
+
+## License
+Same as [RHEL](rhel.md#license).
+
+
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies

docs/docs/coverage/os/chainguard.md

@@ -0,0 +1,32 @@
+# Chainguard
+Trivy supports the following scanners for OS packages.
+
+|    Scanner    | Supported |
+| :-----------: | :-------: |
+|     SBOM      |     ✓     |
+| Vulnerability |     ✓     |
+|    License    |     ✓     |
+
+The table below outlines the features offered by Trivy.
+
+|                Feature                | Supported |
+| :-----------------------------------: | :-------: |
+|    Detect unfixed vulnerabilities     |     -     |
+| [Dependency graph][dependency-graph] |     ✓     |
+
+## SBOM
+Same as [Alpine Linux](alpine.md#sbom).
+
+## Vulnerability
+Chainguard offers its own security advisories, and these are utilized when scanning Chainguard for vulnerabilities.
+Everything else is the same as [Alpine Linux](alpine.md#vulnerability).
+
+### Data Source
+See [here](../../scanner/vulnerability.md#data-sources).
+
+## License
+Same as [Alpine Linux](alpine.md#license).
+
+
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies
+[secdb]: https://packages.cgr.dev/chainguard/security.json

docs/docs/coverage/os/debian.md

@@ -0,0 +1,74 @@
+# Debian
+Trivy supports the following scanners for OS packages.
+
+|    Scanner    | Supported |
+| :-----------: | :-------: |
+|     SBOM      |     ✓     |
+| Vulnerability |     ✓     |
+|    License    |     ✓     |
+
+Please see [here](index.md#supported-os) for supported versions.
+
+The table below outlines the features offered by Trivy.
+
+|                Feature                | Supported |
+| :-----------------------------------: | :-------: |
+|        Unfixed vulnerabilities        |     ✓     |
+| [Dependency graph][dependency-graph] |     ✓     |
+
+## SBOM
+Trivy detects packages that have been installed through package managers such as `apt` and `dpkg`.
+While there are some exceptions, like Go binaries and JAR files, it's important to note that binaries that have been custom-built using `make` or tools installed via `curl` are generally not detected.
+
+## Vulnerability
+Debian offers its own security advisories, and these are utilized when scanning Debian for vulnerabilities.
+
+### Data Source
+See [here](../../scanner/vulnerability.md#data-sources).
+
+### Fixed Version
+When looking at fixed versions, it's crucial to consider the patches supplied by Debian.
+For example, for CVE-2023-3269, the fixed version for Debian 12 (bookworm) is listed as `6.1.37-1` in [the Security Tracker][CVE-2023-3269].
+This patch is provided in [DSA-5448-1].
+Note that this is different from the upstream fixed version, which is `6.5`.
+Typically, only the upstream information gets listed on [NVD], so it's important not to get confused.
+
+### Severity
+Trivy calculates the severity of an issue based on the 'Urgency' metric found in the Security Tracker.
+If 'Urgency' isn't provided by Debian, the severity from the NVD is taken into account.
+
+Using CVE-2019-15052 as an example, while it is rated as "Critical" in NVD, Debian has marked its "Urgency" as ["Low"][CVE-2019-15052].
+As a result, Trivy will display it as "Low".
+
+### Status
+Trivy supports the following [vulnerability statuses] for Debian.
+
+|       Status        | Supported |
+| :-----------------: | :-------: |
+|        Fixed        |     ✓     |
+|      Affected       |     ✓     |
+| Under Investigation |           |
+|    Will Not Fix     |           |
+|    Fix Deferred     |     ✓     |
+|     End of Life     |     ✓     |
+
+## License
+To identify the license of a package, Trivy checks the copyright file located at `/usr/share/doc/*/copyright`.
+
+However, this method has its limitations as the file isn't machine-readable, leading to situations where the license isn't detected.
+In such scenarios, the `--license-full` flag can be passed.
+It compares the contents of known licenses with the copyright file to discern the license in question.
+Please be aware that using this flag can increase memory usage, so it's disabled by default for efficiency.
+
+
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies
+
+[debian-tracker]: https://security-tracker.debian.org/tracker/
+[debian-oval]: https://www.debian.org/security/oval/
+
+[CVE-2023-3269]: https://security-tracker.debian.org/tracker/CVE-2023-3269
+[CVE-2019-15052]: https://security-tracker.debian.org/tracker/CVE-2019-15052
+[DSA-5448-1]: https://security-tracker.debian.org/tracker/DSA-5448-1
+[NVD]: https://nvd.nist.gov/vuln/detail/CVE-2023-3269
+
+[vulnerability statuses]: ../../configuration/filtering.md#by-status

docs/docs/coverage/os/google-distroless.md

@@ -0,0 +1,34 @@
+# Google Distroless Images
+Trivy supports the following scanners for OS packages.
+
+|    Scanner    | Supported |
+| :-----------: | :-------: |
+|     SBOM      |     ✓     |
+| Vulnerability |     ✓     |
+|    License    |     ✓     |
+
+Please see [here](index.md#supported-os) for supported versions.
+
+The table below outlines the features offered by Trivy.
+
+|               Feature                | Supported |
+| :----------------------------------: | :-------: |
+|       Unfixed vulnerabilities        |     -     |
+| [Dependency graph][dependency-graph] |     ✓     |
+
+## SBOM
+Trivy detects packages pre-installed in distroless images.
+
+## Vulnerability
+Google Distroless is based on [Debian]; see there for details.
+
+## License
+Google Distroless is based on [Debian]; see there for details.
+
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies
+
+[metadata]: https://packages.vmware.com/photon/photon_cve_metadata/
+
+[vulnerability statuses]: ../../configuration/filtering.md#by-status
+
+[Debian]: debian.md

docs/docs/coverage/os/index.md

@@ -0,0 +1,45 @@
+# OS
+
+## Scanner
+Trivy supports operating systems for 
+
+- [SBOM][sbom]
+- [Vulnerabilities][vuln]
+- [Licenses][license]
+
+## Supported OS
+
+| OS                                            | Supported Versions                  | Package Managers |
+|-----------------------------------------------|-------------------------------------|------------------|
+| [Alpine Linux](alpine.md)                     | 2.2 - 2.7, 3.0 - 3.18, edge         | apk              |
+| [Wolfi Linux](wolfi.md)                       | (n/a)                               | apk              |
+| [Chainguard](chainguard.md)                   | (n/a)                               | apk              |
+| [Red Hat Enterprise Linux](rhel.md)           | 6, 7, 8                             | dnf/yum/rpm      |
+| [CentOS](centos.md)[^1]                       | 6, 7, 8                             | dnf/yum/rpm      |
+| [AlmaLinux](alma.md)                          | 8, 9                                | dnf/yum/rpm      |
+| [Rocky Linux](rocky.md)                       | 8, 9                                | dnf/yum/rpm      |
+| [Oracle Linux](oracle.md)                     | 5, 6, 7, 8                          | dnf/yum/rpm      |
+| [CBL-Mariner](cbl-mariner.md)                 | 1.0, 2.0                            | dnf/yum/rpm      |
+| [Amazon Linux](amazon.md)                     | 1, 2, 2023                          | dnf/yum/rpm      |
+| [openSUSE Leap](suse.md)                      | 42, 15                              | zypper/rpm       |
+| [SUSE Enterprise Linux](suse.md)              | 11, 12, 15                          | zypper/rpm       |
+| [Photon OS](photon.md)                        | 1.0, 2.0, 3.0, 4.0                  | tndf/yum/rpm     |
+| [Debian GNU/Linux](debian.md)                 | 7, 8, 9, 10, 11, 12                 | apt/dpkg         |
+| [Ubuntu](ubuntu.md)                           | All versions supported by Canonical | apt/dpkg         |
+
+## Supported container images
+
+| Container image                               | Supported Versions                  | Package Managers |
+|-----------------------------------------------|-------------------------------------|------------------|
+| [Google Distroless](google-distroless.md)[^2] | Any                                 | apt/dpkg         |
+| [Bitnami](bitnami.md)                         | Any                                 | -                |
+
+Each page gives more details.
+
+[^1]: CentOS Stream is not supported 
+[^2]: https://github.com/GoogleContainerTools/distroless
+
+
+[sbom]: ../../supply-chain/sbom.md
+[vuln]: ../../scanner/vulnerability.md
+[license]: ../../scanner/license.md

docs/docs/coverage/os/oracle.md

@@ -0,0 +1,70 @@
+# Oracle Linux
+Trivy supports the following scanners for OS packages.
+
+|    Scanner    | Supported |
+| :-----------: | :-------: |
+|     SBOM      |     ✓     |
+| Vulnerability |     ✓     |
+|    License    |     ✓     |
+
+Please see [here](index.md#supported-os) for supported versions.
+
+The table below outlines the features offered by Trivy.
+
+|                Feature                | Supported |
+| :-----------------------------------: | :-------: |
+|        Unfixed vulnerabilities        |     -     |
+| [Dependency graph][dependency-graph] |     ✓     |
+
+## SBOM
+Trivy detects packages that have been installed through package managers such as `dnf` and `yum`.
+
+## Vulnerability
+Oracle Linux offers its own security advisories, and these are utilized when scanning Oracle Linux for vulnerabilities.
+
+### Data Source
+See [here](../../scanner/vulnerability.md#data-sources).
+
+### Fixed Version
+Trivy takes fixed versions from [Oracle security advisories][alerts].
+
+### Severity
+Trivy determines vulnerability severity based on the severity metric provided in [Oracle security advisories][alerts].
+For example, the security patch for [CVE-2023-0464][CVE-2023-0464] is provided as [ELSA-2023-2645][ELSA-2023-2645].
+Its severity is rated as "MODERATE".
+Thus, even though it's evaluated as "HIGH" in the NVD, Trivy displays it with a severity of "MEDIUM".
+
+The table below is the mapping of Oracle's threat to Trivy's severity levels.
+
+|  Oracle   |  Trivy   |
+| :-------: | :------: |
+|    Low    |   Low    |
+| Moderate  |  Medium  |
+| Important |   High   |
+| Critical  | Critical |
+
+### Status
+Trivy supports the following [vulnerability statuses] for Oracle Linux.
+
+|       Status        | Supported |
+| :-----------------: | :-------: |
+|        Fixed        |     ✓     |
+|      Affected       |     ✓     |
+| Under Investigation |           |
+|    Will Not Fix     |           |
+|    Fix Deferred     |           |
+|     End of Life     |           |
+
+## License
+Trivy identifies licenses by examining the metadata of RPM packages.
+
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies
+
+[oval]: https://linux.oracle.com/security/oval/
+[alerts]: https://www.oracle.com/security-alerts/
+
+[CVE-2023-0464]: https://linux.oracle.com/cve/CVE-2023-0464.html
+[ELSA-2023-2645]: https://linux.oracle.com/errata/ELSA-2023-2645.html
+[NVD]: https://nvd.nist.gov/vuln/detail/CVE-2023-0464
+
+[vulnerability statuses]: ../../configuration/filtering.md#by-status

docs/docs/coverage/os/photon.md

@@ -0,0 +1,54 @@
+# Photon OS
+Trivy supports the following scanners for OS packages.
+
+|    Scanner    | Supported |
+| :-----------: | :-------: |
+|     SBOM      |     ✓     |
+| Vulnerability |     ✓     |
+|    License    |     ✓     |
+
+Please see [here](index.md#supported-os) for supported versions.
+
+The table below outlines the features offered by Trivy.
+
+|               Feature                | Supported |
+|:------------------------------------:|:---------:|
+|       Unfixed vulnerabilities        |     -     |
+| [Dependency graph][dependency-graph] |     ✓     |
+
+## SBOM
+Trivy detects packages that have been installed through package managers such as `tdnf` and `yum`.
+
+## Vulnerability
+Photon OS offers its own security advisories, and these are utilized when scanning Photon OS for vulnerabilities.
+
+### Data Source
+See [here](../../scanner/vulnerability.md#data-sources).
+
+### Fixed Version
+Trivy takes fixed versions from [Photon CVE metadata][metadata].
+
+### Severity
+Trivy determines the severity of vulnerabilities based on the CVSSv3 score provided by Photon OS.
+See [here](../../scanner/vulnerability.md#severity-selection) for the conversion table from CVSS score to severity.
+
+### Status
+Trivy supports the following [vulnerability statuses] for Photon OS.
+
+|       Status        | Supported |
+| :-----------------: | :-------: |
+|        Fixed        |     ✓     |
+|      Affected       |     ✓     |
+| Under Investigation |           |
+|    Will Not Fix     |           |
+|    Fix Deferred     |           |
+|     End of Life     |           |
+
+## License
+Trivy identifies licenses by examining the metadata of RPM packages.
+
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies
+
+[metadata]: https://packages.vmware.com/photon/photon_cve_metadata/
+
+[vulnerability statuses]: ../../configuration/filtering.md#by-status

docs/docs/coverage/os/rhel.md

@@ -0,0 +1,84 @@
+# Red Hat Enterprise Linux
+Trivy supports the following scanners for OS packages.
+
+|    Scanner    | Supported |
+| :-----------: | :-------: |
+|     SBOM      |     ✓     |
+| Vulnerability |     ✓     |
+|    License    |     ✓     |
+
+Please see [here](index.md#supported-os) for supported versions.
+
+The table below outlines the features offered by Trivy.
+
+|               Feature                | Supported |
+| :----------------------------------: | :-------: |
+|       Unfixed vulnerabilities        |     ✓     |
+| [Dependency graph][dependency-graph] |     ✓     |
+
+## SBOM
+Trivy detects packages that have been installed through package managers such as `dnf` and `yum`.
+
+## Vulnerability
+Red Hat offers its own security advisories, and these are utilized when scanning Red Hat Enterprise Linux (RHEL) for vulnerabilities.
+
+### Data Source
+See [here](../../scanner/vulnerability.md#data-sources).
+
+### Fixed Version
+When looking at fixed versions, it's crucial to consider the patches supplied by Red Hat.
+For example, for CVE-2023-0464, the fixed version for RHEL 9 is listed as `3.0.7-16.el9_2` in [their advisory][CVE-2023-0464].
+This patch is provided in [RHSA-2023:3722].
+Note that this is different from the upstream fixed version, which is `3.0.9`, `3.1.1`, and so on.
+Typically, only the upstream information gets listed on [NVD], so it's important not to get confused.
+
+### Severity
+Trivy calculates the severity of a vulnerability based on the 'Impact' metric provided by Red Hat.
+If the impact is not provided or defined yet by Red Hat, the severity from the NVD is taken into account.
+
+Using CVE-2023-0464 as an example, while it is rated as "HIGH" in NVD, Red Hat has marked its 'Impact' as ["Low"][CVE-2023-0464].
+As a result, Trivy will display it as "Low".
+
+The table below is the mapping of Red Hat's impact to Trivy's severity levels.
+
+|  Red Hat  |  Trivy   |
+| :-------: | :------: |
+|    Low    |   Low    |
+| Moderate  |  Medium  |
+| Important |   High   |
+| Critical  | Critical |
+
+### Status
+Trivy supports the following [vulnerability statuses] for RHEL.
+
+|       Status        | Supported |
+| :-----------------: | :-------: |
+|        Fixed        |     ✓     |
+|      Affected       |     ✓     |
+| Under Investigation |     ✓     |
+|    Will Not Fix     |     ✓     |
+|    Fix Deferred     |     ✓     |
+|     End of Life     |     ✓     |
+
+When a vulnerability status is listed as "End of Life", it means a vulnerability with the impact level assigned to this CVE is no longer covered by its current support lifecycle phase.
+The product has been identified to contain the impacted component, but analysis to determine whether it is affected or not by this vulnerability was not performed.
+Red Hat advises that the product should be assumed to be affected.
+Therefore, Trivy detects vulnerabilities with this status as "End of Life".
+
+On the other hand, for those marked "Under Investigation," the impact is unclear as they are still being examined, so Trivy does not detect them. Once the investigation is completed, the status should be updated.
+
+!!! abstract
+    Vulnerabilities with a status of "End of Life", where the presence or absence of impact is unclear, are detected by Trivy. However, those with a status of "Under Investigation" are not detected.
+
+## License
+Trivy identifies licenses by examining the metadata of RPM packages.
+
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies
+[oval]: https://www.redhat.com/security/data/oval/v2/
+[api]: https://www.redhat.com/security/data/metrics/
+
+[CVE-2023-0464]: https://access.redhat.com/security/cve/cve-2023-0464
+[RHSA-2023:3722]: https://access.redhat.com/errata/RHSA-2023:3722
+[NVD]: https://nvd.nist.gov/vuln/detail/CVE-2023-0464
+
+[vulnerability statuses]: ../../configuration/filtering.md#by-status

docs/docs/coverage/os/rocky.md

@@ -0,0 +1,70 @@
+# Rocky Linux
+Trivy supports the following scanners for OS packages.
+
+|    Scanner    | Supported |
+| :-----------: | :-------: |
+|     SBOM      |     ✓     |
+| Vulnerability |     ✓     |
+|    License    |     ✓     |
+
+Please see [here](index.md#supported-os) for supported versions.
+
+The table below outlines the features offered by Trivy.
+
+|               Feature                | Supported |
+|:------------------------------------:|:---------:|
+|       Unfixed vulnerabilities        |     -     |
+| [Dependency graph][dependency-graph] |     ✓     |
+
+## SBOM
+Trivy detects packages that have been installed through package managers such as `dnf` and `yum`.
+
+## Vulnerability
+Rocky Linux offers its own security advisories, and these are utilized when scanning Rocky Linux for vulnerabilities.
+
+### Data Source
+See [here](../../scanner/vulnerability.md#data-sources).
+
+### Fixed Version
+Trivy takes fixed versions from [Rocky Linux Errata][errata], not NVD or somewhere else.
+See [here](../../scanner/vulnerability.md#data-source-selection) for more details.
+
+!!! architectures
+    There are cases when the vulnerability affects packages of not all architectures.
+    For example, vulnerable packages for [CVE-2023-0361](https://errata.rockylinux.org/RLSA-2023:1141) are only `aarch64` packages.
+    
+    Trivy only detects vulnerabilities for packages of your architecture.
+
+### Severity
+Trivy calculates the severity of an issue based on the severity provided in [Rocky Linux Errata][errata].
+
+The table below is the mapping of Rocky Linux's severity to Trivy's severity levels.
+
+| Rocky Linux |  Trivy   |
+| :---------: | :------: |
+|     Low     |   Low    |
+|  Moderate   |  Medium  |
+|  Important  |   High   |
+|  Critical   | Critical |
+
+### Status
+Trivy supports the following [vulnerability statuses] for Rocky Linux.
+
+|       Status        | Supported |
+| :-----------------: | :-------: |
+|        Fixed        |     ✓     |
+|      Affected       |     ✓     |
+| Under Investigation |           |
+|    Will Not Fix     |           |
+|    Fix Deferred     |           |
+|     End of Life     |           |
+
+
+## License
+Trivy identifies licenses by examining the metadata of RPM packages.
+
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies
+[updateinfo]: https://download.rockylinux.org/pub/rocky/
+[errata]: https://errata.rockylinux.org/
+
+[vulnerability statuses]: ../../configuration/filtering.md#by-status

docs/docs/coverage/os/suse.md

@@ -0,0 +1,40 @@
+# SUSE
+Trivy supports the following distributions:
+
+- openSUSE Leap
+- SUSE Enterprise Linux (SLE)
+
+Please see [here](index.md#supported-os) for supported versions.
+
+Trivy supports these scanners for OS packages.
+
+|    Scanner    | Supported |
+| :-----------: | :-------: |
+|     SBOM      |     ✓     |
+| Vulnerability |     ✓     |
+|    License    |     ✓     |
+
+The table below outlines the features offered by Trivy.
+
+|               Feature                | Supported |
+|:------------------------------------:|:---------:|
+|       Unfixed vulnerabilities        |     -     |
+| [Dependency graph][dependency-graph] |     ✓     |
+
+## SBOM
+Trivy detects packages that have been installed through package managers such as `dnf` and `yum`.
+
+## Vulnerability
+SUSE offers its [own security advisories][cvrf], and these are utilized when scanning openSUSE/SLE for vulnerabilities.
+
+### Data Source
+See [here](../../scanner/vulnerability.md#data-sources).
+
+## License
+Trivy identifies licenses by examining the metadata of RPM packages.
+
+
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies
+[cvrf]: http://ftp.suse.com/pub/projects/security/cvrf/
+
+[vulnerability statuses]: ../../configuration/filtering.md#by-status

docs/docs/coverage/os/ubuntu.md

@@ -0,0 +1,65 @@
+# Ubuntu
+Trivy supports these scanners for OS packages.
+
+|    Scanner    | Supported |
+| :-----------: | :-------: |
+|     SBOM      |     ✓     |
+| Vulnerability |     ✓     |
+|    License    |     ✓     |
+
+Please see [here](index.md#supported-os) for supported versions.
+
+The following table provides an outline of the features Trivy offers.
+
+|               Feature                | Supported |
+|:------------------------------------:|:---------:|
+|    Detect unfixed vulnerabilities    |     ✓     |
+| [Dependency graph][dependency-graph] |     ✓     |
+
+## SBOM
+Same as [Debian](debian.md#sbom).
+
+## Vulnerability
+Ubuntu offers its own security advisories, and these are utilized when scanning Ubuntu for vulnerabilities.
+
+### Data Source
+See [here](../../scanner/vulnerability.md#data-sources).
+
+### Fixed Version
+When looking at fixed versions, it's crucial to consider the patches supplied by Ubuntu.
+As an illustration, for CVE-2023-3269, the fixed version for Ubuntu 23.04 (lunar) is listed as `6.2.0-26.26` in [the Security Tracker][CVE-2023-3269].
+It's essential to recognize that this differs from the upstream fixed version, which stands at `6.5`.
+Typically, only the upstream information gets listed on [NVD][CVE-2023-3269 NVD], so it's important not to get confused.
+
+### Severity
+Trivy calculates the severity of an issue based on the 'Priority' metric found in the Security Tracker.
+If 'Priority' isn't provided by Ubuntu, the severity from the NVD is taken into account.
+
+Using CVE-2019-15052 as an example, while it is rated as ["Critical" in NVD][CVE-2019-15052 NVD], Ubuntu has marked its "Priority" as ["Medium"][CVE-2019-15052].
+As a result, Trivy will display it as "Medium".
+
+### Status
+Trivy supports the following [vulnerability statuses] for Ubuntu.
+
+|       Status        | Supported |
+| :-----------------: | :-------: |
+|        Fixed        |     ✓     |
+|      Affected       |     ✓     |
+| Under Investigation |           |
+|    Will Not Fix     |           |
+|    Fix Deferred     |           |
+|     End of Life     |           |
+
+## License
+Same as [Debian](debian.md#license).
+
+
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies
+[Ubuntu CVE Tracker]: https://ubuntu.com/security/cve
+
+[CVE-2023-3269]: https://ubuntu.com/security/CVE-2023-3269
+[CVE-2019-15052]: https://ubuntu.com/security/CVE-2019-15052
+[CVE-2023-3269 NVD]: https://nvd.nist.gov/vuln/detail/CVE-2023-3269
+[CVE-2019-15052 NVD]: https://nvd.nist.gov/vuln/detail/CVE-2019-15052
+
+[vulnerability statuses]: ../../configuration/filtering.md#by-status

docs/docs/coverage/os/wolfi.md

@@ -0,0 +1,31 @@
+# Wolfi Linux
+Trivy supports these scanners for OS packages.
+
+|    Scanner    | Supported |
+| :-----------: | :-------: |
+|     SBOM      |     ✓     |
+| Vulnerability |     ✓     |
+|    License    |     ✓     |
+
+The table below outlines the features offered by Trivy.
+
+|               Feature                | Supported |
+|:------------------------------------:|:---------:|
+|    Detect unfixed vulnerabilities    |     -     |
+| [Dependency graph][dependency-graph] |     ✓     |
+
+## SBOM
+Same as [Alpine Linux](alpine.md#sbom).
+
+## Vulnerability
+Wolfi Linux offers its own security advisories, and these are utilized when scanning Wolfi for vulnerabilities.
+Everything else is the same as [Alpine Linux](alpine.md#vulnerability).
+
+### Data Source
+See [here](../../scanner/vulnerability.md#data-sources).
+
+## License
+Same as [Alpine Linux](alpine.md#license).
+
+[dependency-graph]: ../../configuration/reporting.md#show-origins-of-vulnerable-dependencies
+[secdb]: https://packages.wolfi.dev/os/security.json

docs/docs/references/configuration/cli/trivy.md

@@ -51,7 +51,7 @@ trivy [global flags] command [flags] target
 * [trivy kubernetes](trivy_kubernetes.md)	 - [EXPERIMENTAL] Scan kubernetes cluster
 * [trivy module](trivy_module.md)	 - Manage modules
 * [trivy plugin](trivy_plugin.md)	 - Manage plugins
-* [trivy repository](trivy_repository.md)	 - Scan a remote repository
+* [trivy repository](trivy_repository.md)	 - Scan a repository
 * [trivy rootfs](trivy_rootfs.md)	 - Scan rootfs
 * [trivy sbom](trivy_sbom.md)	 - Scan SBOM for vulnerabilities
 * [trivy server](trivy_server.md)	 - Server mode

docs/docs/references/configuration/cli/trivy_kubernetes.md

@@ -41,6 +41,7 @@ trivy kubernetes [flags] { cluster | all | specific resources like kubectl. eg:
       --download-db-only                  download/update vulnerability database but don't run a scan
       --download-java-db-only             download/update Java index database but don't run a scan
       --exclude-nodes strings             indicate the node labels that the node-collector job should exclude from scanning (example: kubernetes.io/arch:arm64,team:dev)
+      --exclude-owned                     exclude resources that have an owner reference
       --exit-code int                     specify exit code when any security issues are found
       --file-patterns strings             specify config file patterns
   -f, --format string                     format (table,json,cyclonedx) (default "table")

docs/docs/references/configuration/cli/trivy_repository.md

@@ -1,9 +1,9 @@
 ## trivy repository
 
-Scan a remote repository
+Scan a repository
 
 ```
-trivy repository [flags] REPO_URL
+trivy repository [flags] (REPO_PATH | REPO_URL)
 ```
 
 ### Examples
@@ -11,6 +11,8 @@ trivy repository [flags] REPO_URL
 ```
   # Scan your remote git repository
   $ trivy repo https://github.com/knqyf263/trivy-ci-test
+  # Scan your local git repository
+  $ trivy repo /path/to/your/repository
 ```
 
 ### Options

docs/docs/references/configuration/cli/trivy_server.md

@@ -20,30 +20,27 @@ trivy server [flags]
 ### Options
 
 ```
-      --cache-backend string        cache backend (e.g. redis://localhost:6379) (default "fs")
-      --cache-ttl duration          cache TTL when using redis as cache backend
-      --clear-cache                 clear image caches without scanning
-      --db-repository string        OCI repository to retrieve trivy-db from (default "ghcr.io/aquasecurity/trivy-db")
-      --download-db-only            download/update vulnerability database but don't run a scan
-      --download-java-db-only       download/update Java index database but don't run a scan
-      --enable-modules strings      [EXPERIMENTAL] module names to enable
-  -h, --help                        help for server
-      --java-db-repository string   OCI repository to retrieve trivy-java-db from (default "ghcr.io/aquasecurity/trivy-java-db")
-      --listen string               listen address in server mode (default "localhost:4954")
-      --module-dir string           specify directory to the wasm modules that will be loaded (default "$HOME/.trivy/modules")
-      --no-progress                 suppress progress bar
-      --password strings            password. Comma-separated passwords allowed. TRIVY_PASSWORD should be used for security reasons.
-      --redis-ca string             redis ca file location, if using redis as cache backend
-      --redis-cert string           redis certificate file location, if using redis as cache backend
-      --redis-key string            redis key file location, if using redis as cache backend
-      --redis-tls                   enable redis TLS with public certificates, if using redis as cache backend
-      --registry-token string       registry token
-      --reset                       remove all caches and database
-      --skip-db-update              skip updating vulnerability database
-      --skip-java-db-update         skip updating Java index database
-      --token string                for authentication in client/server mode
-      --token-header string         specify a header name for token in client/server mode (default "Trivy-Token")
-      --username strings            username. Comma-separated usernames allowed.
+      --cache-backend string     cache backend (e.g. redis://localhost:6379) (default "fs")
+      --cache-ttl duration       cache TTL when using redis as cache backend
+      --clear-cache              clear image caches without scanning
+      --db-repository string     OCI repository to retrieve trivy-db from (default "ghcr.io/aquasecurity/trivy-db")
+      --download-db-only         download/update vulnerability database but don't run a scan
+      --enable-modules strings   [EXPERIMENTAL] module names to enable
+  -h, --help                     help for server
+      --listen string            listen address in server mode (default "localhost:4954")
+      --module-dir string        specify directory to the wasm modules that will be loaded (default "$HOME/.trivy/modules")
+      --no-progress              suppress progress bar
+      --password strings         password. Comma-separated passwords allowed. TRIVY_PASSWORD should be used for security reasons.
+      --redis-ca string          redis ca file location, if using redis as cache backend
+      --redis-cert string        redis certificate file location, if using redis as cache backend
+      --redis-key string         redis key file location, if using redis as cache backend
+      --redis-tls                enable redis TLS with public certificates, if using redis as cache backend
+      --registry-token string    registry token
+      --reset                    remove all caches and database
+      --skip-db-update           skip updating vulnerability database
+      --token string             for authentication in client/server mode
+      --token-header string      specify a header name for token in client/server mode (default "Trivy-Token")
+      --username strings         username. Comma-separated usernames allowed.
 ```
 
 ### Options inherited from parent commands

docs/docs/references/modes/client-server.md

@@ -288,6 +288,48 @@ $ trivy server --listen localhost:8080 --token dummy
 $ trivy image --server http://localhost:8080 --token dummy alpine:3.10
 ```
 
+## Endpoints
+
+### Health
+Checks whether the Trivy server is running. Authentication is not required.
+
+Example request:
+```bash
+curl -s 0.0.0.0:8080/healthz
+ok
+```
+
+Returns the `200 OK` status if the request was successful.
+### Version
+
+Returns the version of the Trivy and all components (db, policy). Authentication is not required.
+
+Example request:
+```bash
+curl -s 0.0.0.0:8080/version | jq
+{
+  "Version": "dev",
+  "VulnerabilityDB": {
+    "Version": 2,
+    "NextUpdate": "2023-07-25T14:15:29.876639806Z",
+    "UpdatedAt": "2023-07-25T08:15:29.876640206Z",
+    "DownloadedAt": "2023-07-25T09:36:25.599004Z"
+  },
+  "JavaDB": {
+    "Version": 1,
+    "NextUpdate": "2023-07-28T01:03:52.169192565Z",
+    "UpdatedAt": "2023-07-25T01:03:52.169192765Z",
+    "DownloadedAt": "2023-07-25T09:37:48.906152Z"
+  },
+  "PolicyBundle": {
+    "Digest": "sha256:829832357626da2677955e3b427191212978ba20012b6eaa03229ca28569ae43",
+    "DownloadedAt": "2023-07-23T11:40:33.122462Z"
+  }
+}
+```
+
+Returns the `200 OK` status if the request was successful.
+
 ## Architecture
 
 ![architecture](../../../imgs/client-server.png)

docs/docs/scanner/license.md

@@ -17,6 +17,8 @@ License are classified using the [Google License Classification][google-license-
     As those licenses may be in violation, it is recommended to check those unknown licenses as well.    
 
 By default, Trivy scans licenses for packages installed by `apk`, `apt-get`, `dnf`, `npm`, `pip`, `gem`, etc.
+Check out [the coverage document][coverage] for details.
+
 To enable extended license scanning, you can use `--license-full`.
 In addition to package licenses, Trivy scans source code files, Markdown documents, text files and `LICENSE` documents to identify license usage within the image or filesystem.
 
@@ -29,14 +31,14 @@ To configure the confidence level, you can use `--license-confidence-level`. Thi
 Currently, the standard license scanning doesn't support filesystem and repository scanning.
 
 |   License scanning    | Image | Rootfs | Filesystem | Repository |
-|:---------------------:|:-----:|:------:|:----------:|:----------:|
+| :-------------------: | :---: | :----: | :--------: | :--------: |
 |       Standard        |   ✅   |   ✅    |     -      |     -      |
 | Full (--license-full) |   ✅   |   ✅    |     ✅      |     ✅      |
 
 License checking classifies the identified licenses and map the classification to severity.
 
 | Classification | Severity |
-|----------------|----------|
+| -------------- | -------- |
 | Forbidden      | CRITICAL |
 | Restricted     | HIGH     |
 | Reciprocal     | MEDIUM   |
@@ -343,4 +345,5 @@ license:
 ```
 
 
+[coverage]: ../coverage/index.md
 [google-license-classification]: https://opensource.google/documentation/reference/thirdparty/licenses

docs/docs/scanner/misconfiguration/custom/index.md

@@ -14,7 +14,7 @@ As for `--namespaces` option, the detail is described as below.
 If a file name matches the following file patterns, Trivy will parse the file and pass it as input to your Rego policy.
 
 | File format   | File pattern                                              |
-|---------------|-----------------------------------------------------------|
+| ------------- | --------------------------------------------------------- |
 | JSON          | `*.json`                                                  |
 | YAML          | `*.yaml` and `*.yml`                                      |
 | Dockerfile    | `Dockerfile`, `Dockerfile.*`, and `*.Dockerfile`          |
@@ -125,14 +125,14 @@ schema that will be used is based on the input document type. It is recommended
 correct and do not reference incorrect properties/values.
 
 | Field name                 | Allowed values                                                    |        Default value         |     In table     |     In JSON      |
-|----------------------------|-------------------------------------------------------------------|:----------------------------:|:----------------:|:----------------:|
+| -------------------------- | ----------------------------------------------------------------- | :--------------------------: | :--------------: | :--------------: |
 | title                      | Any characters                                                    |             N/A              | :material-check: | :material-check: |
 | description                | Any characters                                                    |                              | :material-close: | :material-check: |
 | schemas.input              | `schema["kubernetes"]`, `schema["dockerfile"]`, `schema["cloud"]` | (applied to all input types) | :material-close: | :material-close: |
 | custom.id                  | Any characters                                                    |             N/A              | :material-check: | :material-check: |
 | custom.severity            | `LOW`, `MEDIUM`, `HIGH`, `CRITICAL`                               |           UNKNOWN            | :material-check: | :material-check: |
-| custom.recommended_actions | Any characters                                                    |                              | :material-close: | :material-check: | 
-| custom.input.selector.type | Any item(s) in [this list][source-types]                          |                              | :material-close: | :material-check: | 
+| custom.recommended_actions | Any characters                                                    |                              | :material-close: | :material-check: |
+| custom.input.selector.type | Any item(s) in [this list][source-types]                          |                              | :material-close: | :material-check: |
 | url                        | Any characters                                                    |                              | :material-close: | :material-check: |
 
 
@@ -178,6 +178,7 @@ You can specify input format via the `custom.input` annotation.
     Even if a Dockerfile exists in the specified directory, it will not be passed to the policy as input.
 
     Possible values for input types are:
+
     - `dockerfile` (Dockerfile)
     - `kubernetes` (Kubernetes YAML/JSON)
     - `rbac` (Kubernetes RBAC YAML/JSON)

docs/docs/scanner/misconfiguration/index.md

@@ -349,55 +349,4 @@ This can be repeated for specifying multiple packages.
 trivy conf --policy ./policy --namespaces main --namespaces user ./configs
 ```
 
-### Terraform value overrides
-You can pass `tf-vars` files to Trivy to override default values found in the Terraform HCL code.
-
-```bash
-trivy conf --tf-vars dev.terraform.tfvars ./infrastructure/tf
-```
-
-### Exclude downloaded Terraform modules
-You can remove results for downloaded modules in `.terraform` folder.
-```bash
-trivy conf --tf-exclude-downloaded-modules ./configs
-```
-
-### Helm value overrides
-There are a number of options for overriding values in Helm charts. When override values are passed to the Helm scanner, the values will be used during the Manifest rendering process and will become part of the scanned artifact.
-
-#### Setting inline value overrides
-Overrides can be set inline on the command line
-
-```bash
-trivy conf --helm-set securityContext.runAsUser=0 ./charts/mySql
-```
-
-#### Setting value file overrides
-Overrides can be in a file that has the key=value set.
-
-```yaml
-# Example override file (overrides.yaml)
-
-securityContext:
-  runAsUser: 0
-```
-
-```bash
-trivy conf --helm-values overrides.yaml ./charts/mySql
-``` 
-
-#### Setting value as explicit string
-the `--helm-set-string` is the same as `--helm-set` but explicitly retains the value as a string
-
-```bash
-trivy config --helm-set-string name=false ./infrastructure/tf
-```
-
-#### Setting specific values from files
-Specific override values can come from specific files
-
-```bash
-trivy conf --helm-set-file environment=dev.values.yaml ./charts/mySql
-```
-
 [custom]: custom/index.md

docs/docs/scanner/misconfiguration/policy/builtin.md

@@ -1,23 +1,12 @@
 # Built-in Policies
 
 ## Policy Sources
-
 Built-in policies are mainly written in [Rego][rego] and Go.
 Those policies are managed under [defsec repository][defsec].
-
-| Config type               | Source               |
-|---------------------------|----------------------|
-| Kubernetes                | [defsec][kubernetes] |
-| Dockerfile, Containerfile | [defsec][docker]     |
-| Terraform                 | [defsec][defsec]     |
-| CloudFormation            | [defsec][defsec]     |
-| Azure ARM Template        | [defsec][defsec]     |
-| Helm Chart                | [defsec][kubernetes] |      
+See [here](../../../coverage/iac/index.md) for the list of supported config types.
 
 For suggestions or issues regarding policy content, please open an issue under the [defsec][defsec] repository.
 
-Helm Chart scanning will resolve the chart to Kubernetes manifests then run the [kubernetes][kubernetes] checks.
-
 ## Policy Distribution
 defsec policies are distributed as an OPA bundle on [GitHub Container Registry][ghcr] (GHCR).
 When misconfiguration detection is enabled, Trivy pulls the OPA bundle from GHCR as an OCI artifact and stores it in the cache.
@@ -28,7 +17,8 @@ If Trivy is unable to pull down newer policies, it will use the embedded set of
 Trivy checks for updates to OPA bundle on GHCR every 24 hours and pulls it if there are any updates.
 
 [rego]: https://www.openpolicyagent.org/docs/latest/policy-language/
+
+[kubernetes-policies]: https://github.com/aquasecurity/defsec/tree/master/rules/kubernetes/policies
+[docker-policies]: https://github.com/aquasecurity/defsec/tree/master/rules/docker/policies
 [defsec]: https://github.com/aquasecurity/defsec
-[kubernetes]: https://github.com/aquasecurity/defsec/tree/master/rules/kubernetes/policies
-[docker]: https://github.com/aquasecurity/defsec/tree/master/rules/docker/policies
-[ghcr]: https://github.com/aquasecurity/defsec/pkgs/container/defsec
+[ghcr]: https://github.com/aquasecurity/defsec/pkgs/container/defsec

docs/docs/scanner/secret.md

@@ -96,7 +96,7 @@ If the file doesn't exist, only built-in rules are used.
 You can customize the config file path via the `--secret-config` flag.
 
 !!! warning
-    Trivy uses [Golang regexp package](https://pkg.go.dev/regexp/syntax#hdr-Syntax). To use `^` and `$` as simbols of begin and end of line use multi-line mode -`(?m)`.
+    Trivy uses [Golang regexp package](https://pkg.go.dev/regexp/syntax#hdr-Syntax). To use `^` and `$` as symbols of begin and end of line use multi-line mode -`(?m)`.
 
 ### Custom Rules
 Trivy allows defining custom rules.

docs/docs/scanner/vulnerability.md

@@ -0,0 +1,199 @@
+# Vulnerability Scanning
+Trivy detects known vulnerabilities according to the versions of installed packages.
+
+The following packages are supported.
+
+- [OS packages](#os-packages)
+- [Language-specific packages](#language-specific-packages)
+- [Kubernetes components (control plane, node and addons)](#kubernetes-components-control-plane-node-and-addons)
+
+Trivy also detects known vulnerabilities in Kubernetes components using KBOM (Kubernetes bill of Material) scanning. To learn more, see the [documentation for Kubernetes scanning](../target/kubernetes.md#KBOM).
+
+## OS Packages
+Trivy is capable of automatically detecting installed OS packages when scanning container images, VM images and running hosts.
+
+!!! note
+    Trivy doesn't support third-party/self-compiled packages/binaries, but official packages provided by vendors such as Red Hat and Debian.
+
+### Supported OS
+See [here](../coverage/os/index.md#supported-os) for the supported OSes.
+
+### Data Sources
+
+| OS            | Source                                                       |
+| ------------- | ------------------------------------------------------------ |
+| Arch Linux    | [Vulnerable Issues][arch]                                    |
+| Alpine Linux  | [secdb][alpine]                                              |
+| Wolfi Linux   | [secdb][wolfi]                                               |
+| Chainguard    | [secdb][chainguard]                                          |
+| Amazon Linux  | [Amazon Linux Security Center][amazon]                       |
+| Debian        | [Security Bug Tracker][debian-tracker] / [OVAL][debian-oval] |
+| Ubuntu        | [Ubuntu CVE Tracker][ubuntu]                                 |
+| RHEL/CentOS   | [OVAL][rhel-oval] / [Security Data][rhel-api]                |
+| AlmaLinux     | [AlmaLinux Product Errata][alma]                             |
+| Rocky Linux   | [Rocky Linux UpdateInfo][rocky]                              |
+| Oracle Linux  | [OVAL][oracle]                                               |
+| CBL-Mariner   | [OVAL][mariner]                                              |
+| OpenSUSE/SLES | [CVRF][suse]                                                 |
+| Photon OS     | [Photon Security Advisory][photon]                           |
+
+#### Data Source Selection
+Trivy **only** consumes security advisories from the sources listed in the above table.
+
+As for packages installed from OS package managers (`dpkg`, `yum`, `apk`, etc.), Trivy uses the advisory database from the appropriate **OS vendor**.
+
+For example: for a python package installed from `yum` (Amazon linux), Trivy will only get advisories from [ALAS][amazon].
+But for a python package installed from another source (e.g. `pip`), Trivy will get advisories from the `GitLab` and `GitHub` databases.
+
+This advisory selection is essential to avoid getting false positives because OS vendors usually backport upstream fixes, and the fixed version can be different from the upstream fixed version.
+
+#### Severity Selection
+The severity is taken from the selected data source since the severity from vendors is more accurate.
+Using CVE-2023-0464 as an example, while it is [rated as "HIGH" in NVD][nvd-CVE-2023-0464], Red Hat has marked its 'Impact' as ["Low"][redhat-CVE-2023-0464].
+As a result, Trivy will display it as "Low".
+
+The severity depends on the compile option, the default configuration, etc.
+NVD doesn't know how the vendor distributes the software.
+Red Hat evaluates the severity more accurately.
+That's why Trivy prefers vendor scores over NVD.
+
+If the data source does not provide a severity, the severity is determined based on the CVSS score as follows:
+
+| Base Score Range | Severity |
+| ---------------- | -------- |
+| 0.1-3.9          | Low      |
+| 4.0-6.9          | Medium   |
+| 7.0-8.9          | High     |
+| 9.0-10.0         | Critical |
+
+If the CVSS score is also not provided, it falls back to [NVD][nvd], and if NVD does not have severity, it will be UNKNOWN.
+
+### Unfixed Vulnerabilities
+The unfixed/unfixable vulnerabilities mean that the patch has not yet been provided on their distribution.
+To hide unfixed/unfixable vulnerabilities, you can use the `--ignore-unfixed` flag.
+
+## Language-specific Packages
+
+### Supported Languages
+See [here](../coverage/language/index.md#supported-languages) for the supported languages.
+
+### Data Sources
+
+| Language | Source                                              | Commercial Use | Delay[^1] |
+|----------|-----------------------------------------------------|:--------------:|:---------:|
+| PHP      | [PHP Security Advisories Database][php]             |       ✅        |     -     |
+|          | [GitHub Advisory Database (Composer)][php-ghsa]     |       ✅        |     -     |
+| Python   | [GitHub Advisory Database (pip)][python-ghsa]       |       ✅        |     -     |
+|          | [Open Source Vulnerabilities (PyPI)][python-osv]    |       ✅        |     -     |
+| Ruby     | [Ruby Advisory Database][ruby]                      |       ✅        |     -     |
+|          | [GitHub Advisory Database (RubyGems)][ruby-ghsa]    |       ✅        |     -     |
+| Node.js  | [Ecosystem Security Working Group][nodejs]          |       ✅        |     -     |
+|          | [GitHub Advisory Database (npm)][nodejs-ghsa]       |       ✅        |     -     |
+| Java     | [GitLab Advisories Community][gitlab]               |       ✅        |  1 month  |
+|          | [GitHub Advisory Database (Maven)][java-ghsa]       |       ✅        |     -     |
+| Go       | [GitHub Advisory Database (Go)][go-ghsa]            |       ✅        |     -     |
+| Rust     | [Open Source Vulnerabilities (crates.io)][rust-osv] |       ✅        |     -     |
+| .NET     | [GitHub Advisory Database (NuGet)][dotnet-ghsa]     |       ✅        |     -     |
+| C/C++    | [GitLab Advisories Community][gitlab]               |       ✅        |  1 month  |
+| Dart     | [GitHub Advisory Database (Pub)][pub-ghsa]          |       ✅        |     -     |
+| Elixir   | [GitHub Advisory Database (Erlang)][erlang-ghsa]    |       ✅        |     -     |
+| Swift    | [GitHub Advisory Database (Swift)][swift-ghsa]      |       ✅        |     -     |
+
+[^1]: Intentional delay between vulnerability disclosure and registration in the DB
+
+## Kubernetes
+
+Trivy can detect vulnerabilities in Kubernetes clusters and components.
+
+### Data Sources
+
+| Vendor        | Source                                      |
+| ------------- |---------------------------------------------|
+| Kubernetes    | [Kubernetes Official CVE feed][k8s-cve][^1] |
+
+[^1]: Some manual triage and correction has been made.
+
+## Database
+Trivy downloads [the vulnerability database](https://github.com/aquasecurity/trivy-db) every 6 hours.
+Trivy uses two types of databases for vulnerability detection:
+
+- Vulnerability Database
+- Java Index Database
+
+This page provides detailed information about these databases.
+
+### Vulnerability Database
+Trivy utilizes a database containing vulnerability information.
+This database is built every six hours on [GitHub](https://github.com/aquasecurity/trivy-db) and is distributed via [GitHub Container registry (GHCR)](https://ghcr.io/aquasecurity/trivy-db).
+The database is cached and updated as needed.
+As Trivy updates the database automatically during execution, users don't need to be concerned about it.
+
+For CLI flags related to the database, please refer to [this page](../configuration/db.md).
+
+#### Private Hosting
+If you host the database on your own OCI registry, you can specify a different repository with the `--db-repository` flag.
+The default is `ghcr.io/aquasecurity/trivy-db`.
+
+```shell
+$ trivy image --db-repository YOUR_REPO YOUR_IMAGE
+```
+
+If authentication is required, it can be configured in the same way as for private images.
+Please refer to [the documentation](../advanced/private-registries/index.md) for more details.
+
+### Java Index Database
+This database is only downloaded when scanning JAR files so that Trivy can identify the groupId, artifactId, and version of JAR files.
+It is built once a day on [GitHub](https://github.com/aquasecurity/trivy-java-db) and distributed via [GitHub Container registry (GHCR)](https://ghcr.io/aquasecurity/trivy-java-db).
+Like the vulnerability database, it is automatically downloaded and updated when needed, so users don't need to worry about it.
+
+#### Private Hosting
+If you host the database on your own OCI registry, you can specify a different repository with the `--java-db-repository` flag.
+The default is `ghcr.io/aquasecurity/trivy-java-db`.
+
+If authentication is required, you need to run `docker login YOUR_REGISTRY`.
+Currently, specifying a username and password is not supported.
+
+[^1]: https://github.com/GoogleContainerTools/distroless
+
+[nvd-CVE-2023-0464]: https://nvd.nist.gov/vuln/detail/CVE-2023-0464
+[redhat-CVE-2023-0464]: https://access.redhat.com/security/cve/cve-2023-0464
+
+[arch]: https://security.archlinux.org/
+[alpine]: https://secdb.alpinelinux.org/
+[wolfi]: https://packages.wolfi.dev/os/security.json
+[chainguard]: https://packages.cgr.dev/chainguard/security.json
+[amazon]: https://alas.aws.amazon.com/
+[debian-tracker]: https://security-tracker.debian.org/tracker/
+[debian-oval]: https://www.debian.org/security/oval/
+[ubuntu]: https://ubuntu.com/security/cve
+[rhel-oval]: https://www.redhat.com/security/data/oval/v2/
+[rhel-api]: https://www.redhat.com/security/data/metrics/
+[alma]: https://errata.almalinux.org/
+[rocky]: https://download.rockylinux.org/pub/rocky/
+[oracle]: https://linux.oracle.com/security/oval/
+[suse]: http://ftp.suse.com/pub/projects/security/cvrf/
+[photon]: https://packages.vmware.com/photon/photon_cve_metadata/
+[mariner]: https://github.com/microsoft/CBL-MarinerVulnerabilityData/
+
+[php-ghsa]: https://github.com/advisories?query=ecosystem%3Acomposer
+[python-ghsa]: https://github.com/advisories?query=ecosystem%3Apip
+[ruby-ghsa]: https://github.com/advisories?query=ecosystem%3Arubygems
+[nodejs-ghsa]: https://github.com/advisories?query=ecosystem%3Anpm
+[java-ghsa]: https://github.com/advisories?query=ecosystem%3Amaven
+[dotnet-ghsa]: https://github.com/advisories?query=ecosystem%3Anuget
+[pub-ghsa]: https://github.com/advisories?query=ecosystem%3Apub
+[erlang-ghsa]: https://github.com/advisories?query=ecosystem%3Aerlang
+[go-ghsa]: https://github.com/advisories?query=ecosystem%3Ago
+[swift-ghsa]: https://github.com/advisories?query=ecosystem%3Aswift
+
+[php]: https://github.com/FriendsOfPHP/security-advisories
+[ruby]: https://github.com/rubysec/ruby-advisory-db
+[nodejs]: https://github.com/nodejs/security-wg
+[gitlab]: https://gitlab.com/gitlab-org/advisories-community
+
+[python-osv]: https://osv.dev/list?q=&ecosystem=PyPI
+[rust-osv]: https://osv.dev/list?q=&ecosystem=crates.io
+
+[nvd]: https://nvd.nist.gov/vuln
+
+[k8s-cve]: https://kubernetes.io/docs/reference/issues-security/official-cve-feed/

docs/docs/scanner/vulnerability/index.md

@@ -1,51 +0,0 @@
-# Vulnerability Scanning
-
-## Overview
-This section describes the overview of vulnerability scanning.
-Trivy detects known vulnerabilities according to the versions of installed packages.
-
-The following packages are supported.
-
-- [OS packages](os.md)
-- [Language-specific packages](language/index.md)
-
-Trivy downloads [the vulnerabillity database](https://github.com/aquasecurity/trivy-db) every 6 hours.
-
-## Database
-Trivy uses two types of databases for vulnerability detection:
-
-- Vulnerability Database
-- Java Index Database
-
-This page provides detailed information about these databases.
-
-### Vulnerability Database
-Trivy utilizes a database containing vulnerability information.
-This database is built every six hours on [GitHub](https://github.com/aquasecurity/trivy-db) and is distributed via [GitHub Container registry (GHCR)](https://ghcr.io/aquasecurity/trivy-db).
-The database is cached and updated as needed.
-As Trivy updates the database automatically during execution, users don't need to be concerned about it.
-
-For CLI flags related to the database, please refer to [this page](../../configuration/db.md).
-
-#### Private Hosting
-If you host the database on your own OCI registry, you can specify a different repository with the `--db-repository` flag.
-The default is `ghcr.io/aquasecurity/trivy-db`.
-
-```shell
-$ trivy image --db-repository YOUR_REPO YOUR_IMAGE
-```
-
-If authentication is required, it can be configured in the same way as for private images.
-Please refer to [the documentation](../../advanced/private-registries/index.md) for more details.
-
-### Java Index Database
-This database is only downloaded when scanning JAR files so that Trivy can identify the groupId, artifactId, and version of JAR files.
-It is built once a day on [GitHub](https://github.com/aquasecurity/trivy-java-db) and distributed via [GitHub Container registry (GHCR)](https://ghcr.io/aquasecurity/trivy-java-db).
-Like the vulnerability database, it is automatically downloaded and updated when needed, so users don't need to worry about it.
-
-#### Private Hosting
-If you host the database on your own OCI registry, you can specify a different repository with the `--java-db-repository` flag.
-The default is `ghcr.io/aquasecurity/trivy-java-db`.
-
-If authentication is required, you need to run `docker login YOUR_REGISTRY`.
-Currently, specifying a username and password is not supported.

docs/docs/scanner/vulnerability/language/index.md

@@ -1,92 +0,0 @@
-# Language-specific Packages
-
-`Trivy` automatically detects the following files and scans vulnerabilities in the application dependencies.
-
-## Supported languages
-
-| Language             | File                                                                                       | Image[^7] | Rootfs[^8] | Filesystem[^9] | Repository[^10] | Dev dependencies             | Dependency location[^11] |
-|----------------------|--------------------------------------------------------------------------------------------|:---------:|:----------:|:--------------:|:---------------:|------------------------------|:------------------------:|
-| Ruby                 | Gemfile.lock                                                                               |     -     |     -      |       ✅        |        ✅        | included                     |            -             |
-|                      | gemspec                                                                                    |     ✅     |     ✅      |       -        |        -        | included                     |            -             |
-| [Python](python.md)  | Pipfile.lock                                                                               |     -     |     -      |       ✅        |        ✅        | excluded                     |            ✅             |
-|                      | poetry.lock                                                                                |     -     |     -      |       ✅        |        ✅        | excluded                     |            -             |
-|                      | requirements.txt                                                                           |     -     |     -      |       ✅        |        ✅        | included                     |            -             |
-|                      | egg package[^1]                                                                            |     ✅     |     ✅      |       -        |        -        | excluded                     |            -             |
-|                      | wheel package[^2]                                                                          |     ✅     |     ✅      |       -        |        -        | excluded                     |            -             |
-| [PHP](php.md)        | composer.lock                                                                              |     ✅     |     ✅      |       ✅        |        ✅        | excluded                     |            ✅             |
-| [Node.js](nodejs.md) | package-lock.json                                                                          |     -     |     -      |       ✅        |        ✅        | [excluded](./nodejs.md#npm)  |            ✅             |
-|                      | yarn.lock                                                                                  |     -     |     -      |       ✅        |        ✅        | [excluded](./nodejs.md#yarn) |            ✅             |
-|                      | pnpm-lock.yaml                                                                             |     -     |     -      |       ✅        |        ✅        | excluded                     |            -             |
-|                      | package.json                                                                               |     ✅     |     ✅      |       -        |        -        | excluded                     |            -             |
-| .NET                 | packages.lock.json                                                                         |     ✅     |     ✅      |       ✅        |        ✅        | included                     |            ✅             |
-|                      | packages.config                                                                            |     ✅     |     ✅      |       ✅        |        ✅        | excluded                     |            -             |
-|                      | .deps.json                                                                                 |     ✅     |     ✅      |       ✅        |        ✅        | excluded                     |            ✅             |
-| [Java](java.md)      | JAR/WAR/PAR/EAR[^3]                                                                        |     ✅     |     ✅      |       -        |        -        | included                     |            -             |
-|                      | pom.xml[^4]                                                                                |     -     |     -      |       ✅        |        ✅        | excluded                     |            -             |
-|                      | *gradle.lockfile                                                                           |     -     |     -      |       ✅        |        ✅        | excluded                     |            -             |
-| [Go](golang.md)      | Binaries built by Go[^5]                                                                   |     ✅     |     ✅      |       -        |        -        | excluded                     |            -             |
-|                      | go.mod[^6]                                                                                 |     -     |     -      |       ✅        |        ✅        | included                     |            -             |
-| [Rust](rust.md)      | Cargo.lock                                                                                 |     ✅     |     ✅      |       ✅        |        ✅        | excluded                     |            ✅             |
-|                      | Binaries built with [cargo-auditable](https://github.com/rust-secure-code/cargo-auditable) |     ✅     |     ✅      |       -        |        -        | excluded                     |            -             |
-| C/C++                | conan.lock[^12]                                                                            |     -     |     -      |       ✅        |        ✅        | excluded                     |            -             |   
-| Elixir               | mix.lock[^12]                                                                              |     -     |     -      |       ✅        |        ✅        | excluded                     |            ✅             |
-| Dart                 | pubspec.lock                                                                               |     -     |     -      |       ✅        |        ✅        | included                     |            -             |
-
-The path of these files does not matter.
-
-Example: [Dockerfile](https://github.com/aquasecurity/trivy-ci-test/blob/main/Dockerfile)
-
-[^1]: `*.egg-info`, `*.egg-info/PKG-INFO`, `*.egg` and `EGG-INFO/PKG-INFO`
-[^2]: `.dist-info/META-DATA`
-[^3]: `*.jar`, `*.war`, `*.par` and `*.ear`
-[^4]: It requires Internet access when the POM doesn't exist in your local repository
-[^5]: UPX-compressed binaries don't work
-[^6]: If smaller than go 1.17, go.sum is also required
-[^7]: ✅ means "enabled" and `-` means "disabled" in the image scanning
-[^8]: ✅ means "enabled" and `-` means "disabled" in the rootfs scanning
-[^9]: ✅ means "enabled" and `-` means "disabled" in the filesystem scanning
-[^10]: ✅ means "enabled" and `-` means "disabled" in the git repository scanning
-[^11]: ✅ means that Trivy detects line numbers where each dependency is declared in the scanned file. Only supported in [json](../../../configuration/reporting.md#json) and [sarif](../../../configuration/reporting.md#sarif) formats. SARIF uses `startline == 1 and endline == 1` for unsupported file types
-[^12]: To scan a filename other than the default filename use [file-patterns](../../../configuration/others.md#file-patterns)
-[^13]: When you scan `Cargo.lock` and `Cargo.toml` together. See about it [here](./rust.md#cargo).
-
-## Data Sources
-
-| Language | Source                                              | Commercial Use | Delay[^1] |
-|----------|-----------------------------------------------------|:--------------:|:---------:|
-| PHP      | [PHP Security Advisories Database][php]             |       ✅        |     -     |
-|          | [GitHub Advisory Database (Composer)][php-ghsa]     |       ✅        |     -     |
-| Python   | [GitHub Advisory Database (pip)][python-ghsa]       |       ✅        |     -     |
-|          | [Open Source Vulnerabilities (PyPI)][python-osv]    |       ✅        |     -     |
-| Ruby     | [Ruby Advisory Database][ruby]                      |       ✅        |     -     |
-|          | [GitHub Advisory Database (RubyGems)][ruby-ghsa]    |       ✅        |     -     |
-| Node.js  | [Ecosystem Security Working Group][nodejs]          |       ✅        |     -     |
-|          | [GitHub Advisory Database (npm)][nodejs-ghsa]       |       ✅        |     -     |
-| Java     | [GitLab Advisories Community][gitlab]               |       ✅        |  1 month  |
-|          | [GitHub Advisory Database (Maven)][java-ghsa]       |       ✅        |     -     |
-| Go       | [GitHub Advisory Database (Go)][go-ghsa]            |       ✅        |     -     |
-| Rust     | [Open Source Vulnerabilities (crates.io)][rust-osv] |       ✅        |     -     |
-| .NET     | [GitHub Advisory Database (NuGet)][dotnet-ghsa]     |       ✅        |     -     |
-| C/C++    | [GitLab Advisories Community][gitlab]               |       ✅        |  1 month  |
-| Dart     | [GitHub Advisory Database (Pub)][pub-ghsa]          |       ✅        |     -     |
-| Elixir   | [GitHub Advisory Database (Erlang)][erlang-ghsa]    |       ✅        |           |
-
-[^1]: Intentional delay between vulnerability disclosure and registration in the DB
-
-[php-ghsa]: https://github.com/advisories?query=ecosystem%3Acomposer
-[python-ghsa]: https://github.com/advisories?query=ecosystem%3Apip
-[ruby-ghsa]: https://github.com/advisories?query=ecosystem%3Arubygems
-[nodejs-ghsa]: https://github.com/advisories?query=ecosystem%3Anpm
-[java-ghsa]: https://github.com/advisories?query=ecosystem%3Amaven
-[dotnet-ghsa]: https://github.com/advisories?query=ecosystem%3Anuget
-[pub-ghsa]: https://github.com/advisories?query=ecosystem%3Apub
-[erlang-ghsa]: https://github.com/advisories?query=ecosystem%3Aerlang
-[go-ghsa]: https://github.com/advisories?query=ecosystem%3Ago
-
-[php]: https://github.com/FriendsOfPHP/security-advisories
-[ruby]: https://github.com/rubysec/ruby-advisory-db
-[nodejs]: https://github.com/nodejs/security-wg
-[gitlab]: https://gitlab.com/gitlab-org/advisories-community
-
-[python-osv]: https://osv.dev/list?q=&ecosystem=PyPI
-[rust-osv]: https://osv.dev/list?q=&ecosystem=crates.io

docs/docs/scanner/vulnerability/os.md

@@ -1,136 +0,0 @@
-# OS Packages
-Trivy is capable of automatically detecting installed OS packages when scanning container images, VM images and running hosts.
-This page provides an overview of OS packages in the context of Trivy scans.
-
-## Supported OS
-
-The unfixed/unfixable vulnerabilities mean that the patch has not yet been provided on their distribution.
-To hide unfixed/unfixable vulnerabilities, you can use the `--ignore-unfixed` flag.
-
-Trivy doesn't support self-compiled packages/binaries, but official packages provided by vendors such as Red Hat and Debian.
-
-| OS                               | Supported Versions                  | Target Packages               | Detection of unfixed vulnerabilities |
-|----------------------------------|-------------------------------------|-------------------------------|:------------------------------------:|
-| Alpine Linux                     | 2.2 - 2.7, 3.0 - 3.18, edge         | Installed by apk              |                  NO                  |
-| Wolfi Linux                      | (n/a)                               | Installed by apk              |                  NO                  |
-| Chainguard                       | (n/a)                               | Installed by apk              |                  NO                  |
-| Red Hat Universal Base Image[^1] | 7, 8, 9                             | Installed by yum/rpm          |                 YES                  |
-| Red Hat Enterprise Linux         | 6, 7, 8                             | Installed by yum/rpm          |                 YES                  |
-| CentOS                           | 6, 7, 8                             | Installed by yum/rpm          |                 YES                  |
-| AlmaLinux                        | 8, 9                                | Installed by yum/rpm          |                  NO                  |
-| Rocky Linux                      | 8, 9                                | Installed by yum/rpm          |                  NO                  |
-| Oracle Linux                     | 5, 6, 7, 8                          | Installed by yum/rpm          |                  NO                  |
-| CBL-Mariner                      | 1.0, 2.0                            | Installed by yum/rpm          |                 YES                  |
-| Amazon Linux                     | 1, 2, 2023                          | Installed by yum/rpm          |                  NO                  |
-| openSUSE Leap                    | 42, 15                              | Installed by zypper/rpm       |                  NO                  |
-| SUSE Enterprise Linux            | 11, 12, 15                          | Installed by zypper/rpm       |                  NO                  |
-| Photon OS                        | 1.0, 2.0, 3.0, 4.0                  | Installed by tdnf/yum/rpm     |                  NO                  |
-| Debian GNU/Linux                 | 7, 8, 9, 10, 11, 12                 | Installed by apt/apt-get/dpkg |                 YES                  |
-| Ubuntu                           | All versions supported by Canonical | Installed by apt/apt-get/dpkg |                 YES                  |
-| Distroless[^2]                   | Any                                 | Installed by apt/apt-get/dpkg |                 YES                  |
-
-## Data Sources
-
-| OS            | Source                                 |
-|---------------|----------------------------------------|
-| Arch Linux    | [Vulnerable Issues][arch]              |
-| Alpine Linux  | [secdb][alpine]                        |
-| Wolfi Linux   | [secdb][wolfi]                         |
-| Chainguard    | [secdb][chainguard]                    |
-| Amazon Linux  | [Amazon Linux Security Center][amazon] |
-| Debian        | [Security Bug Tracker][debian-tracker] |
-|               | [OVAL][debian-oval]                    |
-| Ubuntu        | [Ubuntu CVE Tracker][ubuntu]           |
-| RHEL/CentOS   | [OVAL][rhel-oval]                      |
-|               | [Security Data][rhel-api]              |
-| AlmaLinux     | [AlmaLinux Product Errata][alma]       |
-| Rocky Linux   | [Rocky Linux UpdateInfo][rocky]        |
-| Oracle Linux  | [OVAL][oracle]                         |
-| CBL-Mariner   | [OVAL][mariner]                        |
-| OpenSUSE/SLES | [CVRF][suse]                           |
-| Photon OS     | [Photon Security Advisory][photon]     |
-
-### Data source selection
-Trivy **only** consumes security advisories from the sources listed in the above table.
-
-As for packages installed from OS package managers (`dpkg`, `yum`, `apk`, etc.), Trivy uses the advisory database from the appropriate **OS vendor**.
-
-For example: for a python package installed from `yum` (Amazon linux), Trivy will only get advisories from [ALAS][amazon].
-But for a python package installed from another source (e.g. `pip`), Trivy will get advisories from the `GitLab` and `GitHub` databases.
-
-This advisory selection is essential to avoid getting false positives because OS vendors usually backport upstream fixes, and the fixed version can be different from the upstream fixed version.
-The severity is from the selected data source.
-If the data source does not provide severity, it falls back to [NVD][nvd], and if NVD does not have severity, it will be UNKNOWN.
-
-## Distributions
-### CBL-Mariner
-Trivy scans [CBL-Mariner][cbl-mariner].
-
-#### Support
-The following table provides an outline of the features Trivy offers.
-
-| Version | Container image | Virtual machine | Distroless |  Multi-arch  | Unfixed support |
-|---------|:---------------:|:---------------:|:----------:|:------------:|:---------------:|
-| 1.0     |        ✔        |        ✔        |     ✔      | amd64, arm64 |        ✔        |
-| 2.0     |        ✔        |        ✔        |     ✔      | amd64, arm64 |        ✔        |
-
-### Examples
-
-=== "image"
-    ```
-    ➜ trivy image mcr.microsoft.com/cbl-mariner/base/core:2.0
-    2022-07-27T14:48:20.355+0600	INFO	Detected OS: cbl-mariner
-    2022-07-27T14:48:20.355+0600	INFO	Detecting CBL-Mariner vulnerabilities...
-    2022-07-27T14:48:20.356+0600	INFO	Number of language-specific files: 0
-    
-    mcr.microsoft.com/cbl-mariner/base/core:2.0 (cbl-mariner 2.0.20220527)
-        
-    Total: 33 (UNKNOWN: 0, LOW: 0, MEDIUM: 15, HIGH: 13, CRITICAL: 5)
-    ```
-
-=== "rootfs"
-    ```
-    ➜ docker run  -it --rm --entrypoint bin/bash mcr.microsoft.com/cbl-mariner/base/core:2.0
-    root [ / ]# tdnf -y install ca-certificates
-    root [ / ]# # Install the latest Trivy
-    root [ / ]# trivy rootfs /
-    2022-07-27T09:30:06.815Z	INFO	Need to update DB
-    2022-07-27T09:30:06.815Z	INFO	DB Repository: ghcr.io/aquasecurity/trivy-db
-    2022-07-27T09:30:06.815Z	INFO	Downloading DB...
-    33.25 MiB / 33.25 MiB [------------------------------] 100.00% 4.20 MiB p/s 8.1s
-    2022-07-27T09:30:21.756Z	INFO	Vulnerability scanning is enabled
-    2022-07-27T09:30:21.756Z	INFO	Secret scanning is enabled
-    2022-07-27T09:30:21.756Z	INFO	If your scanning is slow, please try '--scanners vuln' to disable secret scanning
-    2022-07-27T09:30:21.756Z	INFO	Please see also https://aquasecurity.github.io/trivy/v0.30.4/docs/secret/scanning/#recommendation for faster secret detection
-    2022-07-27T09:30:22.205Z	INFO	Detected OS: cbl-mariner
-    2022-07-27T09:30:22.205Z	INFO	Detecting CBL-Mariner vulnerabilities...
-    2022-07-27T09:30:22.205Z	INFO	Number of language-specific files: 0
-    
-    40ba9a55397c (cbl-mariner 2.0.20220527)
-    =======================================
-    Total: 33 (UNKNOWN: 0, LOW: 0, MEDIUM: 15, HIGH: 13, CRITICAL: 5)
-    ```
-
-[^1]: https://developers.redhat.com/products/rhel/ubi
-[^2]: https://github.com/GoogleContainerTools/distroless
-
-[arch]: https://security.archlinux.org/
-[alpine]: https://secdb.alpinelinux.org/
-[wolfi]: https://packages.wolfi.dev/os/security.json
-[chainguard]: https://packages.cgr.dev/chainguard/security.json
-[amazon]: https://alas.aws.amazon.com/
-[debian-tracker]: https://security-tracker.debian.org/tracker/
-[debian-oval]: https://www.debian.org/security/oval/
-[ubuntu]: https://ubuntu.com/security/cve
-[rhel-oval]: https://www.redhat.com/security/data/oval/v2/
-[rhel-api]: https://www.redhat.com/security/data/metrics/
-[alma]: https://errata.almalinux.org/
-[rocky]: https://download.rockylinux.org/pub/rocky/
-[oracle]: https://linux.oracle.com/security/oval/
-[suse]: http://ftp.suse.com/pub/projects/security/cvrf/
-[photon]: https://packages.vmware.com/photon/photon_cve_metadata/
-[mariner]: https://github.com/microsoft/CBL-MarinerVulnerabilityData/
-
-[cbl-mariner]: https://github.com/microsoft/CBL-Mariner
-
-[nvd]: https://nvd.nist.gov/

docs/docs/supply-chain/sbom.md

@@ -185,18 +185,6 @@ Trivy supports the following packages.
 - [OS packages][os_packages]
 - [Language-specific packages][language_packages]
 
-In addition to the above packages, Trivy also supports the following packages for generating SBOM.
-
-!!! note
-    These packages are not supported for vulnerability scanning.
-
-| Language | File              | Dependency location[^1] |
-|----------|-------------------|:-----------------------:|
-| Python   | conda package[^2] |            -            |
-| Swift    | Podfile.lock      |            -            |
-
-[^1]: Use `startline == 1 and endline == 1` for unsupported file types
-[^2]: `envs/*/conda-meta/*.json`
 
 ### Formats
 #### CycloneDX
@@ -754,7 +742,7 @@ Trivy automatically detects the SBOM files and uses them for scanning.
 It is enabled in the following targets.
 
 |     Target      | Enabled |
-|:---------------:|:-------:|
+| :-------------: | :-----: |
 | Container Image |    ✓    |
 |   Filesystem    |         |
 |     Rootfs      |    ✓    |
@@ -771,5 +759,5 @@ It is enabled in the following targets.
 [sbom]: https://cyclonedx.org/capabilities/sbom/
 [bov]: https://cyclonedx.org/capabilities/bov/
 
-[os_packages]: ../scanner/vulnerability/os.md
-[language_packages]: ../scanner/vulnerability/language/index.md
+[os_packages]: ../scanner/vulnerability.md#os-packages
+[language_packages]: ../scanner/vulnerability.md#language-specific-packages

docs/docs/supply-chain/vex.md

@@ -116,7 +116,7 @@ Total: 1 (UNKNOWN: 0, LOW: 1, MEDIUM: 0, HIGH: 0, CRITICAL: 0)
 CVE-2020-8911 is no longer shown as it is filtered out according to the given CycloneDX VEX document.
 
 ## OpenVEX
-Trivy also supports [OpenVEX](https://github.com/openvex/spec) that is designed to be minimal, compliant, interoperable, and embeddable.
+Trivy also supports [OpenVEX][openvex] that is designed to be minimal, compliant, interoperable, and embeddable.
 Since OpenVEX aims to be SBOM format agnostic, both CycloneDX and SPDX formats are available for use as input SBOMs in Trivy.
 
 The following steps are required:
@@ -134,24 +134,21 @@ $ trivy image --format spdx-json --output debian11.spdx.json debian:11
 
 ### Create the VEX
 Please see also [the example](https://github.com/openvex/examples).
-The product identifiers differ depending on the SBOM format the VEX references.
-
-- SPDX: [Package URL (PURL)](https://github.com/package-url/purl-spec)
-- CycloneDX: [BOM-Link](https://cyclonedx.org/capabilities/bomlink/)
+In Trivy, [the Package URL (PURL)][purl] is used as the product identifier.
 
 ```
-$ cat <<EOF > trivy.openvex
+$ cat <<EOF > debian11.openvex
 {
-  "@context": "https://openvex.dev/ns",
+  "@context": "https://openvex.dev/ns/v0.2.0",
   "@id": "https://openvex.dev/docs/public/vex-2e67563e128250cbcb3e98930df948dd053e43271d70dc50cfa22d57e03fe96f",
   "author": "Aqua Security",
-  "timestamp": "2023-01-16T19:07:16.853479631-06:00",
-  "version": "1",
+  "timestamp": "2023-08-29T19:07:16.853479631-06:00",
+  "version": 1,
   "statements": [
     {
-      "vulnerability": "CVE-2019-8457",
+      "vulnerability": {"name": "CVE-2019-8457"},
       "products": [
-        "pkg:deb/debian/libdb5.3@5.3.28+dfsg1-0.8?arch=arm64\u0026distro=debian-11.6"
+        {"@id": "pkg:deb/debian/libdb5.3@5.3.28+dfsg1-0.8"}
       ],
       "status": "not_affected",
       "justification": "vulnerable_code_not_in_execute_path"
@@ -161,15 +158,19 @@ $ cat <<EOF > trivy.openvex
 EOF
 ```
 
-In the above example, PURLs, located in `packages.externalRefs.referenceLocator` are used since the input SBOM format is SPDX.
+In the above example, PURLs, located in `packages.externalRefs.referenceLocator` in SPDX are used for the product identifier.
 
-As for CycloneDX BOM-Link, please reference [the CycloneDX section](#cyclonedx).
+!!! note
+    If a qualifier is specified in the PURL used as the product id in the VEX, the qualifier is compared.
+    Other qualifiers are ignored in the comparison.
+    `pkg:deb/debian/curl@7.50.3-1` in OpenVEX matches `pkg:deb/debian/curl@7.50.3-1?arch=i386`, 
+    while `pkg:deb/debian/curl@7.50.3-1?arch=amd64` does not match `pkg:deb/debian/curl@7.50.3-1?arch=i386`.
 
 ### Scan SBOM with VEX
 Provide the VEX when scanning the SBOM.
 
 ```
-$ trivy sbom debian11.spdx.json --vex trivy.openvex
+$ trivy sbom debian11.spdx.json --vex debian11.openvex
 ...
 2023-04-26T17:56:05.358+0300    INFO    Filtered out the detected vulnerability {"VEX format": "OpenVEX", "vulnerability-id": "CVE-2019-8457", "status": "not_affected", "justification": "vulnerable_code_not_in_execute_path"}
 
@@ -179,3 +180,6 @@ Total: 80 (UNKNOWN: 0, LOW: 58, MEDIUM: 6, HIGH: 16, CRITICAL: 0)
 ```
 
 CVE-2019-8457 is no longer shown as it is filtered out according to the given OpenVEX document.
+
+[openvex]: https://github.com/openvex/spec
+[purl]: https://github.com/package-url/purl-spec

docs/docs/target/container_image.md

@@ -22,7 +22,7 @@ By default, vulnerability and secret scanning are enabled, and you can configure
 It is enabled by default.
 You can simply specify your image name (and a tag).
 It detects known vulnerabilities in your container image.
-See [here](../scanner/vulnerability/index.md) for the detail.
+See [here](../scanner/vulnerability.md) for the detail.
 
 ```
 $ trivy image [YOUR_IMAGE_NAME]

docs/docs/target/filesystem.md

@@ -23,7 +23,7 @@ $ trivy fs ~/src/github.com/aquasecurity/trivy-ci-test/Pipfile.lock
 ### Vulnerabilities
 It is enabled by default.
 Trivy will look for vulnerabilities based on lock files such as Gemfile.lock and package-lock.json.
-See [here](../scanner/vulnerability/index.md) for the detail.
+See [here](../scanner/vulnerability.md) for the detail.
 
 ```
 $ trivy fs ~/src/github.com/aquasecurity/trivy-ci-test

docs/docs/target/kubernetes.md

@@ -3,21 +3,88 @@
 !!! warning "EXPERIMENTAL"
     This feature might change without preserving backwards compatibility.
 
-## CLI
-The Trivy K8s CLI allows you to scan your Kubernetes cluster for 
+Trivy can connect to your Kubernetes cluster and scan it for security issues using the `trivy k8s` command. This page covers the technical capabilities of Trivy Kubernetes scanning.
+Trivy can also be installed *inside* your cluster as a Kubernetes Operator, and continuously scan it. For more about this, please see the [Trivy Operator][https://aquasecurity.github.io/trivy-operator/] project.
 
+When scanning a Kubernetes cluster, Trivy differentiates between the following:
+
+1. Cluster infrastructure (e.g api-server, kubelet, addons)
+1. Cluster configuration (e.g Roles, ClusterRoles). 
+1. Application workloads (e.g nginx, postgresql).
+
+When scanning any of the above, the container image is scanned separately to the Kubernetes resource definition (the YAML manifest) that defines the resource.
+
+Container image is scanned for:
 - Vulnerabilities
 - Misconfigurations
-- Secrets
- 
-You can either run the CLI locally or integrate it into your CI/CD pipeline.
-The difference to the Trivy CLI is that the Trivy K8s CLI allows you to scan running workloads directly within your cluster.
+- Exposed secrets
 
-If you are looking for continuous cluster audit scanning, have a look at the Trivy K8s operator below.
+Kubernetes resource definition is scanned for:
+- Vulnerabilities - partially supported through [KBOM scanning](#KBOM)
+- Misconfigurations
+- Exposed secrets
 
-Trivy uses your local kubectl configuration to access the API server to list artifacts.
+## Kubernetes target configurations
 
-### Commands
+Trivy follows the behavior of the `kubectl` tool as much as possible.
+
+### Scope
+
+The command expects an argument that selects the scope of the scan (similarly to how `kubectl` expects an argument after `kubectl get`). This argument can be:
+1. A Kubernetes Kind. e.g `pod`, `deployment`, etc. 
+2. A Kubernetes Resource. e.g `pods/mypod`, etc.
+3. `all`. Scan common workload kinds, as listed [here](https://github.com/aquasecurity/trivy-kubernetes/blob/bf8cc2a00d9772e0aa271f06d375b936152b54b1/pkg/k8s/k8s.go#L296:L314)
+4. `cluster` scan the entire cluster including all namespaced resources and cluster level resources.
+
+Examples:
+
+```
+trivy k8s all
+trivy k8s pods
+trivy k8s deploy myapp
+trivy k8s pod/mypod
+trivy k8s pods,deploy
+trivy k8s cluster
+```
+
+Note that the scope argument must appear last in the command line, after any other flag.
+
+### Cluster
+
+By default Trivy will look for a [`kubeconfig` configuration file in the default location](https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/), and use the default cluster that is specified.  
+You can also specify a `kubeconfig` using the `--kubeconfig` flag:
+
+```
+trivy k8s --kubeconfig ~/.kube/config2
+```
+
+### Namespace
+
+By default Trivy will scan all namespaces (following `kubectl` behavior). To specify a namespace use the `--namespace` flag:
+
+```
+trivy k8s --kubeconfig ~/.kube/config2 --namespace default
+```
+### Node
+
+You can exclude specific nodes from the scan using the `--exclude-nodes` flag, which takes a label in the format `label-name:label-value` and excludes all matching nodes:
+
+```
+trivy k8s cluster --report summary --exclude-nodes kubernetes.io/arch:arm6
+```
+
+### Components types
+
+You can control what kinds of components are discovered using the `--components` flag:
+- `--components infra` will discover only cluster infrastructure components.
+- `--components workloads` will discover only application workloads.
+- If the flag is omitted: infra, workloads, and RBAC are discovered.
+
+## Reporting and filtering
+
+Since scanning an entire cluster for any security issue can be overwhelming, By default Trivy summarizes the results in a simple "summary" view.
+By scoping the scan on a specific resource, you can see the detailed report.
+You can always choose the report granularity using the `--report summary`/`--report all` flag.
 
 Scan a full cluster and generate a simple summary report:
 
@@ -27,60 +94,24 @@ $ trivy k8s --report=summary cluster
 
 ![k8s Summary Report](../../imgs/trivy-k8s.png)
 
-The summary report is the default. To get all of the detail the output contains, use `--report all`.
-
 Filter by severity:
 
 ```
-$ trivy k8s --severity=CRITICAL --report=all cluster
+trivy k8s --severity=CRITICAL --report=all cluster
 ```
 
 Filter by scanners (Vulnerabilities, Secrets or Misconfigurations):
 
 ```
-$ trivy k8s --scanners=secret --report=summary cluster
+trivy k8s --scanners=secret --report=summary cluster
 # or
-$ trivy k8s --scanners=config --report=summary cluster
+trivy k8s --scanners=config --report=summary cluster
 ```
 
-Scan a specific namespace:
+The supported output formats are `table`, which is the default, and `json`.
 
 ```
-$ trivy k8s -n kube-system --report=summary all
-```
-
-Use a specific kubeconfig file:
-
-```
-$ trivy k8s --kubeconfig ~/.kube/config2 -n kube-system --report=summary all
-```
-
-Scan a specific resource and get all the output:
-
-```
-$ trivy k8s deployment appname
-```
-
-Scan all deploys, or deploys and configmaps:
-
-```
-$ trivy k8s --report=summary deployment
-$ trivy k8s --report=summary deployment,configmaps
-```
-
-If you want to pass in flags before scanning specific workloads, you will have to do it before the resource name.
-For example, scanning a deployment in the app namespace of your Kubernetes cluster for critical vulnerabilities would be done through the following command:
-
-```
-$ trivy k8s -n app --severity=CRITICAL deployment/appname
-```
-This is specific to all Trivy CLI commands.
-
-The supported formats are `table`, which is the default, and `json`.
-To get a JSON output on a full cluster scan:
-
-```
-$ trivy k8s --format json -o results.json cluster
+trivy k8s --format json -o results.json cluster
 ```
 
 <details>
@@ -239,62 +270,10 @@ $ trivy k8s --format json -o results.json cluster
 
 </details>
 
-
-
-### Infra checks
-
-Trivy by default scans kubernetes infra components (apiserver, controller-manager, scheduler and etcd)
-if they exist under the `kube-system` namespace. For example, if you run a full cluster scan, or scan all
-components under `kube-system` with commands:
-
-```
-$ trivy k8s cluster --report summary # full cluster scan
-$ trivy k8s all -n kube-system --report summary # scan all components under kube-system
-```
-
-A table will be printed about misconfigurations found on kubernetes core components:
-
-```
-Summary Report for minikube
-┌─────────────┬──────────────────────────────────────┬─────────────────────────────┐
-│  Namespace  │               Resource               │ Kubernetes Infra Assessment │
-│             │                                      ├────┬────┬────┬─────┬────────┤
-│             │                                      │ C  │ H  │ M  │ L   │   U    │
-├─────────────┼──────────────────────────────────────┼────┼────┼────┼─────┼────────┤
-│ kube-system │ Pod/kube-apiserver-minikube          │    │    │ 1  │ 10  │        │
-│ kube-system │ Pod/kube-controller-manager-minikube │    │    │    │ 3   │        │
-│ kube-system │ Pod/kube-scheduler-minikube          │    │    │    │ 1   │        │
-└─────────────┴──────────────────────────────────────┴────┴────┴────┴─────┴────────┘
-Severities: C=CRITICAL H=HIGH M=MEDIUM L=LOW U=UNKNOWN
-```
-
-The infra checks are based on CIS Benchmarks recommendations for kubernetes.
-
-
-If you want filter only for the infra checks, you can use the flag `--components` along with the `--scanners=config`
-
-```
-$ trivy k8s cluster --report summary --components=infra --scanners=config # scan only infra
-```
-
-Or, to filter for all other checks besides the infra checks, you can:
-
-```
-$ trivy k8s cluster --report summary --components=workload --scanners=config # scan all components besides infra
-```
-
-If you wish to exclude nodes from being scanned, you can use the flag `--exclude-nodes` with the node labels
-
-```
-trivy k8s cluster --report summary --exclude-nodes kubernetes.io/arch:arm6
-```
-
-### Compliance
+## Compliance
 This section describes Kubernetes specific compliance reports.
 For an overview of Trivy's Compliance feature, including working with custom compliance, check out the [Compliance documentation](../compliance/compliance.md).
 
-#### Built in reports
-
 The following reports are available out of the box:
 
 | Compliance                                   | Name for command     | More info                                                                                                           |
@@ -304,55 +283,77 @@ The following reports are available out of the box:
 | Pod Security Standards, Baseline             | `k8s-pss-baseline`   | [Link](https://kubernetes.io/docs/concepts/security/pod-security-standards/#baseline)                               |
 | Pod  Security Standards, Restricted          | `k8s-pss-restricted` | [Link](https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted)                             |
 
-#### Examples
+Examples:
 
-Scan a full cluster and generate a compliance summary report:
+Scan the cluster for Kubernetes Pod Security Standards Baseline compliance:
 
 ```
-$ trivy k8s cluster --compliance=<compliance_id> --report summary
+trivy k8s cluster --compliance=k8s-pss-baseline --report summary
 ```
 
-***Note*** : The `Issues` column represent the total number of failed checks for this control.
-
-
-Get all of the detailed output for checks:
+Get the detailed report for checks:
 
 ```
-trivy k8s cluster --compliance=<compliance_id> --report all
+trivy k8s cluster --compliance=k8s-cis --report all
 ```
 
-Report result in JSON format:
+Get summary report in JSON format:
 
 ```
-trivy k8s cluster --compliance=<compliance_id> --report summary --format json
+trivy k8s cluster --compliance=k8s-cis --report summary --format json
 ```
 
+Get detailed report in JSON format:
+
 ```
-trivy k8s cluster --compliance=<compliance_id> --report all --format json
+trivy k8s cluster --compliance=k8s-cis --report all --format json
 ```
 
-## Operator
-Trivy has a native [Kubernetes Operator][operator] which continuously scans your Kubernetes cluster for security issues, and generates security reports as Kubernetes [Custom Resources][crd]. It does it by watching Kubernetes for state changes and automatically triggering scans in response to changes, for example initiating a vulnerability scan when a new Pod is created.
-
-> Kubernetes-native security toolkit. ([Documentation][trivy-operator]).
-
-<figure>
-  <figcaption>Workload reconcilers discover K8s controllers, manage scan jobs, and create VulnerabilityReport and ConfigAuditReport objects.</figcaption>
-</figure>
-
-[operator]: https://kubernetes.io/docs/concepts/extend-kubernetes/operator/
-[crd]: https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/
-[trivy-operator]: https://aquasecurity.github.io/trivy-operator/latest
-
-## SBOM
-
-Trivy supports the generation of Kubernetes Bill of Materials (KBOM) for kubernetes cluster control plane components, node components and addons.
-
 ## KBOM
 
-KBOM, Kubernetes Bill of Materials, is a manifest of all the important components that make up your Kubernetes cluster – Control plane components, Node Components, and Addons, including their versions and images. Which “api-server” version are you currently running? Which flavor of “kubelet” is running on each node? What kind of etcd or storage are you currently using? And most importantly – are there any vulnerabilities known to affect these components? These are all questions that KBOM can help you answer.
+KBOM, Kubernetes Bill of Materials, is a manifest of all the important components that make up your Kubernetes cluster – Control plane components, Node Components, and Addons, including their versions and images. Which “api-server” version are you currently running? Which flavor of "kubelet" is running on each node? What kind of etcd or storage are you currently using? And most importantly – are there any vulnerabilities known to affect these components? These are all questions that KBOM can help you answer.  
+For more background on KBOM, see [here](https://blog.aquasec.com/introducing-kbom-kubernetes-bill-of-materials).
+
 Trivy can generate KBOM in CycloneDX format:
 
 ```sh
-trivy k8s cluster --format cyclonedx
-```
+trivy k8s cluster --format cyclonedx --output mykbom.cdx.json
+```
+
+Trivy can also scan that generated KBOM (or any SBOM) for vulnerabilities:
+
+```sh
+trivy sbom mykbom.cdx.json
+```
+
+<details>
+<summary>Result</summary>
+
+```
+2023-09-28T22:52:25.707+0300    INFO    Vulnerability scanning is enabled
+ 2023-09-28T22:52:25.707+0300    INFO    Detected SBOM format: cyclonedx-json
+ 2023-09-28T22:52:25.717+0300    WARN    No OS package is detected. Make sure you haven't deleted any files that contain information about the installed packages.
+ 2023-09-28T22:52:25.717+0300    WARN    e.g. files under "/lib/apk/db/", "/var/lib/dpkg/" and "/var/lib/rpm"
+ 2023-09-28T22:52:25.717+0300    INFO    Detected OS: debian gnu/linux
+ 2023-09-28T22:52:25.717+0300    WARN    unsupported os : debian gnu/linux
+ 2023-09-28T22:52:25.717+0300    INFO    Number of language-specific files: 3
+ 2023-09-28T22:52:25.717+0300    INFO    Detecting kubernetes vulnerabilities...
+ 2023-09-28T22:52:25.718+0300    INFO    Detecting gobinary vulnerabilities...
+ Kubernetes (kubernetes)
+ Total: 2 (UNKNOWN: 0, LOW: 1, MEDIUM: 0, HIGH: 1, CRITICAL: 0)
+ ┌────────────────┬────────────────┬──────────┬────────┬───────────────────┬─────────────────────────────────┬──────────────────────────────────────────────────┐
+ │    Library     │ Vulnerability  │ Severity │ Status │ Installed Version │          Fixed Version          │                      Title                       │
+ ├────────────────┼────────────────┼──────────┼────────┼───────────────────┼─────────────────────────────────┼──────────────────────────────────────────────────┤
+ │ k8s.io/kubelet │ CVE-2021-25749 │ HIGH     │ fixed  │ 1.24.0            │ 1.22.14, 1.23.11, 1.24.5        │ runAsNonRoot logic bypass for Windows containers │
+ │                │                │          │        │                   │                                 │ https://avd.aquasec.com/nvd/cve-2021-25749       │
+ │                ├────────────────┼──────────┤        │                   ├─────────────────────────────────┼──────────────────────────────────────────────────┤
+ │                │ CVE-2023-2431  │ LOW      │        │                   │ 1.24.14, 1.25.9, 1.26.4, 1.27.1 │ Bypass of seccomp profile enforcement            │
+ │                │                │          │        │                   │                                 │ https://avd.aquasec.com/nvd/cve-2023-2431        │
+ └────────────────┴────────────────┴──────────┴────────┴───────────────────┴─────────────────────────────────┴──────────────────────────────────────────────────┘
+```
+
+</details>
+
+Find more in the [documentation for SBOM scanning](./sbom.md).
+
+Currently KBOM vulnerability matching works for plain Kubernetes distributions and does not work well for vendor variants, including some cloud managed distributions.

docs/docs/target/repository.md

@@ -34,13 +34,13 @@ $ trivy repo https://github.com/aquasecurity/trivy-ci-test
 ## Rationale
 `trivy repo` is  designed to scan code repositories, and it is intended to be used for scanning local/remote repositories in your machine or in your CI environment.
 Therefore, unlike container/VM image scanning, it targets lock files such as package-lock.json and does not target artifacts like JAR files, binary files, etc.
-See [here](../scanner/vulnerability/language/index.md) for the detail.
+See [here](../scanner/vulnerability.md#language-specific-packages) for the detail.
 
 ## Scanners
 ### Vulnerabilities
 It is enabled by default.
 Trivy will look for vulnerabilities based on lock files such as Gemfile.lock and package-lock.json.
-See [here](../scanner/vulnerability/index.md) for the detail.
+See [here](../scanner/vulnerability.md) for the detail.
 
 ```
 $ trivy repo ~/src/github.com/aquasecurity/trivy-ci-test
@@ -86,7 +86,7 @@ It is disabled by default and can be enabled with `--scanners config`.
 See [here](../scanner/misconfiguration/index.md) for the detail.
 
 ```shell
-$ trivy repo --scanners config [YOUR_REPO_URL]
+$ trivy repo --scanners config (REPO_PATH | REPO_URL)
 ```
 
 ### Secrets
@@ -94,7 +94,7 @@ It is enabled by default.
 See [here](../scanner/secret.md) for the detail.
 
 ```shell
-$ trivy repo [YOUR_REPO_URL]
+$ trivy repo (REPO_PATH | REPO_URL)
 ```
 
 ### Licenses
@@ -102,7 +102,7 @@ It is disabled by default.
 See [here](../scanner/license.md) for the detail.
 
 ```shell
-$ trivy repo --scanners license [YOUR_REPO_URL]
+$ trivy repo --scanners license (REPO_PATH | REPO_URL)
 ```
 
 ## SBOM generation

docs/docs/target/rootfs.md

@@ -12,4 +12,4 @@ $ trivy rootfs /path/to/rootfs
 !!! note
     Rootfs scanning works differently from the Filesystem scanning.
     You should use `trivy fs` to scan your local projects in CI/CD.
-    See [here](../scanner/vulnerability/index.md) for the differences.
+    See [here](../scanner/vulnerability.md) for the differences.

docs/docs/target/sbom.md

@@ -5,6 +5,7 @@ Trivy can take the following SBOM formats as an input and scan for vulnerabiliti
 - SPDX
 - SPDX JSON
 - CycloneDX-type attestation
+- [KBOM](./kubernetes.md#KBOM) in CycloneDX format
 
 To scan SBOM, you can use the `sbom` subcommand and pass the path to the SBOM.
 The input format is automatically detected.
@@ -107,3 +108,33 @@ Total: 2 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 0, CRITICAL: 2)
 │            │                │          │                   │               │                                                          │
 └────────────┴────────────────┴──────────┴───────────────────┴───────────────┴──────────────────────────────────────────────────────────┘
 ```
+
+## KBOM
+
+To read more about KBOM, see the [documentation for Kubernetes scanning](./kubernetes.md#KBOM).
+
+```shell
+ $ trivy k8s --format cyclonedx cluster -o kbom.json
+ $ trivy sbom kbom.json
+ 2023-09-28T22:52:25.707+0300    INFO    Vulnerability scanning is enabled
+ 2023-09-28T22:52:25.707+0300    INFO    Detected SBOM format: cyclonedx-json
+ 2023-09-28T22:52:25.717+0300    WARN    No OS package is detected. Make sure you haven't deleted any files that contain information about the installed packages.
+ 2023-09-28T22:52:25.717+0300    WARN    e.g. files under "/lib/apk/db/", "/var/lib/dpkg/" and "/var/lib/rpm"
+ 2023-09-28T22:52:25.717+0300    INFO    Detected OS: debian gnu/linux
+ 2023-09-28T22:52:25.717+0300    WARN    unsupported os : debian gnu/linux
+ 2023-09-28T22:52:25.717+0300    INFO    Number of language-specific files: 3
+ 2023-09-28T22:52:25.717+0300    INFO    Detecting kubernetes vulnerabilities...
+ 2023-09-28T22:52:25.718+0300    INFO    Detecting gobinary vulnerabilities...
+ Kubernetes (kubernetes)
+ Total: 2 (UNKNOWN: 0, LOW: 1, MEDIUM: 0, HIGH: 1, CRITICAL: 0)
+ ┌────────────────┬────────────────┬──────────┬────────┬───────────────────┬─────────────────────────────────┬──────────────────────────────────────────────────┐
+ │    Library     │ Vulnerability  │ Severity │ Status │ Installed Version │          Fixed Version          │                      Title                       │
+ ├────────────────┼────────────────┼──────────┼────────┼───────────────────┼─────────────────────────────────┼──────────────────────────────────────────────────┤
+ │ k8s.io/kubelet │ CVE-2021-25749 │ HIGH     │ fixed  │ 1.24.0            │ 1.22.14, 1.23.11, 1.24.5        │ runAsNonRoot logic bypass for Windows containers │
+ │                │                │          │        │                   │                                 │ https://avd.aquasec.com/nvd/cve-2021-25749       │
+ │                ├────────────────┼──────────┤        │                   ├─────────────────────────────────┼──────────────────────────────────────────────────┤
+ │                │ CVE-2023-2431  │ LOW      │        │                   │ 1.24.14, 1.25.9, 1.26.4, 1.27.1 │ Bypass of seccomp profile enforcement            │
+ │                │                │          │        │                   │                                 │ https://avd.aquasec.com/nvd/cve-2023-2431        │
+ └────────────────┴────────────────┴──────────┴────────┴───────────────────┴─────────────────────────────────┴──────────────────────────────────────────────────┘
+ ```
+ 

docs/docs/target/vm.md

@@ -144,7 +144,7 @@ Trivy supports VM image scanning for
 It is enabled by default.
 You can simply specify your VM image location.
 It detects known vulnerabilities in your VM image.
-See [here](../scanner/vulnerability/index.md) for the detail.
+See [here](../scanner/vulnerability.md) for the detail.
 
 ```
 $ trivy vm [YOUR_VM_IMAGE]

docs/ecosystem/cicd.md

@@ -9,6 +9,13 @@ GitHub Action for integrating Trivy into your GitHub pipeline
 
 👉 Get it at: <https://github.com/aquasecurity/trivy-action>
 
+## Azure DevOps (Official)
+[Azure Devops](https://azure.microsoft.com/en-us/products/devops/#overview) is Microsoft Azure cloud native CI/CD service.
+
+Trivy has a "Azure Devops Pipelines Task" for Trivy, that lets you easily introduce security scanning into your workflow, with an integrated Azure Devops UI.
+
+👉 Get it at: <https://github.com/aquasecurity/trivy-azure-pipelines-task>
+
 ### trivy-action (Community)
 
 GitHub Action to scan vulnerability using Trivy. If vulnerabilities are found by Trivy, it creates a GitHub Issue.
@@ -21,12 +28,11 @@ In this action, Trivy scans the dependency files such as package-lock.json and g
 
 👉 Get it at: <https://github.com/marketplace/actions/trivy-github-issues>
 
-## Azure DevOps (Official)
-[Azure Devops](https://azure.microsoft.com/en-us/products/devops/#overview) is Microsoft Azure cloud native CI/CD service.
+### Buildkite Plugin (Community)
 
-Trivy has a "Azure Devops Pipelines Task" for Trivy, that lets you easily introduce security scanning into your workflow, with an integrated Azure Devops UI.
+The trivy buildkite plugin provides a convenient mechanism for running the open-source trivy static analysis tool on your project. 
 
-👉 Get it at: <https://github.com/aquasecurity/trivy-azure-pipelines-task>
+👉 Get it at: https://github.com/equinixmetal-buildkite/trivy-buildkite-plugin
 
 ## Semaphore (Community)
 [Semaphore](https://semaphoreci.com/) is a CI/CD service.