docs(cli): added makefile and go file to create docs (#3930)

Co-authored-by: Teppei Fukuda <knqyf263@gmail.com>

.github/CODEOWNERS

@@ -2,12 +2,8 @@
 *   @knqyf263
 
 # Docs
-/docs/community/ @knqyf263 @AnaisUrlichs @itaysk
-/docs/ecosystem/ @knqyf263 @AnaisUrlichs @itaysk
-/docs/getting-started/ @knqyf263 @AnaisUrlichs @itaysk
-/docs/tutorials/ @knqyf263 @AnaisUrlichs @itaysk
+/docs/** @knqyf263 @AnaisUrlichs @itaysk
 /mkdocs.yml @knqyf263 @AnaisUrlichs @itaysk
-/docs/index.md @knqyf263 @AnaisUrlichs @itaysk
 /README.md @knqyf263 @AnaisUrlichs @itaysk
 
 # Helm chart

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

@@ -0,0 +1,53 @@
+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/canary.yaml

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

.github/workflows/release.yaml

@@ -24,7 +24,7 @@ jobs:
           fetch-depth: 0
 
       - name: Restore Trivy binaries from cache
-        uses: actions/cache@v3.2.2
+        uses: actions/cache@v3.2.6
         with:
           path: dist/
           key: ${{ runner.os }}-bins-${{github.workflow}}-${{github.sha}}

.github/workflows/reusable-release.yaml

@@ -87,7 +87,7 @@ jobs:
       ## only for canary build
       - name: Build and push
         if: ${{ inputs.goreleaser_config == 'goreleaser-canary.yml' }}
-        uses: docker/build-push-action@v3
+        uses: docker/build-push-action@v4
         with:
           platforms: linux/amd64, linux/arm64
           file: ./Dockerfile.canary # path to Dockerfile
@@ -99,7 +99,7 @@ jobs:
             public.ecr.aws/aquasecurity/trivy:canary
 
       - name: Cache Trivy binaries
-        uses: actions/cache@v3.2.2
+        uses: actions/cache@v3.2.6
         with:
           path: dist/
           # use 'github.sha' to create a unique cache folder for each run.

.github/workflows/roadmap.yaml

@@ -11,7 +11,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       # 'kind/feature' AND 'priority/backlog' labels -> 'Backlog' column
-      - uses: actions/add-to-project@v0.4.0 # add new issue to project
+      - uses: actions/add-to-project@v0.4.1 # add new issue to project
         with:
           project-url: https://github.com/orgs/aquasecurity/projects/25
           github-token: ${{ secrets.ORG_PROJECT_TOKEN }}
@@ -28,7 +28,7 @@ jobs:
           field-values: Backlog
 
       # 'kind/feature' AND 'priority/important-longterm' labels -> 'Important (long-term)' column
-      - uses: actions/add-to-project@v0.4.0 # add new issue to project
+      - uses: actions/add-to-project@v0.4.1 # add new issue to project
         with:
           project-url: https://github.com/orgs/aquasecurity/projects/25
           github-token: ${{ secrets.ORG_PROJECT_TOKEN }}
@@ -45,7 +45,7 @@ jobs:
           field-values: Important (long-term)
 
       # 'kind/feature' AND 'priority/important-soon' labels -> 'Important (soon)' column
-      - uses: actions/add-to-project@v0.4.0 # add new issue to project
+      - uses: actions/add-to-project@v0.4.1 # add new issue to project
         with:
           project-url: https://github.com/orgs/aquasecurity/projects/25
           github-token: ${{ secrets.ORG_PROJECT_TOKEN }}
@@ -62,7 +62,7 @@ jobs:
           field-values: Important (soon)
 
       # 'kind/feature' AND 'priority/critical-urgent' labels -> 'Urgent' column
-      - uses: actions/add-to-project@v0.4.0 # add new issue to project
+      - uses: actions/add-to-project@v0.4.1 # add new issue to project
         with:
           project-url: https://github.com/orgs/aquasecurity/projects/25
           github-token: ${{ secrets.ORG_PROJECT_TOKEN }}

.github/workflows/scan.yaml

@@ -13,11 +13,11 @@ jobs:
         uses: actions/checkout@v3
 
       - name: Run Trivy vulnerability scanner and create GitHub issues
-        uses: knqyf263/trivy-issue-action@v0.0.4
+        uses: knqyf263/trivy-issue-action@v0.0.5
         with:
           assignee: knqyf263
           severity: CRITICAL
-          skip-dirs: integration,examples
+          skip-dirs: integration,examples,pkg
           label: kind/security
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/semantic-pr.yaml

@@ -69,8 +69,9 @@ jobs:
             java
             go
             c
-            c++
+            c\+\+
             elixir
+            dart
 
             os
             lang

.github/workflows/test-docs.yaml

@@ -0,0 +1,28 @@
+name: Test docs
+on:
+  pull_request:
+    paths:
+      - 'docs/**'
+      - 'mkdocs.yml'
+jobs:
+  build-documents:
+    name: Documentation Test
+    runs-on: ubuntu-latest
+    steps:
+    - name: Checkout
+      uses: actions/checkout@v3
+      with:
+        fetch-depth: 0
+        persist-credentials: true
+    - uses: actions/setup-python@v4
+      with:
+        python-version: 3.x
+    - name: Install dependencies
+      run: |
+        pip install -r docs/build/requirements.txt
+    - name: Configure the git user
+      run: |
+        git config user.name "knqyf263"
+        git config user.email "knqyf263@gmail.com"
+    - name: Deploy the dev documents
+      run: mike deploy test

.github/workflows/test.yaml

@@ -4,11 +4,16 @@ on:
     branches:
       - main
     paths-ignore:
-      - '*.md'
+      - '**.md'
       - 'docs/**'
       - 'mkdocs.yml'
       - 'LICENSE'
   pull_request:
+      paths-ignore:
+      - '**.md'
+      - 'docs/**'
+      - 'mkdocs.yml'
+      - 'LICENSE'
 jobs:
   test:
     name: Test
@@ -22,7 +27,7 @@ jobs:
       - name: Set up Go
         uses: actions/setup-go@v3
         with:
-          go-version-file: go.mod
+          go-version: oldstable
 
       - name: go mod tidy
         run: |
@@ -34,20 +39,20 @@ jobs:
         if: matrix.operating-system == 'ubuntu-latest'
 
       - name: Lint
-        uses: golangci/golangci-lint-action@v3.3.0
+        uses: golangci/golangci-lint-action@v3.4.0
         with:
-          version: v1.49
+          version: v1.52
           args: --deadline=30m
           skip-cache: true # https://github.com/golangci/golangci-lint-action/issues/244#issuecomment-1052197778
         if: matrix.operating-system == 'ubuntu-latest'
 
-      # Install tools
-      - uses: aquaproj/aqua-installer@v1.2.0
+      - name: Install tools
+        uses: aquaproj/aqua-installer@v2.0.2
         with:
           aqua_version: v1.25.0
 
       - name: Run unit tests
-        run: make test
+        run: mage test:unit
 
   integration:
     name: Integration Test
@@ -61,8 +66,13 @@ jobs:
         with:
           go-version-file: go.mod
 
+      - name: Install tools
+        uses: aquaproj/aqua-installer@v2.0.2
+        with:
+          aqua_version: v1.25.0
+
       - name: Run integration tests
-        run: make test-integration
+        run: mage test:integration
 
   module-test:
     name: Module Integration Test
@@ -76,15 +86,15 @@ jobs:
         with:
           go-version-file: go.mod
 
-      # Install tools
-      - uses: aquaproj/aqua-installer@v1.1.2
+      - name: Install tools
+        uses: aquaproj/aqua-installer@v2.0.2
         with:
           aqua_version: v1.25.0
 
       - name: Run module integration tests
         shell: bash
         run: |
-          make test-module-integration
+          mage test:module
 
   build-test:
     name: Build Test
@@ -116,24 +126,3 @@ jobs:
         version: v1.4.1
         args: release --skip-sign --snapshot --rm-dist --skip-publish --timeout 90m
 
-  build-documents:
-    name: Documentation Test
-    runs-on: ubuntu-latest
-    steps:
-    - name: Checkout
-      uses: actions/checkout@v3
-      with:
-        fetch-depth: 0
-        persist-credentials: true
-    - uses: actions/setup-python@v4
-      with:
-        python-version: 3.x
-    - name: Install dependencies
-      run: |
-        pip install -r docs/build/requirements.txt
-    - name: Configure the git user
-      run: |
-        git config user.name "knqyf263"
-        git config user.email "knqyf263@gmail.com"
-    - name: Deploy the dev documents
-      run: mike deploy test

.github/workflows/vm-test.yaml

@@ -9,6 +9,11 @@ on:
       - 'pkg/fanal/artifact/vm/**'
       - 'integration/vm_test.go'
   pull_request:
+    paths:
+      - 'pkg/fanal/vm/**'
+      - 'pkg/fanal/walker/vm.go'
+      - 'pkg/fanal/artifact/vm/**'
+      - 'integration/vm_test.go'
 
 jobs:
   vm-test:
@@ -22,6 +27,10 @@ jobs:
         uses: actions/setup-go@v3
         with:
           go-version-file: go.mod
+      - name: Install tools
+        uses: aquaproj/aqua-installer@v2.0.2
+        with:
+          aqua_version: v1.25.0
       - name: Run vm integration tests
         run: |
-          make test-vm-integration
+          mage test:vm

.gitignore

@@ -34,4 +34,7 @@ integration/testdata/fixtures/vm-images
 dist
 
 # WebAssembly
-*.wasm
+*.wasm
+
+# Signing
+gpg.key

.golangci.yaml

@@ -21,6 +21,7 @@ linters-settings:
     local-prefixes: github.com/aquasecurity
   gosec:
     excludes:
+      - G101
       - G114
       - G204
       - G402

Dockerfile

@@ -1,4 +1,4 @@
-FROM alpine:3.17.0
+FROM alpine:3.17.2
 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.17.0
+FROM alpine:3.17.2
 RUN apk --no-cache add ca-certificates git
 
 # binaries were created with GoReleaser

Dockerfile.protoc

@@ -10,3 +10,6 @@ RUN curl --retry 5 -OL https://github.com/protocolbuffers/protobuf/releases/down
 
 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
+
+ENV TRIVY_PROTOC_CONTAINER=true

Makefile

@@ -1,133 +0,0 @@
-VERSION := $(patsubst v%,%,$(shell git describe --tags --always)) #Strips the v prefix from the tag
-LDFLAGS := -ldflags "-s -w -X=main.version=$(VERSION)"
-
-GOPATH := $(firstword $(subst :, ,$(shell go env GOPATH)))
-GOBIN := $(GOPATH)/bin
-GOSRC := $(GOPATH)/src
-
-TEST_MODULE_DIR := pkg/module/testdata
-TEST_MODULE_SRCS := $(wildcard $(TEST_MODULE_DIR)/*/*.go)
-TEST_MODULES := $(patsubst %.go,%.wasm,$(TEST_MODULE_SRCS))
-
-EXAMPLE_MODULE_DIR := examples/module
-EXAMPLE_MODULE_SRCS := $(wildcard $(EXAMPLE_MODULE_DIR)/*/*.go)
-EXAMPLE_MODULES := $(patsubst %.go,%.wasm,$(EXAMPLE_MODULE_SRCS))
-
-MKDOCS_IMAGE := aquasec/mkdocs-material:dev
-MKDOCS_PORT := 8000
-
-u := $(if $(update),-u)
-
-# Tools
-$(GOBIN)/wire:
-	go install github.com/google/wire/cmd/wire@v0.5.0
-
-$(GOBIN)/crane:
-	go install github.com/google/go-containerregistry/cmd/crane@v0.9.0
-
-$(GOBIN)/golangci-lint:
-	curl -sfL https://raw.githubusercontent.com/golangci/golangci-lint/master/install.sh| sh -s -- -b $(GOBIN) v1.49.0
-
-$(GOBIN)/labeler:
-	go install github.com/knqyf263/labeler@latest
-
-$(GOBIN)/easyjson:
-	go install github.com/mailru/easyjson/...@v0.7.7
-
-.PHONY: wire
-wire: $(GOBIN)/wire
-	wire gen ./pkg/commands/... ./pkg/rpc/...
-
-.PHONY: mock
-mock: $(GOBIN)/mockery
-	mockery -all -inpkg -case=snake -dir $(DIR)
-
-.PHONY: deps
-deps:
-	go get ${u} -d
-	go mod tidy
-
-.PHONY: generate-test-modules
-generate-test-modules: $(TEST_MODULES)
-
-# Compile WASM modules for unit and integration tests
-%.wasm:%.go
-	@if !(type "tinygo" > /dev/null 2>&1); then \
-		echo "Need to install TinyGo. Follow https://tinygo.org/getting-started/install/"; \
-		exit 1; \
-	fi
-	go generate $<
-
-# Run unit tests
-.PHONY: test
-test: $(TEST_MODULES)
-	go test -v -short -coverprofile=coverage.txt -covermode=atomic ./...
-
-integration/testdata/fixtures/images/*.tar.gz: $(GOBIN)/crane
-	mkdir -p integration/testdata/fixtures/images/
-	integration/scripts/download-images.sh
-
-# Run integration tests
-.PHONY: test-integration
-test-integration: integration/testdata/fixtures/images/*.tar.gz
-	go test -v -tags=integration ./integration/... ./pkg/fanal/test/integration/...
-
-# Run WASM integration tests
-.PHONY: test-module-integration
-test-module-integration: integration/testdata/fixtures/images/*.tar.gz $(EXAMPLE_MODULES)
-	go test -v -tags=module_integration ./integration/...
-
-# Run VM integration tests
-.PHONY: test-vm-integration
-test-vm-integration: integration/testdata/fixtures/vm-images/*.img.gz
-	go test -v -tags=vm_integration ./integration/...
-
-integration/testdata/fixtures/vm-images/*.img.gz:
-	integration/scripts/download-vm-images.sh
-
-
-.PHONY: lint
-lint: $(GOBIN)/golangci-lint
-	$(GOBIN)/golangci-lint run --timeout 5m
-
-.PHONY: fmt
-fmt:
-	find ./ -name "*.proto" | xargs clang-format -i
-
-.PHONY: build
-build:
-	go build $(LDFLAGS) ./cmd/trivy
-
-.PHONY: protoc
-protoc:
-	docker build -t trivy-protoc - < Dockerfile.protoc
-	docker run --rm -it -v ${PWD}:/app -w /app trivy-protoc make _$@
-
-_protoc:
-	for path in `find ./rpc/ -name "*.proto" -type f`; do \
-		protoc --twirp_out=. --twirp_opt=paths=source_relative --go_out=. --go_opt=paths=source_relative $${path} || exit; \
-	done
-
-.PHONY: install
-install:
-	go install $(LDFLAGS) ./cmd/trivy
-
-.PHONY: clean
-clean:
-	rm -rf integration/testdata/fixtures/images
-
-# Create labels on GitHub
-.PHONY: label
-label: $(GOBIN)/labeler
-	labeler apply misc/triage/labels.yaml -r aquasecurity/trivy -l 5
-
-# Run MkDocs development server to preview the documentation page
-.PHONY: mkdocs-serve
-mkdocs-serve:
-	docker build -t $(MKDOCS_IMAGE) -f docs/build/Dockerfile docs/build
-	docker run --name mkdocs-serve --rm -v $(PWD):/docs -p $(MKDOCS_PORT):8000 $(MKDOCS_IMAGE)
-
-# Generate JSON marshaler/unmarshaler for TinyGo/WebAssembly as TinyGo doesn't support encoding/json.
-.PHONY: easyjson
-easyjson: $(GOBIN)/easyjson
-	easyjson pkg/module/serialize/types.go

README.md

@@ -31,29 +31,35 @@ Scanners (what Trivy can find there):
 - Sensitive information and secrets
 - Software licenses
 
+To learn more, go to the [Trivy homepage][homepage] for feature highlights, or to the [Documentation site][docs] for detailed information.
+
 ## Quick Start
 
 ### Get Trivy
 
-Trivy is available in most common distribution methods. The full list of installation options is available in the [Installation] page, here are a few popular options:
+Trivy is available in most common distribution channels. The full list of installation options is available in the [Installation] page. Here are a few popular examples:
 
-- `apt-get install trivy`
-- `yum install trivy`
-- `brew install aquasecurity/trivy/trivy`
+- `brew install trivy`
 - `docker run aquasec/trivy`
 - Download binary from <https://github.com/aquasecurity/trivy/releases/latest/>
+- See [Installation] for more
 
-Trivy is integrated with many popular platforms and applications. The full list of integrations is available in the [Ecosystem] page. Here are a few popular options:
+Trivy is integrated with many popular platforms and applications. The complete list of integrations is available in the [Ecosystem] page. Here are a few popular examples:
 
 - [GitHub Actions](https://github.com/aquasecurity/trivy-action)
-- [CircleCI](https://circleci.com/developer/orbs/orb/fifteen5/trivy-orb)
 - [Kubernetes operator](https://github.com/aquasecurity/trivy-operator)
 - [VS Code plugin](https://github.com/aquasecurity/trivy-vscode-extension)
+- See [Ecosystem] for more
+
+### Canary builds
+There are canary builds ([Docker Hub](https://hub.docker.com/r/aquasec/trivy/tags?page=1&name=canary), [GitHub](https://github.com/aquasecurity/trivy/pkgs/container/trivy/75776514?tag=canary), [ECR](https://gallery.ecr.aws/aquasecurity/trivy#canary) images and [binaries](https://github.com/aquasecurity/trivy/actions/workflows/canary.yaml)) as generated every push to main branch.
+
+Please be aware: canary builds might have critical bugs, it's not recommended for use in production.
 
 ### General usage
 
 ```bash
-trivy <target> [--security-checks <scanner1,scanner2>] <subject>
+trivy <target> [--scanners <scanner1,scanner2>] <subject>
 ```
 
 Examples:
@@ -70,7 +76,7 @@ https://user-images.githubusercontent.com/1161307/171013513-95f18734-233d-45d3-a
 </details>
 
 ```bash
-trivy fs --security-checks vuln,secret,config myproject/
+trivy fs --scanners vuln,secret,config myproject/
 ```
 
 <details>
@@ -91,36 +97,6 @@ trivy k8s --report summary cluster
 
 </details>
 
-## Highlights
-
-- Comprehensive vulnerability detection
-    - OS packages (Alpine Linux, Red Hat Universal Base Image, Red Hat Enterprise Linux, CentOS, AlmaLinux, Rocky Linux, CBL-Mariner, Oracle Linux, Debian, Ubuntu, Amazon Linux, openSUSE Leap, SUSE Enterprise Linux, Photon OS and Distroless)
-    - **Language-specific packages** (Bundler, Composer, Pipenv, Poetry, npm, yarn, Cargo, NuGet, Maven, and Go)
-    - High accuracy, especially [Alpine Linux][alpine] and RHEL/CentOS
-- Supply chain security (SBOM support)
-    - Support CycloneDX
-    - Support SPDX
-    - Generating and Scanning SBOM
-    - Leveraging in-toto attestations
-    - Integrated with [Sigstore]
-- Misconfiguration detection (IaC scanning) 
-    - Wide variety of security checks are provided **out of the box**
-    - Kubernetes, Docker, Terraform, and more
-    - User-defined policies using [OPA Rego][rego]
-- Secret detection
-    - A wide variety of built-in rules are provided **out of the box**
-    - User-defined patterns
-    - Efficient scanning of container images
-- Simple
-    - Available in apt, yum, brew, dockerhub
-    - **No pre-requisites** such as a database, system libraries, or eny environmental requirements. The binary runs anywhere.
-    - The first scan will finish within 10 seconds (depending on your network). Consequent scans will finish instantaneously.
-- Fits your workflow
-    - **Great for CI** such as GitHub Actions, Jenkins, GitLab CI, etc.
-    - Available as extension for IDEs such as vscode, jetbrains, vim
-    - Available as extension for Docker Desktop, Rancher Desktop
-    - See [Ecosystem] section in the documentation.
-
 ## FAQ
 
 ### How to pronounce the name "Trivy"?
@@ -143,6 +119,7 @@ Contact us about any matter by opening a GitHub Discussion [here][discussions]
 [docker-pulls]: https://img.shields.io/docker/pulls/aquasec/trivy?logo=docker&label=docker%20pulls%20%2F%20trivy
 [license]: https://github.com/aquasecurity/trivy/blob/main/LICENSE
 [license-img]: https://img.shields.io/badge/License-Apache%202.0-blue.svg
+[homepage]: https://trivy.dev
 [docs]: https://aquasecurity.github.io/trivy
 [pronunciation]: #how-to-pronounce-the-name-trivy
 

aqua.yaml

@@ -6,3 +6,4 @@ registries:
   ref: v3.106.0 # renovate: depName=aquaproj/aqua-registry
 packages:
 - name: tinygo-org/tinygo@v0.26.0
+- name: magefile/mage@v1.14.0

ci/deploy-rpm.sh

@@ -1,18 +1,21 @@
 #!/bin/bash
 
+TRIVY_VERSION=$(find dist/ -type f -name "*64bit.rpm" -printf "%f\n" | head -n1 | sed -nre 's/^[^0-9]*(([0-9]+\.)*[0-9]+).*/\1/p')
+
 function create_rpm_repo () {
         version=$1
         rpm_path=rpm/releases/${version}/x86_64
 
-        RPM_EL=$(find ../dist/ -type f -name "*64bit.rpm" -printf "%f\n" | head -n1 | sed -e "s/_/-/g" -e "s/-Linux/.el$version/" -e "s/-64bit/.x86_64/")
-        echo $RPM_EL
-
         mkdir -p $rpm_path
-        cp ../dist/*64bit.rpm ${rpm_path}/${RPM_EL}
+        cp ../dist/*64bit.rpm ${rpm_path}/
 
-        createrepo_c --update $rpm_path
+        createrepo_c -u https://github.com/aquasecurity/trivy/releases/download/ --location-prefix="v"$TRIVY_VERSION --update $rpm_path
+
+        rm ${rpm_path}/*64bit.rpm
 }
 
+echo "Create RPM releases for Trivy v$TRIVY_VERSION"
+
 cd trivy-repo
 
 VERSIONS=(5 6 7 8 9)
@@ -22,6 +25,5 @@ for version in ${VERSIONS[@]}; do
 done
 
 git add .
-git commit -m "Update rpm packages"
+git commit -m "Update rpm packages for Trivy v$TRIVY_VERSION"
 git push origin main
-

cmd/trivy/main.go

@@ -9,6 +9,8 @@ import (
 	"github.com/aquasecurity/trivy/pkg/commands"
 	"github.com/aquasecurity/trivy/pkg/log"
 	"github.com/aquasecurity/trivy/pkg/plugin"
+
+	_ "modernc.org/sqlite" // sqlite driver for RPM DB and Java DB
 )
 
 var (

docs/community/contribute/pr.md

@@ -9,11 +9,59 @@ Thank you for taking interest in contributing to Trivy!
 1. Your PR is more likely to be accepted if it includes tests (We have not historically been very strict about tests, but we would like to improve this!).
 1. If your PR affects the user experience in some way, please update the README.md and the CLI help accordingly.
 
-### Title
+## Development
+Install the necessary tools for development by following their respective installation instructions.
+
+- [Go](https://go.dev/doc/install)
+- [Mage](https://magefile.org/)
+
+### Build
+After making changes to the Go source code, build the project with the following command:
+
+```shell
+$ mage build
+$ ./trivy -h
+```
+
+### Lint
+You must pass the linter checks:
+
+```shell
+$ mage lint
+```
+
+Additionally, you need to have run `go mod tidy`, so execute the following command as well:
+
+```shell
+$ mage tidy
+```
+
+### Unit tests
+Your PR must pass all the unit tests. You can test it as below.
+
+```
+$ mage test:unit
+```
+
+### Integration tests
+Your PR must pass all the integration tests. You can test it as below.
+
+```
+$ mage test:integration
+```
+
+### Documentation
+You can build the documents as below and view it at http://localhost:8000.
+
+```
+$ mage docs:serve
+```
+
+## Title
 It is not that strict, but we use the title conventions in this repository.
 Each commit message doesn't have to follow the conventions as long as it is clear and descriptive since it will be squashed and merged.
 
-#### Format of the title
+### Format of the title
 
 ```
 <type>(<scope>): <subject>
@@ -81,6 +129,7 @@ language:
 - java
 - go
 - elixir
+- dart
 
 vuln:
 
@@ -121,7 +170,7 @@ others:
 
 The `<scope>` can be empty (e.g. if the change is a global or difficult to assign to a single component), in which case the parentheses are omitted.
 
-#### Example titles
+### Example titles
 
 ```
 feat(alma): add support for AlmaLinux
@@ -142,33 +191,15 @@ chore(deps): bump go.uber.org/zap from 1.19.1 to 1.20.0
 **NOTE**: please do not use `chore(deps): update fanal` and something like that if you add new features or fix bugs in Trivy-related projects.
 The PR title should describe what the PR adds or fixes even though it just updates the dependency in Trivy.
 
-### Unit tests
-Your PR must pass all the unit tests. You can test it as below.
+## Commits
 
-```
-$ make test
-```
-
-### Integration tests
-Your PR must pass all the integration tests. You can test it as below.
-
-```
-$ make test-integration
-```
-
-### Documentation
-You can build the documents as below and view it at http://localhost:8000.
-
-```
-$ make mkdocs-serve
-```
 
 ## Understand where your pull request belongs
 
 Trivy is composed of several repositories that work together:
 
 - [Trivy](https://github.com/aquasecurity/trivy) is the client-side, user-facing, command line tool.
-- [vuln-list](https://github.com/aquasecurity/vuln-list) is a vulnerabilities database, aggregated from different sources, and normalized for easy consumption. Think of this as the "server" side of the trivy command line tool. **There should be no pull requests to this repo**
+- [vuln-list](https://github.com/aquasecurity/vuln-list) is a vulnerability database, aggregated from different sources, and normalized for easy consumption. Think of this as the "server" side of the trivy command line tool. **There should be no pull requests to this repo**
 - [vuln-list-update](https://github.com/aquasecurity/vuln-list-update) is the code that maintains the vuln-list database.
 - [trivy-db](https://github.com/aquasecurity/trivy-db) maintains the vulnerability database pulled by Trivy CLI.
 - [go-dep-parser](https://github.com/aquasecurity/go-dep-parser) is a library for parsing lock files such as package-lock.json and Gemfile.lock.

docs/docs/advanced/air-gap.md

@@ -5,6 +5,8 @@ Trivy can be used in air-gapped environments. Note that an allowlist is [here][a
 ## Air-Gapped Environment for vulnerabilities
 
 ### Download the vulnerability database
+At first, you need to download the vulnerability database for use in air-gapped environments.
+
 === "Trivy"
 
     ```
@@ -15,7 +17,6 @@ Trivy can be used in air-gapped environments. Note that an allowlist is [here][a
     ```
 
 === "oras >= v0.13.0"
-    At first, you need to download the vulnerability database for use in air-gapped environments.
     Please follow [oras installation instruction][oras].
 
     Download `db.tar.gz`:
@@ -25,7 +26,6 @@ Trivy can be used in air-gapped environments. Note that an allowlist is [here][a
     ```
 
 === "oras < v0.13.0"
-    At first, you need to download the vulnerability database for use in air-gapped environments.
     Please follow [oras installation instruction][oras].
 
     Download `db.tar.gz`:
@@ -34,41 +34,95 @@ Trivy can be used in air-gapped environments. Note that an allowlist is [here][a
     $ oras pull -a ghcr.io/aquasecurity/trivy-db:2
     ```
 
-### Transfer the DB file into the air-gapped environment
+### Download the Java index database[^1]
+Java users also need to download the Java index database for use in air-gapped environments.
+
+!!! note
+    You container image may contain JAR files even though you don't use Java directly.
+    In that case, you also need to download the Java index database.
+
+=== "Trivy"
+
+    ```
+    TRIVY_TEMP_DIR=$(mktemp -d)
+    trivy --cache-dir $TRIVY_TEMP_DIR image --download-java-db-only
+    tar -cf ./javadb.tar.gz -C $TRIVY_TEMP_DIR/java-db metadata.json trivy-java.db
+    rm -rf $TRIVY_TEMP_DIR
+    ```
+=== "oras >= v0.13.0"
+    Please follow [oras installation instruction][oras].
+
+    Download `javadb.tar.gz`:
+
+    ```
+    $ oras pull ghcr.io/aquasecurity/trivy-java-db:1
+    ```
+
+=== "oras < v0.13.0"
+    Please follow [oras installation instruction][oras].
+
+    Download `javadb.tar.gz`:
+
+    ```
+    $ oras pull -a ghcr.io/aquasecurity/trivy-java-db:1
+    ```
+
+
+### Transfer the DB files into the air-gapped environment
 The way of transfer depends on the environment.
 
-```
-$ rsync -av -e ssh /path/to/db.tar.gz [user]@[host]:dst
-```
+=== "Vulnerability db"
+    ```
+    $ rsync -av -e ssh /path/to/db.tar.gz [user]@[host]:dst
+    ```
 
-### Put the DB file in Trivy's cache directory
-You have to know where to put the DB file. The following command shows the default cache directory.
+=== "Java index db[^1]"
+    ```
+    $ rsync -av -e ssh /path/to/javadb.tar.gz [user]@[host]:dst
+    ```
+
+### Put the DB files in Trivy's cache directory
+You have to know where to put the DB files. The following command shows the default cache directory.
 
 ```
 $ ssh user@host
 $ trivy -h | grep cache
    --cache-dir value  cache directory (default: "/home/myuser/.cache/trivy") [$TRIVY_CACHE_DIR]
 ```
+=== "Vulnerability db"
+    Put the DB file in the cache directory + `/db`.
+    
+    ```
+    $ mkdir -p /home/myuser/.cache/trivy/db
+    $ cd /home/myuser/.cache/trivy/db
+    $ tar xvf /path/to/db.tar.gz -C /home/myuser/.cache/trivy/db
+    x trivy.db
+    x metadata.json
+    $ rm /path/to/db.tar.gz
+    ```
 
-Put the DB file in the cache directory + `/db`.
+=== "Java index db[^1]"
+    Put the DB file in the cache directory + `/java-db`.
+
+    ```
+    $ mkdir -p /home/myuser/.cache/trivy/java-db
+    $ cd /home/myuser/.cache/trivy/java-db
+    $ tar xvf /path/to/javadb.tar.gz -C /home/myuser/.cache/trivy/java-db
+    x trivy-java.db
+    x metadata.json
+    $ rm /path/to/javadb.tar.gz
+    ```
+
+
+
+In an air-gapped environment it is your responsibility to update the Trivy databases on a regular basis, so that the scanner can detect recently-identified vulnerabilities. 
+
+### Run Trivy with the specific flags.
+In an air-gapped environment, you have to specify `--skip-db-update` and `--skip-java-db-update`[^1] so that Trivy doesn't attempt to download the latest database files.
+In addition, if you want to scan `pom.xml` dependencies, you need to specify `--offline-scan` since Trivy tries to issue API requests for scanning Java applications by default.
 
 ```
-$ mkdir -p /home/myuser/.cache/trivy/db
-$ cd /home/myuser/.cache/trivy/db
-$ tar xvf /path/to/db.tar.gz -C /home/myuser/.cache/trivy/db
-x trivy.db
-x metadata.json
-$ rm /path/to/db.tar.gz
-```
-
-In an air-gapped environment it is your responsibility to update the Trivy database on a regular basis, so that the scanner can detect recently-identified vulnerabilities. 
-
-### Run Trivy with `--skip-update` and `--offline-scan` option
-In an air-gapped environment, specify `--skip-update` so that Trivy doesn't attempt to download the latest database file.
-In addition, if you want to scan Java dependencies such as JAR and pom.xml, you need to specify `--offline-scan` since Trivy tries to issue API requests for scanning Java applications by default.
-
-```
-$ trivy image --skip-update --offline-scan alpine:3.12
+$ trivy image --skip-db-update --skip-java-db-update --offline-scan alpine:3.12
 ```
 
 ## Air-Gapped Environment for misconfigurations
@@ -84,3 +138,5 @@ $ 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](../vulnerability/languages/java.md)

docs/docs/advanced/container/containerd.md

@@ -1,29 +0,0 @@
-# containerd
-
-!!! warning "EXPERIMENTAL"
-    This feature might change without preserving backwards compatibility.
-
-Scan your image in [containerd][containerd] running locally.
-
-```bash
-$ nerdctl images
-REPOSITORY        TAG       IMAGE ID        CREATED         PLATFORM       SIZE         BLOB SIZE
-aquasec/nginx    latest    2bcabc23b454    3 hours ago     linux/amd64    149.1 MiB    54.1 MiB
-$ trivy image aquasec/nginx
-```
-
-If your containerd socket is not the default path (`//run/containerd/containerd.sock`), you can override it via `CONTAINERD_ADDRESS`.
-
-```bash
-$ export CONTAINERD_ADDRESS=/run/k3s/containerd/containerd.sock
-$ trivy image aquasec/nginx
-```
-
-If your scan targets are images in a namespace other than containerd's default namespace (`default`), you can override it via `CONTAINERD_NAMESPACE`.
-
-```bash
-$ export CONTAINERD_NAMESPACE=k8s.io
-$ trivy image aquasec/nginx
-```
-
-[containerd]: https://containerd.io/

docs/docs/advanced/container/oci.md

@@ -1,17 +0,0 @@
-# OCI Image Layout
-
-An image directory compliant with [Open Container Image Layout Specification](https://github.com/opencontainers/image-spec/blob/master/spec.md).
-
-Buildah:
-
-```
-$ buildah push docker.io/library/alpine:3.11 oci:/path/to/alpine
-$ trivy image --input /path/to/alpine
-```
-
-Skopeo:
-
-```
-$ skopeo copy docker-daemon:alpine:3.11 oci:/path/to/alpine
-$ trivy image --input /path/to/alpine
-```

docs/docs/advanced/container/podman.md

@@ -1,28 +0,0 @@
-# Podman
-
-!!! warning "EXPERIMENTAL"
-    This feature might change without preserving backwards compatibility.
-
-Scan your image in Podman (>=2.0) running locally. The remote Podman is not supported.
-Before performing Trivy commands, you must enable the podman.sock systemd service on your machine.
-For more details, see [here][sock].
-
-
-```bash
-$ systemctl --user enable --now podman.socket
-```
-
-Then, you can scan your image in Podman.
-
-```bash
-$ cat Dockerfile
-FROM alpine:3.12
-RUN apk add --no-cache bash
-$ podman build -t test .
-$ podman images
-REPOSITORY                TAG     IMAGE ID      CREATED      SIZE
-localhost/test            latest  efc372d4e0de  About a minute ago  7.94 MB
-$ trivy image test
-```
-
-[sock]: https://github.com/containers/podman/blob/master/docs/tutorials/remote_client.md#enable-the-podman-service-on-the-server-machine

docs/docs/advanced/plugins.md

@@ -42,6 +42,11 @@ For example, to download the Kubernetes Trivy plugin you can execute the followi
 ```bash
 $ trivy plugin install github.com/aquasecurity/trivy-plugin-kubectl
 ```
+Also, Trivy plugin can be installed from a local archive:
+```bash
+$ trivy plugin install myplugin.tar.gz
+```
+
 ## Using Plugins
 Once the plugin is installed, Trivy will load all available plugins in the cache on the start of the next Trivy execution.
 A plugin will be made in the Trivy CLI based on the plugin name.
@@ -162,6 +167,21 @@ When the plugin is called via Trivy CLI, `bin` command will be executed.
 
 The plugin is responsible for handling flags and arguments. Any arguments are passed to the plugin from the `trivy` command.
 
+A plugin should be archived `*.tar.gz`.
+
+```bash
+$ tar -czvf myplugin.tar.gz plugin.yaml script.py
+plugin.yaml
+script.py
+
+$ trivy plugin install myplugin.tar.gz
+2023-03-03T19:04:42.026+0600	INFO	Installing the plugin from myplugin.tar.gz...
+2023-03-03T19:04:42.026+0600	INFO	Loading the plugin metadata...
+
+$ trivy myplugin
+Hello from Trivy demo plugin!
+```
+
 ## Example
 https://github.com/aquasecurity/trivy-plugin-kubectl
 

docs/docs/advanced/private-registries/docker-hub.md

@@ -1,7 +1,2 @@
-Docker Hub needs `TRIVY_USERNAME` and `TRIVY_PASSWORD`.
-You don't need to set ENV vars when download from public repository.
-
-```bash
-export TRIVY_USERNAME={DOCKERHUB_USERNAME}
-export TRIVY_PASSWORD={DOCKERHUB_PASSWORD}
-```
+See [here](./index.md) for the detail.
+You don't need to provide a credential when download from public repository.

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

@@ -2,3 +2,34 @@ Trivy uses AWS SDK. You don't need to install `aws` CLI tool.
 You can use [AWS CLI's ENV Vars][env-var].
 
 [env-var]: https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-envvars.html
+
+### AWS private registry permissions
+
+You may need to grant permissions to allow Trivy to pull images from private ECR.
+
+It depends on how you want to provide AWS Role to trivy.
+
+- [IAM Role Service account](https://github.com/aws/amazon-eks-pod-identity-webhook)
+- [Kube2iam](https://github.com/jtblin/kube2iam) or [Kiam](https://github.com/uswitch/kiam)
+
+#### IAM Role Service account
+
+Add the AWS role in trivy's service account annotations:
+
+```yaml
+trivy:
+
+  serviceAccount:
+    annotations: {}
+      # eks.amazonaws.com/role-arn: arn:aws:iam::ACCOUNT_ID:role/IAM_ROLE_NAME
+```
+
+#### Kube2iam or Kiam
+
+Add the AWS role to pod's annotations:
+
+```yaml
+podAnnotations: {}
+  ## kube2iam/kiam annotation
+  # iam.amazonaws.com/role: arn:aws:iam::ACCOUNT_ID:role/IAM_ROLE_NAME
+```

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

@@ -1,4 +1,49 @@
-Trivy can download images from a private registry, without installing `Docker` or any other 3rd party tools.
-That's because it's easy to run in a CI process.
+Trivy can download images from a private registry without the need for installing Docker or any other 3rd party tools.
+This makes it easy to run within a CI process.
 
-All you have to do is install `Trivy` and set ENV vars.
+## Credential
+To use Trivy with private images, simply install it and provide your credentials:
+
+```shell
+$ TRIVY_USERNAME=YOUR_USERNAME TRIVY_PASSWORD=YOUR_PASSWORD trivy image YOUR_PRIVATE_IMAGE
+```
+
+Trivy also supports providing credentials through CLI flags:
+
+```shell
+$ TRIVY_PASSWORD=YOUR_PASSWORD trivy image --username YOUR_USERNAME YOUR_PRIVATE_IMAGE
+```
+
+!!! warning
+    The CLI flag `--password` is available, but its use is not recommended for security reasons.
+
+You can also store your credentials in `trivy.yaml`.
+For more information, please refer to [the documentation](../../references/customization/config-file.md).
+
+It can handle multiple sets of credentials as well:
+
+```shell
+$ export TRIVY_USERNAME=USERNAME1,USERNAME2
+$ export TRIVY_PASSWORD=PASSWORD1,PASSWORD2
+$ trivy image YOUR_PRIVATE_IMAGE
+```
+
+In the example above, Trivy attempts to use two pairs of credentials:
+
+- USERNAME1/PASSWORD1
+- USERNAME2/PASSWORD2
+
+Please note that the number of usernames and passwords must be the same.
+
+## docker login
+If you have Docker configured locally and have set up the credentials, Trivy can access them.
+
+```shell
+$ docker login ghcr.io
+Username: 
+Password:
+$ trivy image ghcr.io/your/private_image
+```
+
+!!! note
+    `docker login` can be used with any container runtime, such as Podman.

docs/docs/attestation/rekor.md

@@ -21,7 +21,7 @@ You need to pass `--sbom-sources rekor` so that Trivy will look for SBOM attesta
 $ trivy image --sbom-sources rekor otms61/alpine:3.7.3                                                                            [~/src/github.com/aquasecurity/trivy]
 2022-09-16T17:37:13.258+0900	INFO	Vulnerability scanning is enabled
 2022-09-16T17:37:13.258+0900	INFO	Secret scanning is enabled
-2022-09-16T17:37:13.258+0900	INFO	If your scanning is slow, please try '--security-checks vuln' to disable secret scanning
+2022-09-16T17:37:13.258+0900	INFO	If your scanning is slow, please try '--scanners vuln' to disable secret scanning
 2022-09-16T17:37:13.258+0900	INFO	Please see also https://aquasecurity.github.io/trivy/dev/docs/secret/scanning/#recommendation for faster secret detection
 2022-09-16T17:37:14.827+0900	INFO	Detected SBOM format: cyclonedx-json
 2022-09-16T17:37:14.901+0900	INFO	Found SBOM (cyclonedx) attestation in Rekor
@@ -80,6 +80,11 @@ $ trivy plugin install github.com/aquasecurity/trivy-plugin-attest
 $ trivy attest --predicate ./bat.cdx --type cyclonedx ./bat-v0.20.0-x86_64-apple-darwin/bat
 ```
 
+!!! note
+    The public instance of the Rekor maintained by the Sigstore team limits the attestation size.
+    If you are using the public instance, please make sure that your SBOM is small enough.
+    To get more detail, please refer to the Rekor project's [documentation](https://github.com/sigstore/rekor#public-instance).
+
 ### Scan a non-packaged binary
 Trivy calculates the digest of the `bat` binary and searches for the SBOM attestation by the digest in Rekor.
 If it is found, Trivy uses that for vulnerability scanning.
@@ -105,7 +110,7 @@ Total: 1 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 1, CRITICAL: 0)
 Also, it is applied to non-packaged binaries even in container images.
 
 ```bash
-$ trivy image --sbom-sources rekor --security-checks vuln alpine-with-bat
+$ trivy image --sbom-sources rekor --scanners vuln alpine-with-bat
 2022-10-25T13:40:14.920+0300    INFO    Vulnerability scanning is enabled
 2022-10-25T13:40:18.047+0300    INFO    Found SBOM attestation in Rekor: bat
 2022-10-25T13:40:18.186+0300    INFO    Detected OS: alpine

docs/docs/cloud/aws/compliance.md

@@ -1,39 +0,0 @@
-# AWS Compliance
-
-!!! warning "EXPERIMENTAL"
-    This feature might change without preserving backwards compatibility.
-
-This page describes AWS 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
---- | --- | ---
-AWS CIS Foundations Benchmark v1.2 | `aws-cis-1.2` | [link](https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf)
-AWS CIS Foundations Benchmark v1.4 | `aws-cis-1.4` | [link](https://docs.aws.amazon.com/securityhub/latest/userguide/securityhub-cis-controls-1.4.0.html)
-
-## Examples
-
-Scan a cloud account and generate a compliance summary report:
-
-```
-$ trivy aws --compliance=<compliance_id> --report=summary
-```
-
-***Note*** : The `Issues` column represent the total number of failed checks for this control.
-
-
-Get all of the detailed output for checks:
-
-```
-$ trivy aws --compliance=<compliance_id> --report all
-```
-
-Report result in JSON format:
-
-```
-$ trivy aws --compliance=<compliance_id> --report all --format json
-```
-

docs/docs/cloud/aws/scanning.md

@@ -1,66 +0,0 @@
-# Amazon Web Services
-
-!!! warning "EXPERIMENTAL"
-    This feature might change without preserving backwards compatibility.
-
-The Trivy AWS CLI allows you to scan your AWS account for misconfigurations. You can either run the CLI locally or integrate it into your CI/CD pipeline. 
-
-Whilst you can already scan the infrastructure-as-code that defines your AWS resources with `trivy config`, you can now scan your live AWS account(s) directly too.
-
-The included checks cover all of the aspects of the [AWS CIS 1.2](https://docs.aws.amazon.com/securityhub/latest/userguide/securityhub-standards-cis.html) automated benchmarks.
-
-Trivy uses the same [authentication methods](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html) as the AWS CLI to configure and authenticate your access to the AWS platform.
-
-You will need permissions configured to read all AWS resources - we recommend using a group/role with the `ReadOnlyAccess` policy attached.
-
-Once you've scanned your account, you can run additional commands to filter the results without having to run the entire scan again - infrastructure information is cached locally per AWS account/region.
-
-## CLI Commands
-
-Scan a full AWS account (all supported services):
-
-```shell
-trivy aws --region us-east-1
-```
-
-You can allow Trivy to determine the AWS region etc. by using the standard AWS configuration files and environment variables. The `--region` flag overrides these.
-
-![AWS Summary Report](../../../imgs/trivy-aws.png)
-
-The summary view is the default when scanning multiple services.
-
-Scan a specific service:
-
-```shell
-trivy aws --service s3
-```
-
-Scan multiple services:
-
-```shell
-# --service s3,ec2 works too
-trivy aws --service s3 --service ec2
-```
-
-Show results for a specific AWS resource:
-
-```shell
-trivy aws --service s3 --arn arn:aws:s3:::example-bucket
-```
-
-All ARNs with detected issues will be displayed when showing results for their associated service.
-
-## Compliance Spec
-Trivy can also run specific checks by spec by specifying the compliance flag:
-```shell
-trivy aws --compliance=awscis1.2
-```
-Will only target the checks defined under the AWS CIS 1.2 spec. Currently, we support AWS CIS 1.2 and 1.4 specs. More details [here](compliance.md).
-
-## Cached Results
-
-By default, Trivy will cache a representation of each AWS service for 24 hours. This means you can filter and view results for a service without having to wait for the entire scan to run again. If you want to force the cache to be refreshed with the latest data, you can use `--update-cache`. Or if you'd like to use cached data for a different timeframe, you can specify `--max-cache-age` (e.g. `--max-cache-age 2h`.). Regardless of whether the cache is used or not, rules will be evaluated again with each run of `trivy aws`.
-
-## Custom Policies
-
-You can write custom policies for Trivy to evaluate against your AWS account. These policies are written in [Rego](https://www.openpolicyagent.org/docs/latest/policy-language/), the same language used by [Open Policy Agent](https://www.openpolicyagent.org/). See the [Custom Policies](../../misconfiguration/custom/index.md) page for more information.

docs/docs/compliance/compliance.md

@@ -9,21 +9,23 @@ Trivy’s compliance flag lets you curate a specific set of checks into a report
 
 Compliance report is currently supported in the following targets (trivy sub-commands):
 
+- `trivy image`
 - `trivy aws`
 - `trivy k8s`
 
-Add the `--compliance` flag to the command line, and set it's value to desired report. For example: `trivy k8s cluster --compliance k8s-nsa` (see below for built-in and custom reports)
+Add the `--compliance` flag to the command line, and set it's value to desired report.
+For example: `trivy k8s cluster --compliance k8s-nsa` (see below for built-in and custom reports)
 
 ### Options
 
 The following flags are compatible with `--compliance` flag and allows customizing it's output:
 
-flag | effect
---- | ---
-`--report summary` | shows a summary of the results. for every control shows the number of failed checks.
-`--report all` | shows fully detailed results. for every control shows where it failed and why.
-`--format table` | shows results in textual table format (good for human readability).
-`--format json` | shows results in json format (good for machine readability).
+| flag               | effect                                                                               |
+|--------------------|--------------------------------------------------------------------------------------|
+| `--report summary` | shows a summary of the results. for every control shows the number of failed checks. |
+| `--report all`     | shows fully detailed results. for every control shows where it failed and why.       |
+| `--format table`   | shows results in textual table format (good for human readability).                  |
+| `--format json`    | shows results in json format (good for machine readability).                         |
 
 ## Built-in compliance
 
@@ -32,8 +34,9 @@ to specify a built-in compliance report, select it by ID like `trivy --complianc
 
 For the list of built-in compliance reports, please see the relevant section:
 
-- [Kubernetes compliance](../kubernetes/cli/compliance.md) 
-- [AWS compliance](../cloud/aws/compliance.md)
+- [Docker compliance](../target/container_image.md#compliance)
+- [Kubernetes compliance](../target/kubernetes.md#compliance) 
+- [AWS compliance](../target/aws.md#compliance)
 
 ## Custom compliance
 

docs/docs/index.md

@@ -1,72 +1,5 @@
 # Docs
 
-This documentation details how to use Trivy to access the features listed below.
+In this section you can find the complete reference documentation for all of the different features and settings that Trivy has to offer.
 
-## Features
-
-- Comprehensive vulnerability detection
-    - [OS packages][os] (Alpine, Wolfi, Red Hat Universal Base Image, Red Hat Enterprise Linux, CentOS, AlmaLinux, Rocky Linux, CBL-Mariner, Oracle Linux, Debian, Ubuntu, Amazon Linux, openSUSE Leap, SUSE Enterprise Linux, Photon OS and Distroless)
-    - [**Language-specific packages**][lang] (Bundler, Composer, Pipenv, Poetry, npm, yarn, pnpm, Cargo, NuGet, Maven, and Go)
-- Detect IaC misconfigurations
-    - A wide variety of [built-in policies][builtin] are provided **out of the box**:
-        - Kubernetes
-        - Docker
-        - Terraform
-        - more coming soon
-    - Support custom policies
-- Simple
-    - Specify only an image name, a directory containing IaC configs, or an artifact name
-    - See [Quick Start][quickstart]
-- Fast
-    - The first scan will finish within 10 seconds (depending on your network). Consequent scans will finish in single seconds.
-    - Unlike other scanners that take long to fetch vulnerability information (~10 minutes) on the first run, and encourage you to maintain a durable vulnerability database, Trivy is stateless and requires no maintenance or preparation.
-- Easy installation
-    - `apt-get install`, `yum install` and `brew install` is possible (See [Installation][installation])
-    - **No pre-requisites** such as installation of DB, libraries, etc.
-- High accuracy
-    - **Especially Alpine Linux and RHEL/CentOS**
-    - Other OSes are also high
-- DevSecOps
-    - **Suitable for CI** such as Travis CI, CircleCI, Jenkins, GitLab CI, etc.
-    - See [CI Example][integrations]
-- Support multiple formats
-    - container image
-        - A local image in Docker Engine which is running as a daemon
-        - A local image in [Podman][podman] (>=2.0) which is exposing a socket
-        - A remote image in Docker Registry such as Docker Hub, ECR, GCR and ACR
-        - A tar archive stored in the `docker save` / `podman save` formatted file
-        - An image directory compliant with [OCI Image Format][oci]
-    - local filesystem and rootfs
-    - remote git repository
-- [SBOM][sbom] (Software Bill of Materials) support
-    - CycloneDX
-    - SPDX
-    - GitHub Dependency Snapshots
-
-Please see [LICENSE][license] for Trivy licensing information.
-
-[installation]: ../getting-started/installation.md
-[vuln]: ../docs/vulnerability/scanning/index.md
-[misconf]: ../docs/misconfiguration/scanning.md
-[kubernetesoperator]: ../docs/kubernetes/operator/index.md
-[container]: ../docs/vulnerability/scanning/image.md
-[rootfs]: ../docs/vulnerability/scanning/rootfs.md
-[filesystem]: ../docs/vulnerability/scanning/filesystem.md
-[repo]: ../docs/vulnerability/scanning/git-repository.md
-[kubernetes]: ../docs/kubernetes/cli/scanning.md
-
-[standalone]: ../docs/references/modes/standalone.md
-[client-server]: ../docs/references/modes/client-server.md
-[integrations]: ../tutorials/integrations/index.md
-
-[os]: ../docs/vulnerability/detection/os.md
-[lang]: ../docs/vulnerability/detection/language.md
-
-[builtin]: ../docs/misconfiguration/policy/builtin.md
-[quickstart]: ../index.md
-[podman]: ../docs/advanced/container/podman.md
-
-[sbom]: ../docs/sbom/index.md
-
-[oci]: https://github.com/opencontainers/image-spec
-[license]:  https://github.com/aquasecurity/trivy/blob/main/LICENSE
+👈 Please use the side-navigation on the left in order to browse the different topics.

docs/docs/kubernetes/cli/compliance.md

@@ -1,42 +0,0 @@
-# Kubernetes Compliance
-
-!!! warning "EXPERIMENTAL"
-    This feature might change without preserving backwards compatibility.
-
-This page 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
---- | --- | ---
-NSA, CISA Kubernetes Hardening Guidance v1.2 | `k8s-nsa` | [Link](https://media.defense.gov/2022/Aug/29/2003066362/-1/-1/0/CTR_KUBERNETES_HARDENING_GUIDANCE_1.2_20220829.PDF)
-CIS Benchmark for Kubernetes v1.23 | `k8s-cis` | [Link](https://www.cisecurity.org/benchmark/kubernetes)
-
-## Examples
-
-Scan a full cluster and generate a compliance summary report:
-
-```
-$ trivy k8s cluster --compliance=<compliance_id> --report summary
-```
-
-***Note*** : The `Issues` column represent the total number of failed checks for this control.
-
-
-Get all of the detailed output for checks:
-
-```
-trivy k8s cluster --compliance=<compliance_id> --report all
-```
-
-Report result in JSON format:
-
-```
-trivy k8s cluster --compliance=<compliance_id> --report summary --format json
-```
-
-```
-trivy k8s cluster --compliance=<compliance_id> --report all --format json
-```

docs/docs/kubernetes/operator/index.md

@@ -1,14 +0,0 @@
-# Trivy 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

docs/docs/licenses/scanning.md

@@ -25,7 +25,7 @@ In addition to package licenses, Trivy scans source code files, Markdown documen
 
 Currently, the standard license scanning doesn't support filesystem and repository scanning.
 
-|   License scnanning   | Image | Rootfs    | Filesystem | Repository |
+|   License scanning    | Image | Rootfs    | Filesystem | Repository |
 |:---------------------:|:-----:|:---------:|:----------:|:----------:|
 |       Standard        |  ✅   |     ✅    |   -        |      -     |
 | Full (--license-full) |  ✅   |     ✅    |     ✅     |     ✅     |
@@ -47,10 +47,10 @@ License checking classifies the identified licenses and map the classification t
 This section shows how to scan license in container image and filesystem.
 
 ### Standard scanning
-Specify an image name with `--security-checks license`.
+Specify an image name with `--scanners license`.
 
 ``` shell
-$ trivy image --security-checks license --severity UNKNOWN,HIGH,CRITICAL alpine:3.15
+$ trivy image --scanners license --severity UNKNOWN,HIGH,CRITICAL alpine:3.15
 2022-07-13T17:28:39.526+0300    INFO    License scanning is enabled
 
 OS Packages (license)
@@ -78,7 +78,7 @@ Total: 6 (UNKNOWN: 0, HIGH: 6, CRITICAL: 0)
 Specify `--license-full`
 
 ``` shell
-$ trivy image --security-checks license --severity UNKNOWN,HIGH,CRITICAL --license-full grafana/grafana
+$ trivy image --scanners license --severity UNKNOWN,HIGH,CRITICAL --license-full grafana/grafana
 2022-07-13T17:48:40.905+0300    INFO    Full license scanning is enabled
 
 OS Packages (license)
@@ -141,7 +141,7 @@ Trivy has number of configuration flags for use with license scanning;
 Trivy license scanning can ignore licenses that are identified to explicitly remove them from the results using the `--ignored-licenses` flag;
 
 ```shell
-$ trivy image --security-checks license --ignored-licenses MPL-2.0,MIT --severity LOW grafana/grafana:latest
+$ trivy image --scanners license --ignored-licenses MPL-2.0,MIT --severity LOW grafana/grafana:latest
 2022-07-13T18:15:28.605Z        INFO    License scanning is enabled
 
 OS Packages (license)

docs/docs/misconfiguration/custom/index.md

@@ -40,7 +40,7 @@ A single package must contain only one policy.
     # title: Deployment not allowed
     # description: Deployments are not allowed because of some reasons.
     # schemas:
-    #   - input: schema.input
+    #   - input: schema["kubernetes"]
     # custom:
     #   id: ID001
     #   severity: LOW
@@ -124,16 +124,16 @@ All fields are optional. The `schemas` field should be used to enable policy val
 schema that will be used is based on the input document type. It is recommended to use this to ensure your policies are 
 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.input`                           | (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: | 
-| url                        | Any characters                           |                              | :material-close: | :material-check: |
+| 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: | 
+| url                        | Any characters                                                    |                              | :material-close: | :material-check: |
 
 
 Some fields are displayed in scan results.
@@ -196,13 +196,7 @@ You can specify input format via the `custom.input` annotation.
     `type` accepts `kubernetes`, `dockerfile`, `cloudformation`, `terraform`, `terraformplan`, `json`, or `yaml`.
 
 ### Schemas
-
-You can explore the format of input documents by browsing the schema for the relevant input type:
-
-- [Cloud](https://github.com/aquasecurity/defsec/blob/master/pkg/rego/schemas/cloud.json)
-- [Dockerfile](https://github.com/aquasecurity/defsec/blob/master/pkg/rego/schemas/dockerfile.json)
-- [Kubernetes](https://github.com/aquasecurity/defsec/blob/master/pkg/rego/schemas/kubernetes.json)
-- [RBAC](https://github.com/aquasecurity/defsec/blob/master/pkg/rego/schemas/rbac.json)
+See [here](./schema.md) for the detail.
 
 [rego]: https://www.openpolicyagent.org/docs/latest/policy-language/
 [package]: https://www.openpolicyagent.org/docs/latest/policy-language/#packages

docs/docs/misconfiguration/custom/schema.md

@@ -0,0 +1,93 @@
+# Input Schema
+
+## Overview
+Policies can be defined with custom schemas that allow inputs to be verified against them. Adding a policy schema
+enables Trivy to show more detailed error messages when an invalid input is encountered.
+
+In Trivy we have been able to define a schema for a [Dockerfile](https://github.com/aquasecurity/defsec/blob/master/pkg/rego/schemas/dockerfile.json).
+Without input schemas, a policy would be as follows:
+
+!!! example
+    ```
+    # METADATA
+    package mypackage
+
+    deny {
+        input.evil == "foo bar"
+    }
+    ```
+
+If this policy is run against offending Dockerfile(s), there will not be any issues as the policy will fail to evaluate.
+Although the policy's failure to evaluate is legitimate, this should not result in a positive result for the scan.
+
+For instance if we have a policy that checks for misconfigurations in a `Dockerfile`, we could define the
+schema as such
+
+!!! example
+    ```
+    # METADATA
+    # schemas:
+    # - input: schema["dockerfile"]
+    package mypackage
+    
+    deny {
+        input.evil == "foo bar"
+    }
+    ```
+
+Here `input: schema["dockerfile"]` points to a schema that expects a valid `Dockerfile` as input. An example of this
+can be found [here](https://github.com/aquasecurity/defsec/blob/master/pkg/rego/schemas/dockerfile.json)
+
+Now if this policy is evaluated against, a more descriptive error will be available to help fix the problem.
+
+```bash
+1 error occurred: testpolicy.rego:8: rego_type_error: undefined ref: input.evil
+        input.evil
+              ^
+              have: "evil"
+              want (one of): ["Stages"]
+```
+
+Currently, out of the box the following schemas are supported natively:
+
+1. [Docker](https://github.com/aquasecurity/defsec/blob/master/pkg/rego/schemas/dockerfile.json)
+2. [Kubernetes](https://github.com/aquasecurity/defsec/blob/master/pkg/rego/schemas/kubernetes.json)
+3. [Cloud](https://github.com/aquasecurity/defsec/blob/master/pkg/rego/schemas/cloud.json)
+
+
+## Custom Policies with Custom Schemas
+
+You can also bring a custom policy that defines one or more custom schema. 
+
+!!! example
+    ```
+    # METADATA
+    # schemas:
+    # - input: schema["fooschema"]
+    # - input: schema["barschema"]
+    package mypackage
+    
+    deny {
+        input.evil == "foo bar"
+    }
+    ```
+
+The policies can be placed in a structure as follows
+
+!!! example
+    ```
+    /Users/user/my-custom-policies
+    ├── my_policy.rego
+    └── schemas
+        └── fooschema.json
+        └── barschema.json
+    ```
+
+To use such a policy with Trivy, use the `--config-policy` flag that points to the directory where the schemas and policies
+are contained.
+
+```bash
+$ trivy --config-policy=/Users/user/my-custom-policies <path/to/iac>
+```
+
+For more details on how to define schemas within Rego policies, please see the [OPA guide](https://www.openpolicyagent.org/docs/latest/schemas/#schema-annotations) that describes it in more detail.

docs/docs/misconfiguration/custom/selectors.md

@@ -0,0 +1,51 @@
+# Input Selectors
+
+## Overview
+Sometimes you might want to limit a certain policy to only be run on certain resources. This can be
+achieved with input selectors.
+
+## Use case
+For instance, if you have a custom policy that you only want to be evaluated if a certain resource type is being scanned.
+In such a case you could utilize input selectors to limit its evaluation on only those resources.
+
+!!! example
+    ```
+        # METADATA
+        # title: "RDS Publicly Accessible"
+        # description: "Ensures RDS instances are not launched into the public cloud."
+        # custom:
+        #   input:
+        #     selector:
+        #     - type: cloud
+        #       subtypes:
+        #         - provider: aws
+        #           service: rds
+        package builtin.aws.rds.aws0999
+
+        deny[res] {
+        instance := input.aws.rds.instances[_]
+        instance.publicaccess.value
+        res := result.new("Instance has Public Access enabled", instance.publicaccess)
+    ```
+
+Observe the following `subtypes` defined:
+```yaml
+        #       subtypes:
+        #         - provider: aws
+        #           service: rds
+```
+
+They will ensure that the policy is only run when the input to such a policy contains an `RDS` instance. 
+
+## Enabling selectors and subtypes
+Currently, the following are supported:
+
+| Selector                 | Subtype fields required | Example                         |
+|--------------------------|-------------------------|---------------------------------|
+| Cloud (AWS, Azure, etc.) | `provider`, `service`   | `provider: aws`, `service: rds` |
+| Kubernetes               |                         | `type: kubernetes`              |
+| Dockerfile               |                         | `type: dockerfile`              |
+
+
+## Default behaviour
+If no subtypes or selectors are specified, the policy will be evaluated regardless of input.

docs/docs/misconfiguration/policy/builtin.md

@@ -13,16 +13,22 @@ Those policies are managed under [defsec repository][defsec].
 | CloudFormation            | [defsec][defsec]     |
 | Azure ARM Template        | [defsec][defsec]     |
 | Helm Chart                | [defsec][kubernetes] |      
-| RBAC                      | [defsec][rbac]       |      
 
 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.
 
-Ansible scanning is coming soon.
+## 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.
+Those policies are then loaded into Trivy OPA engine and used for detecting misconfigurations.
+If Trivy is unable to pull down newer policies, it will use the embedded set of policies as a fallback. This is also the case in air-gap environments where `--skip-policy-update` might be passed.
 
-[rego]: https://www.openpolicyagent.org/docs/latest/policy-language
+## Update Interval
+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/
 [defsec]: https://github.com/aquasecurity/defsec
-[kubernetes]: https://github.com/aquasecurity/defsec/tree/master/internal/rules/policies/kubernetes
-[docker]: https://github.com/aquasecurity/defsec/tree/master/internal/rules/policies/docker
-[rbac]: https://github.com/aquasecurity/defsec/tree/master/internal/rules/policies/rbac
+[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

docs/docs/misconfiguration/scanning.md

@@ -37,28 +37,28 @@ $ trivy config [YOUR_IaC_DIRECTORY]
     ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
     ```
 
-You can also enable misconfiguration detection in container image, filesystem and git repository scanning via `--security-checks config`.
+You can also enable misconfiguration detection in container image, filesystem and git repository scanning via `--scanners config`.
 
 ```bash
-$ trivy image --security-checks config IMAGE_NAME
+$ trivy image --scanners config IMAGE_NAME
 ```
 
 ```bash
-$ trivy fs --security-checks config /path/to/dir
+$ trivy fs --scanners config /path/to/dir
 ```
 
 !!! note
     Misconfiguration detection is not enabled by default in `image`, `fs` and `repo` subcommands.
 
 Unlike the `config` subcommand, `image`, `fs` and `repo` subcommands can also scan for vulnerabilities and secrets at the same time. 
-You can specify `--security-checks vuln,config,secret` to enable vulnerability and secret detection as well as misconfiguration detection.
+You can specify `--scanners vuln,config,secret` to enable vulnerability and secret detection as well as misconfiguration detection.
 
 
 !!! example
     ``` bash
     $ ls myapp/
     Dockerfile Pipfile.lock
-    $ trivy fs --security-checks vuln,config,secret --severity HIGH,CRITICAL myapp/
+    $ trivy fs --scanners vuln,config,secret --severity HIGH,CRITICAL myapp/
     2022-05-16T13:42:21.440+0100	INFO	Number of language-specific files: 1
     2022-05-16T13:42:21.440+0100	INFO	Detecting pipenv vulnerabilities...
     2022-05-16T13:42:21.440+0100	INFO	Detected config files: 1

docs/docs/references/cli/client.md

@@ -1,70 +0,0 @@
-# Client
-
-```bash
-Usage:
-  trivy client [flags] IMAGE_NAME
-
-Aliases:
-  client, c
-
-Scan Flags
-      --offline-scan             do not issue API requests to identify dependencies
-      --security-checks string   comma-separated list of what security issues to detect (vuln,config,secret) (default "vuln,secret")
-      --skip-dirs strings        specify the directories where the traversal is skipped
-      --skip-files strings       specify the file paths to skip traversal
-
-Report Flags
-      --dependency-tree        show dependency origin tree (EXPERIMENTAL)
-      --exit-code int          specify exit code when any security issues are found
-  -f, --format string          format (table, json, sarif, template, cyclonedx, spdx, spdx-json, github, cosign-vuln) (default "table")
-      --ignore-policy string   specify the Rego file path to evaluate each vulnerability
-      --ignorefile string      specify .trivyignore file (default ".trivyignore")
-      --list-all-pkgs          enabling the option will output all packages regardless of vulnerability
-  -o, --output string          output file name
-      --report string          specify a report format for the output. (all,summary) (default "all")
-  -s, --severity string        severities of security issues to be displayed (comma separated) (default "UNKNOWN,LOW,MEDIUM,HIGH,CRITICAL")
-  -t, --template string        output template
-
-Cache Flags
-      --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
-      --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
-
-DB Flags
-      --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
-      --no-progress            suppress progress bar
-      --reset                  remove all caches and database
-      --skip-db-update         skip updating vulnerability database
-
-Vulnerability Flags
-      --ignore-unfixed     display only fixed vulnerabilities
-      --vuln-type string   comma-separated list of vulnerability types (os,library) (default "os,library")
-
-Misconfiguration Flags
-      --config-data strings         specify paths from which data for the Rego policies will be recursively loaded
-      --config-policy strings       specify paths to the Rego policy files directory, applying config files
-      --file-patterns strings       specify config file patterns, available with '--security-checks config'
-      --include-non-failures        include successes and exceptions, available with '--security-checks config'
-      --policy-namespaces strings   Rego namespaces
-      --trace                       enable more verbose trace output for custom queries
-
-Client/Server Flags
-      --custom-headers strings   custom headers in client mode
-      --remote string            server address (default "http://localhost:4954")
-      --token string             for authentication in client/server mode
-      --token-header string      specify a header name for token in client/server mode (default "Trivy-Token")
-
-Global Flags:
-      --cache-dir string          cache directory (default "/Users/teppei/Library/Caches/trivy")
-  -c, --config string             config path (default "trivy.yaml")
-  -d, --debug                     debug mode
-      --generate-default-config   write the default config to trivy-default.yaml
-      --insecure                  allow insecure server connections when using TLS
-  -q, --quiet                     suppress progress bar and log output
-      --timeout duration          timeout (default 5m0s)
-  -v, --version                   show version
-```

docs/docs/references/cli/config.md

@@ -1,49 +0,0 @@
-# Config
-
-``` bash
-Scan config files for misconfigurations
-
-Usage:
-  trivy config [flags] DIR
-
-Aliases:
-  config, conf
-
-Scan Flags
-      --skip-dirs strings    specify the directories where the traversal is skipped
-      --skip-files strings   specify the file paths to skip traversal
-
-Report Flags
-      --exit-code int       specify exit code when any security issues are found
-  -f, --format string       format (table, json, sarif, template, cyclonedx, spdx, spdx-json, github, cosign-vuln) (default "table")
-      --ignorefile string   specify .trivyignore file (default ".trivyignore")
-  -o, --output string       output file name
-  -s, --severity string     severities of security issues to be displayed (comma separated) (default "UNKNOWN,LOW,MEDIUM,HIGH,CRITICAL")
-  -t, --template string     output template
-
-Cache Flags
-      --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
-      --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
-
-Misconfiguration Flags
-      --config-data strings         specify paths from which data for the Rego policies will be recursively loaded
-      --config-policy strings       specify paths to the Rego policy files directory, applying config files
-      --file-patterns strings       specify config file patterns, available with '--security-checks config'
-      --include-non-failures        include successes and exceptions, available with '--security-checks config'
-      --policy-namespaces strings   Rego namespaces
-      --trace                       enable more verbose trace output for custom queries
-
-Global Flags:
-      --cache-dir string          cache directory (default "/Users/teppei/Library/Caches/trivy")
-  -c, --config string             config path (default "trivy.yaml")
-  -d, --debug                     debug mode
-      --generate-default-config   write the default config to trivy-default.yaml
-      --insecure                  allow insecure server connections when using TLS
-  -q, --quiet                     suppress progress bar and log output
-      --timeout duration          timeout (default 5m0s)
-  -v, --version                   show version
-```

docs/docs/references/cli/fs.md

@@ -1,85 +0,0 @@
-# Filesystem
-
-```bash
-Scan local filesystem
-
-Usage:
-  trivy filesystem [flags] PATH
-
-Aliases:
-  filesystem, fs
-
-Examples:
-  # Scan a local project including language-specific files
-  $ trivy fs /path/to/your_project
-
-  # Scan a single file
-  $ trivy fs ./trivy-ci-test/Pipfile.lock
-
-Scan Flags
-      --offline-scan             do not issue API requests to identify dependencies
-      --security-checks string   comma-separated list of what security issues to detect (vuln,config,secret) (default "vuln,secret")
-      --skip-dirs strings        specify the directories where the traversal is skipped
-      --skip-files strings       specify the file paths to skip traversal
-
-Report Flags
-      --dependency-tree        show dependency origin tree (EXPERIMENTAL)
-      --exit-code int          specify exit code when any security issues are found
-  -f, --format string          format (table, json, sarif, template, cyclonedx, spdx, spdx-json, github, cosign-vuln) (default "table")
-      --ignore-policy string   specify the Rego file path to evaluate each vulnerability
-      --ignorefile string      specify .trivyignore file (default ".trivyignore")
-      --list-all-pkgs          enabling the option will output all packages regardless of vulnerability
-  -o, --output string          output file name
-  -s, --severity string        severities of security issues to be displayed (comma separated) (default "UNKNOWN,LOW,MEDIUM,HIGH,CRITICAL")
-  -t, --template string        output template
-
-Cache Flags
-      --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
-      --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
-
-DB Flags
-      --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
-      --no-progress            suppress progress bar
-      --reset                  remove all caches and database
-      --skip-db-update         skip updating vulnerability database
-
-Vulnerability Flags
-      --ignore-unfixed     display only fixed vulnerabilities
-      --vuln-type string   comma-separated list of vulnerability types (os,library) (default "os,library")
-
-Misconfiguration Flags
-      --config-data strings         specify paths from which data for the Rego policies will be recursively loaded
-      --config-policy strings       specify paths to the Rego policy files directory, applying config files
-      --file-patterns strings       specify config file patterns, available with '--security-checks config'
-      --include-non-failures        include successes and exceptions, available with '--security-checks config'
-      --policy-namespaces strings   Rego namespaces
-      --trace                       enable more verbose trace output for custom queries
-
-Secret Flags
-      --secret-config string   specify a path to config file for secret scanning (default "trivy-secret.yaml")
-
-License Flags
-      --ignored-licenses strings   specify a list of license to ignore
-      --license-full               eagerly look for licenses in source code headers and license files
-
-Client/Server Flags
-      --custom-headers strings   custom headers in client mode
-      --server string            server address in client mode
-      --token string             for authentication in client/server mode
-      --token-header string      specify a header name for token in client/server mode (default "Trivy-Token")
-
-Global Flags:
-      --cache-dir string          cache directory (default "/Users/teppei/Library/Caches/trivy")
-  -c, --config string             config path (default "trivy.yaml")
-  -d, --debug                     debug mode
-      --generate-default-config   write the default config to trivy-default.yaml
-      --insecure                  allow insecure server connections when using TLS
-  -q, --quiet                     suppress progress bar and log output
-      --timeout duration          timeout (default 5m0s)
-  -v, --version                   show version
-```

docs/docs/references/cli/image.md

@@ -1,103 +0,0 @@
-# Image
-
-```bash
-Scan a container image
-
-Usage:
-  trivy image [flags] IMAGE_NAME
-
-Aliases:
-  image, i
-
-Examples:
-  # Scan a container image
-  $ trivy image python:3.4-alpine
-
-  # Scan a container image from a tar archive
-  $ trivy image --input ruby-3.1.tar
-
-  # Filter by severities
-  $ trivy image --severity HIGH,CRITICAL alpine:3.15
-
-  # Ignore unfixed/unpatched vulnerabilities
-  $ trivy image --ignore-unfixed alpine:3.15
-
-  # Scan a container image in client mode
-  $ trivy image --server http://127.0.0.1:4954 alpine:latest
-
-  # Generate json result
-  $ trivy image --format json --output result.json alpine:3.15
-
-  # Generate a report in the CycloneDX format
-  $ trivy image --format cyclonedx --output result.cdx alpine:3.15
-
-Scan Flags
-      --offline-scan             do not issue API requests to identify dependencies
-      --security-checks string   comma-separated list of what security issues to detect (vuln,config,secret) (default "vuln,secret")
-      --skip-dirs strings        specify the directories where the traversal is skipped
-      --skip-files strings       specify the file paths to skip traversal
-
-Report Flags
-      --exit-code int          specify exit code when any security issues are found
-  -f, --format string          format (table, json, sarif, template, cyclonedx, spdx, spdx-json, github, cosign-vuln) (default "table")
-      --ignore-policy string   specify the Rego file path to evaluate each vulnerability
-      --ignorefile string      specify .trivyignore file (default ".trivyignore")
-      --list-all-pkgs          enabling the option will output all packages regardless of vulnerability
-  -o, --output string          output file name
-  -s, --severity string        severities of security issues to be displayed (comma separated) (default "UNKNOWN,LOW,MEDIUM,HIGH,CRITICAL")
-  -t, --template string        output template
-
-Cache Flags
-      --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
-      --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
-
-DB Flags
-      --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
-      --no-progress            suppress progress bar
-      --reset                  remove all caches and database
-      --skip-db-update         skip updating vulnerability database
-
-Image Flags
-      --input string   input file path instead of image name
-      --removed-pkgs   detect vulnerabilities of removed packages (only for Alpine)
-
-Vulnerability Flags
-      --ignore-unfixed     display only fixed vulnerabilities
-      --vuln-type string   comma-separated list of vulnerability types (os,library) (default "os,library")
-
-Misconfiguration Flags
-      --config-data strings         specify paths from which data for the Rego policies will be recursively loaded
-      --config-policy strings       specify paths to the Rego policy files directory, applying config files
-      --file-patterns strings       specify config file patterns, available with '--security-checks config'
-      --include-non-failures        include successes and exceptions, available with '--security-checks config'
-      --policy-namespaces strings   Rego namespaces
-      --trace                       enable more verbose trace output for custom queries
-
-Secret Flags
-      --secret-config string   specify a path to config file for secret scanning (default "trivy-secret.yaml")
-
-License Flags
-      --ignored-licenses strings   specify a list of license to ignore
-      --license-full               eagerly look for licenses in source code headers and license files
-
-Client/Server Flags
-      --custom-headers strings   custom headers in client mode
-      --server string            server address in client mode
-      --token string             for authentication in client/server mode
-      --token-header string      specify a header name for token in client/server mode (default "Trivy-Token")
-
-Global Flags:
-      --cache-dir string          cache directory (default "/Users/teppei/Library/Caches/trivy")
-  -c, --config string             config path (default "trivy.yaml")
-  -d, --debug                     debug mode
-      --generate-default-config   write the default config to trivy-default.yaml
-      --insecure                  allow insecure server connections when using TLS
-  -q, --quiet                     suppress progress bar and log output
-      --timeout duration          timeout (default 5m0s)
-  -v, --version                   show version
-```

docs/docs/references/cli/index.md

@@ -1,50 +0,0 @@
-Trivy has several sub commands, image, fs, repo, client and server.
-
-``` bash
-Scanner for vulnerabilities in container images, file systems, and Git repositories, as well as for configuration issues and hard-coded secrets
-
-Usage:
-  trivy [global flags] command [flags] target
-  trivy [command]
-
-Examples:
-  # Scan a container image
-  $ trivy image python:3.4-alpine
-
-  # Scan a container image from a tar archive
-  $ trivy image --input ruby-3.1.tar
-
-  # Scan local filesystem
-  $ trivy fs .
-
-  # Run in server mode
-  $ trivy server
-
-Available Commands:
-  config      Scan config files for misconfigurations
-  filesystem  Scan local filesystem
-  help        Help about any command
-  image       Scan a container image
-  kubernetes  scan kubernetes cluster
-  module      Manage modules
-  plugin      Manage plugins
-  repository  Scan a remote repository
-  rootfs      Scan rootfs
-  sbom        Scan SBOM for vulnerabilities
-  server      Server mode
-  version     Print the version
-
-Flags:
-      --cache-dir string          cache directory (default "/Users/teppei/Library/Caches/trivy")
-  -c, --config string             config path (default "trivy.yaml")
-  -d, --debug                     debug mode
-  -f, --format string             version format (json)
-      --generate-default-config   write the default config to trivy-default.yaml
-  -h, --help                      help for trivy
-      --insecure                  allow insecure server connections when using TLS
-  -q, --quiet                     suppress progress bar and log output
-      --timeout duration          timeout (default 5m0s)
-  -v, --version                   show version
-
-Use "trivy [command] --help" for more information about a command.
-```

docs/docs/references/cli/plugin.md

@@ -1,34 +0,0 @@
-# Plugin
-
-```bash
-Manage plugins
-
-Usage:
-  trivy plugin [command]
-
-Aliases:
-  plugin, p
-
-Available Commands:
-  info        Show information about the specified plugin
-  install     Install a plugin
-  list        List installed plugin
-  run         Run a plugin on the fly
-  uninstall   Uninstall a plugin
-  update      Update an existing plugin
-
-Flags:
-  -h, --help   help for plugin
-
-Global Flags:
-      --cache-dir string          cache directory (default "/Users/teppei/Library/Caches/trivy")
-  -c, --config string             config path (default "trivy.yaml")
-  -d, --debug                     debug mode
-      --generate-default-config   write the default config to trivy-default.yaml
-      --insecure                  allow insecure server connections when using TLS
-  -q, --quiet                     suppress progress bar and log output
-      --timeout duration          timeout (default 5m0s)
-  -v, --version                   show version
-
-Use "trivy plugin [command] --help" for more information about a command.
-```

docs/docs/references/cli/repo.md

@@ -1,87 +0,0 @@
-# Repository
-
-```bash
-Scan a remote repository
-
-Usage:
-  trivy repository [flags] REPO_URL
-
-Aliases:
-  repository, repo
-
-Examples:
-  # Scan your remote git repository
-  $ trivy repo https://github.com/knqyf263/trivy-ci-test
-
-Scan Flags
-      --offline-scan             do not issue API requests to identify dependencies
-      --security-checks string   comma-separated list of what security issues to detect (vuln,config,secret) (default "vuln,secret")
-      --skip-dirs strings        specify the directories where the traversal is skipped
-      --skip-files strings       specify the file paths to skip traversal
-
-Report Flags
-      --dependency-tree        show dependency origin tree (EXPERIMENTAL)
-      --exit-code int          specify exit code when any security issues are found
-  -f, --format string          format (table, json, sarif, template, cyclonedx, spdx, spdx-json, github, cosign-vuln) (default "table")
-      --ignore-policy string   specify the Rego file path to evaluate each vulnerability
-      --ignorefile string      specify .trivyignore file (default ".trivyignore")
-      --list-all-pkgs          enabling the option will output all packages regardless of vulnerability
-  -o, --output string          output file name
-  -s, --severity string        severities of security issues to be displayed (comma separated) (default "UNKNOWN,LOW,MEDIUM,HIGH,CRITICAL")
-  -t, --template string        output template
-
-Cache Flags
-      --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
-      --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
-
-DB Flags
-      --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
-      --no-progress            suppress progress bar
-      --reset                  remove all caches and database
-      --skip-db-update         skip updating vulnerability database
-
-Vulnerability Flags
-      --ignore-unfixed     display only fixed vulnerabilities
-      --vuln-type string   comma-separated list of vulnerability types (os,library) (default "os,library")
-
-Misconfiguration Flags
-      --config-data strings         specify paths from which data for the Rego policies will be recursively loaded
-      --config-policy strings       specify paths to the Rego policy files directory, applying config files
-      --file-patterns strings       specify config file patterns, available with '--security-checks config'
-      --include-non-failures        include successes and exceptions, available with '--security-checks config'
-      --policy-namespaces strings   Rego namespaces
-      --trace                       enable more verbose trace output for custom queries
-
-Secret Flags
-      --secret-config string   specify a path to config file for secret scanning (default "trivy-secret.yaml")
-
-License Flags
-      --ignored-licenses strings   specify a list of license to ignore
-      --license-full               eagerly look for licenses in source code headers and license files
-
-Client/Server Flags
-      --custom-headers strings   custom headers in client mode
-      --server string            server address in client mode
-      --token string             for authentication in client/server mode
-      --token-header string      specify a header name for token in client/server mode (default "Trivy-Token")
-
-Repository Flags
-      --branch string   pass the branch name to be scanned
-      --commit string   pass the commit hash to be scanned
-      --tag string      pass the tag name to be scanned
-
-Global Flags:
-      --cache-dir string          cache directory (default "/Users/teppei/Library/Caches/trivy")
-  -c, --config string             config path (default "trivy.yaml")
-  -d, --debug                     debug mode
-      --generate-default-config   write the default config to trivy-default.yaml
-      --insecure                  allow insecure server connections when using TLS
-  -q, --quiet                     suppress progress bar and log output
-      --timeout duration          timeout (default 5m0s)
-  -v, --version                   show version
-```

docs/docs/references/cli/rootfs.md

@@ -1,94 +0,0 @@
-# Rootfs
-
-```bash
-Scan rootfs
-
-Usage:
-  trivy rootfs [flags] ROOTDIR
-
-Examples:
-  # Scan unpacked filesystem
-  $ docker export $(docker create alpine:3.10.2) | tar -C /tmp/rootfs -xvf -
-  $ trivy rootfs /tmp/rootfs
-
-  # Scan from inside a container
-  $ docker run --rm -it alpine:3.11
-  / # curl -sfL https://raw.githubusercontent.com/aquasecurity/trivy/main/contrib/install.sh | sh -s -- -b /usr/local/bin
-  / # trivy rootfs /
-
-Scan Flags
-      --file-patterns strings     specify config file patterns
-      --offline-scan              do not issue API requests to identify dependencies
-      --rekor-url string          [EXPERIMENTAL] address of rekor STL server (default "https://rekor.sigstore.dev")
-      --sbom-sources strings      [EXPERIMENTAL] try to retrieve SBOM from the specified sources (rekor)
-      --security-checks strings   comma-separated list of what security issues to detect (vuln,config,secret,license) (default [vuln,secret])
-      --skip-dirs strings         specify the directories where the traversal is skipped
-      --skip-files strings        specify the file paths to skip traversal
-
-Report Flags
-      --dependency-tree        show dependency origin tree (EXPERIMENTAL)
-      --exit-code int          specify exit code when any security issues are found
-  -f, --format string          format (table, json, sarif, template, cyclonedx, spdx, spdx-json, github, cosign-vuln) (default "table")
-      --ignore-policy string   specify the Rego file path to evaluate each vulnerability
-      --ignorefile string      specify .trivyignore file (default ".trivyignore")
-      --list-all-pkgs          enabling the option will output all packages regardless of vulnerability
-  -o, --output string          output file name
-  -s, --severity string        severities of security issues to be displayed (comma separated) (default "UNKNOWN,LOW,MEDIUM,HIGH,CRITICAL")
-  -t, --template string        output template
-
-Cache Flags
-      --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
-      --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
-
-DB Flags
-      --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
-      --no-progress            suppress progress bar
-      --reset                  remove all caches and database
-      --skip-db-update         skip updating vulnerability database
-
-Vulnerability Flags
-      --ignore-unfixed     display only fixed vulnerabilities
-      --vuln-type string   comma-separated list of vulnerability types (os,library) (default "os,library")
-
-Misconfiguration Flags
-      --helm-set strings          specify Helm values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
-      --helm-set-file strings     specify Helm values from respective files specified via the command line (can specify multiple or separate values with commas: key1=path1,key2=path2)
-      --helm-set-string strings   specify Helm string values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
-      --helm-values strings       specify paths to override the Helm values.yaml files
-      --include-non-failures      include successes and exceptions, available with '--security-checks config'
-      --tf-vars strings           specify paths to override the Terraform tfvars files
-
-Secret Flags
-      --secret-config string   specify a path to config file for secret scanning (default "trivy-secret.yaml")
-
-License Flags
-      --ignored-licenses strings   specify a list of license to ignore
-      --license-full               eagerly look for licenses in source code headers and license files
-
-Rego Flags
-      --config-data strings         specify paths from which data for the Rego policies will be recursively loaded
-      --config-policy strings       specify paths to the Rego policy files directory, applying config files
-      --policy-namespaces strings   Rego namespaces
-      --trace                       enable more verbose trace output for custom queries
-
-Client/Server Flags
-      --custom-headers strings   custom headers in client mode
-      --server string            server address in client mode
-      --token string             for authentication in client/server mode
-      --token-header string      specify a header name for token in client/server mode (default "Trivy-Token")
-
-Global Flags:
-      --cache-dir string          cache directory (default "/Users/teppei/Library/Caches/trivy")
-  -c, --config string             config path (default "trivy.yaml")
-  -d, --debug                     debug mode
-      --generate-default-config   write the default config to trivy-default.yaml
-      --insecure                  allow insecure server connections when using TLS
-  -q, --quiet                     suppress progress bar and log output
-      --timeout duration          timeout (default 5m0s)
-  -v, --version                   show version
-```

docs/docs/references/cli/sbom.md

@@ -1,70 +0,0 @@
-# SBOM
-
-```bash
-Scan SBOM for vulnerabilities
-
-Usage:
-  trivy sbom [flags] SBOM_PATH
-
-Examples:
-  # Scan CycloneDX and show the result in tables
-  $ trivy sbom /path/to/report.cdx
-
-  # Scan CycloneDX and generate a CycloneDX report
-  $ trivy sbom --format cyclonedx /path/to/report.cdx
-
-  # Scan CycloneDX-type attestation and show the result in tables
-  $ trivy sbom /path/to/report.cdx.intoto.jsonl
-
-
-Scan Flags
-      --offline-scan             do not issue API requests to identify dependencies
-      --security-checks string   comma-separated list of what security issues to detect (vuln,config,secret) (default "vuln,secret")
-      --skip-dirs strings        specify the directories where the traversal is skipped
-      --skip-files strings       specify the file paths to skip traversal
-
-Report Flags
-      --exit-code int          specify exit code when any security issues are found
-  -f, --format string          format (table, json, sarif, template, cyclonedx, spdx, spdx-json, github, cosign-vuln) (default "table")
-      --ignore-policy string   specify the Rego file path to evaluate each vulnerability
-      --ignorefile string      specify .trivyignore file (default ".trivyignore")
-      --list-all-pkgs          enabling the option will output all packages regardless of vulnerability
-  -o, --output string          output file name
-  -s, --severity string        severities of security issues to be displayed (comma separated) (default "UNKNOWN,LOW,MEDIUM,HIGH,CRITICAL")
-  -t, --template string        output template
-
-Cache Flags
-      --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
-      --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
-
-DB Flags
-      --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
-      --no-progress            suppress progress bar
-      --reset                  remove all caches and database
-      --skip-db-update         skip updating vulnerability database
-
-Vulnerability Flags
-      --ignore-unfixed     display only fixed vulnerabilities
-      --vuln-type string   comma-separated list of vulnerability types (os,library) (default "os,library")
-
-Client/Server Flags
-      --custom-headers strings   custom headers in client mode
-      --server string            server address in client mode
-      --token string             for authentication in client/server mode
-      --token-header string      specify a header name for token in client/server mode (default "Trivy-Token")
-
-Global Flags:
-      --cache-dir string          cache directory (default "/Users/teppei/Library/Caches/trivy")
-  -c, --config string             config path (default "trivy.yaml")
-  -d, --debug                     debug mode
-      --generate-default-config   write the default config to trivy-default.yaml
-      --insecure                  allow insecure server connections when using TLS
-  -q, --quiet                     suppress progress bar and log output
-      --timeout duration          timeout (default 5m0s)
-  -v, --version                   show version
-```

docs/docs/references/cli/server.md

@@ -1,49 +0,0 @@
-# Server
-
-```bash
-Server mode
-
-Usage:
-  trivy server [flags]
-
-Aliases:
-  server, s
-
-Examples:
-  # Run a server
-  $ trivy server
-
-  # Listen on 0.0.0.0:10000
-  $ trivy server --listen 0.0.0.0:10000
-
-
-Cache Flags
-      --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
-      --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
-
-DB Flags
-      --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
-      --no-progress            suppress progress bar
-      --reset                  remove all caches and database
-      --skip-db-update         skip updating vulnerability database
-
-Client/Server Flags
-      --listen string         listen address in server mode (default "localhost:4954")
-      --token string          for authentication in client/server mode
-      --token-header string   specify a header name for token in client/server mode (default "Trivy-Token")
-
-Global Flags:
-      --cache-dir string          cache directory (default "/Users/teppei/Library/Caches/trivy")
-  -c, --config string             config path (default "trivy.yaml")
-  -d, --debug                     debug mode
-      --generate-default-config   write the default config to trivy-default.yaml
-      --insecure                  allow insecure server connections when using TLS
-  -q, --quiet                     suppress progress bar and log output
-      --timeout duration          timeout (default 5m0s)
-  -v, --version                   show version
-```

docs/docs/references/cli/trivy.md

@@ -0,0 +1,60 @@
+## trivy
+
+Unified security scanner
+
+### Synopsis
+
+Scanner for vulnerabilities in container images, file systems, and Git repositories, as well as for configuration issues and hard-coded secrets
+
+```
+trivy [global flags] command [flags] target
+```
+
+### Examples
+
+```
+  # Scan a container image
+  $ trivy image python:3.4-alpine
+
+  # Scan a container image from a tar archive
+  $ trivy image --input ruby-3.1.tar
+
+  # Scan local filesystem
+  $ trivy fs .
+
+  # Run in server mode
+  $ trivy server
+```
+
+### Options
+
+```
+      --cache-dir string          cache directory (default "/home/shubham/.cache/trivy")
+  -c, --config string             config path (default "trivy.yaml")
+  -d, --debug                     debug mode
+  -f, --format string             version format (json)
+      --generate-default-config   write the default config to trivy-default.yaml
+  -h, --help                      help for trivy
+      --insecure                  allow insecure server connections when using TLS
+  -q, --quiet                     suppress progress bar and log output
+      --timeout duration          timeout (default 5m0s)
+  -v, --version                   show version
+```
+
+### SEE ALSO
+
+* [trivy aws](trivy_aws.md)	 - [EXPERIMENTAL] Scan AWS account
+* [trivy config](trivy_config.md)	 - Scan config files for misconfigurations
+* [trivy filesystem](trivy_filesystem.md)	 - Scan local filesystem
+* [trivy image](trivy_image.md)	 - Scan a container image
+* [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 rootfs](trivy_rootfs.md)	 - Scan rootfs
+* [trivy sbom](trivy_sbom.md)	 - Scan SBOM for vulnerabilities
+* [trivy server](trivy_server.md)	 - Server mode
+* [trivy version](trivy_version.md)	 - Print the version
+* [trivy vm](trivy_vm.md)	 - [EXPERIMENTAL] Scan a virtual machine image
+
+###### Auto generated by spf13/cobra on 16-Mar-2023

docs/docs/references/cli/trivy_aws.md

@@ -0,0 +1,117 @@
+## trivy aws
+
+[EXPERIMENTAL] Scan AWS account
+
+### Synopsis
+
+Scan an AWS account for misconfigurations. Trivy uses the same authentication methods as the AWS CLI. See https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html
+
+The following services are supported:
+- accessanalyzer
+- api-gateway
+- athena
+- cloudfront
+- cloudtrail
+- cloudwatch
+- codebuild
+- documentdb
+- dynamodb
+- ec2
+- ecr
+- ecs
+- efs
+- eks
+- elasticache
+- elasticsearch
+- elb
+- emr
+- iam
+- kinesis
+- kms
+- lambda
+- mq
+- msk
+- neptune
+- rds
+- redshift
+- s3
+- sns
+- sqs
+- ssm
+- workspaces
+
+
+```
+trivy aws [flags]
+```
+
+### Examples
+
+```
+  # basic scanning
+  $ trivy aws --region us-east-1
+
+  # limit scan to a single service:
+  $ trivy aws --region us-east-1 --service s3
+
+  # limit scan to multiple services:
+  $ trivy aws --region us-east-1 --service s3 --service ec2
+
+  # force refresh of cache for fresh results
+  $ trivy aws --region us-east-1 --update-cache
+
+```
+
+### Options
+
+```
+      --account string              The AWS account to scan. It's useful to specify this when reviewing cached results for multiple accounts.
+      --arn string                  The AWS ARN to show results for. Useful to filter results once a scan is cached.
+      --compliance string           compliance report to generate (aws-cis-1.2, aws-cis-1.4)
+      --config-data strings         specify paths from which data for the Rego policies will be recursively loaded
+      --config-policy strings       specify paths to the Rego policy files directory, applying config files
+      --dependency-tree             [EXPERIMENTAL] show dependency origin tree of vulnerable packages
+      --endpoint string             AWS Endpoint override
+      --exit-code int               specify exit code when any security issues are found
+  -f, --format string               format (table, json, template, sarif, cyclonedx, spdx, spdx-json, github, cosign-vuln) (default "table")
+      --helm-set strings            specify Helm values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
+      --helm-set-file strings       specify Helm values from respective files specified via the command line (can specify multiple or separate values with commas: key1=path1,key2=path2)
+      --helm-set-string strings     specify Helm string values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
+      --helm-values strings         specify paths to override the Helm values.yaml files
+  -h, --help                        help for aws
+      --ignore-policy string        specify the Rego file path to evaluate each vulnerability
+      --ignorefile string           specify .trivyignore file (default ".trivyignore")
+      --include-non-failures        include successes and exceptions, available with '--scanners config'
+      --list-all-pkgs               enabling the option will output all packages regardless of vulnerability
+      --max-cache-age duration      The maximum age of the cloud cache. Cached data will be requeried from the cloud provider if it is older than this. (default 24h0m0s)
+  -o, --output string               output file name
+      --policy-namespaces strings   Rego namespaces
+      --region string               AWS Region to scan
+      --report string               specify a report format for the output. (all,summary) (default "all")
+      --service strings             Only scan AWS Service(s) specified with this flag. Can specify multiple services using --service A --service B etc.
+  -s, --severity string             severities of security issues to be displayed (comma separated) (default "UNKNOWN,LOW,MEDIUM,HIGH,CRITICAL")
+      --skip-policy-update          skip fetching rego policy updates
+  -t, --template string             output template
+      --tf-vars strings             specify paths to override the Terraform tfvars files
+      --trace                       enable more verbose trace output for custom queries
+      --update-cache                Update the cache for the applicable cloud provider instead of using cached results.
+```
+
+### Options inherited from parent commands
+
+```
+      --cache-dir string          cache directory (default "/home/shubham/.cache/trivy")
+  -c, --config string             config path (default "trivy.yaml")
+  -d, --debug                     debug mode
+      --generate-default-config   write the default config to trivy-default.yaml
+      --insecure                  allow insecure server connections when using TLS
+  -q, --quiet                     suppress progress bar and log output
+      --timeout duration          timeout (default 5m0s)
+  -v, --version                   show version
+```
+
+### SEE ALSO
+
+* [trivy](trivy.md)	 - Unified security scanner
+
+###### Auto generated by spf13/cobra on 16-Mar-2023

docs/docs/references/cli/trivy_config.md

@@ -0,0 +1,61 @@
+## trivy config
+
+Scan config files for misconfigurations
+
+```
+trivy config [flags] DIR
+```
+
+### 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
+      --config-data strings         specify paths from which data for the Rego policies will be recursively loaded
+      --config-policy strings       specify paths to the Rego policy files directory, applying config files
+      --enable-modules strings      [EXPERIMENTAL] module names to enable
+      --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, template, sarif, cyclonedx, spdx, spdx-json, github, cosign-vuln) (default "table")
+      --helm-set strings            specify Helm values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
+      --helm-set-file strings       specify Helm values from respective files specified via the command line (can specify multiple or separate values with commas: key1=path1,key2=path2)
+      --helm-set-string strings     specify Helm string values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
+      --helm-values strings         specify paths to override the Helm values.yaml files
+  -h, --help                        help for config
+      --ignorefile string           specify .trivyignore file (default ".trivyignore")
+      --include-non-failures        include successes and exceptions, available with '--scanners config'
+      --k8s-version string          specify k8s version to validate outdated api by it (example: 1.21.0)
+      --module-dir string           specify directory to the wasm modules that will be loaded (default "/home/shubham/.trivy/modules")
+  -o, --output string               output file name
+      --policy-namespaces strings   Rego namespaces
+      --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
+  -s, --severity string             severities of security issues to be displayed (comma separated) (default "UNKNOWN,LOW,MEDIUM,HIGH,CRITICAL")
+      --skip-dirs strings           specify the directories where the traversal is skipped
+      --skip-files strings          specify the file paths to skip traversal
+      --skip-policy-update          skip fetching rego policy updates
+  -t, --template string             output template
+      --tf-vars strings             specify paths to override the Terraform tfvars files
+      --trace                       enable more verbose trace output for custom queries
+```
+
+### Options inherited from parent commands
+
+```
+      --cache-dir string          cache directory (default "/home/shubham/.cache/trivy")
+  -c, --config string             config path (default "trivy.yaml")
+  -d, --debug                     debug mode
+      --generate-default-config   write the default config to trivy-default.yaml
+      --insecure                  allow insecure server connections when using TLS
+  -q, --quiet                     suppress progress bar and log output
+      --timeout duration          timeout (default 5m0s)
+  -v, --version                   show version
+```
+
+### SEE ALSO
+
+* [trivy](trivy.md)	 - Unified security scanner
+
+###### Auto generated by spf13/cobra on 16-Mar-2023

docs/docs/references/cli/trivy_filesystem.md

@@ -0,0 +1,95 @@
+## trivy filesystem
+
+Scan local filesystem
+
+```
+trivy filesystem [flags] PATH
+```
+
+### Examples
+
+```
+  # Scan a local project including language-specific files
+  $ trivy fs /path/to/your_project
+
+  # Scan a single file
+  $ trivy fs ./trivy-ci-test/Pipfile.lock
+```
+
+### 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
+      --config-data strings         specify paths from which data for the Rego policies will be recursively loaded
+      --config-policy strings       specify paths to the Rego policy files directory, applying config files
+      --custom-headers strings      custom headers in client mode
+      --db-repository string        OCI repository to retrieve trivy-db from (default "ghcr.io/aquasecurity/trivy-db")
+      --dependency-tree             [EXPERIMENTAL] show dependency origin tree of vulnerable packages
+      --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
+      --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, template, sarif, cyclonedx, spdx, spdx-json, github, cosign-vuln) (default "table")
+      --helm-set strings            specify Helm values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
+      --helm-set-file strings       specify Helm values from respective files specified via the command line (can specify multiple or separate values with commas: key1=path1,key2=path2)
+      --helm-set-string strings     specify Helm string values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
+      --helm-values strings         specify paths to override the Helm values.yaml files
+  -h, --help                        help for filesystem
+      --ignore-policy string        specify the Rego file path to evaluate each vulnerability
+      --ignore-unfixed              display only fixed vulnerabilities
+      --ignored-licenses strings    specify a list of license to ignore
+      --ignorefile string           specify .trivyignore file (default ".trivyignore")
+      --include-non-failures        include successes and exceptions, available with '--scanners config'
+      --java-db-repository string   OCI repository to retrieve trivy-java-db from (default "ghcr.io/aquasecurity/trivy-java-db")
+      --license-full                eagerly look for licenses in source code headers and license files
+      --list-all-pkgs               enabling the option will output all packages regardless of vulnerability
+      --module-dir string           specify directory to the wasm modules that will be loaded (default "/home/shubham/.trivy/modules")
+      --no-progress                 suppress progress bar
+      --offline-scan                do not issue API requests to identify dependencies
+  -o, --output string               output file name
+      --policy-namespaces strings   Rego namespaces
+      --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
+      --rekor-url string            [EXPERIMENTAL] address of rekor STL server (default "https://rekor.sigstore.dev")
+      --reset                       remove all caches and database
+      --sbom-sources strings        [EXPERIMENTAL] try to retrieve SBOM from the specified sources (rekor)
+      --scanners strings            comma-separated list of what security issues to detect (vuln,config,secret,license) (default [vuln,secret])
+      --secret-config string        specify a path to config file for secret scanning (default "trivy-secret.yaml")
+      --server string               server address in client mode
+  -s, --severity string             severities of security issues to be displayed (comma separated) (default "UNKNOWN,LOW,MEDIUM,HIGH,CRITICAL")
+      --skip-db-update              skip updating vulnerability database
+      --skip-dirs strings           specify the directories where the traversal is skipped
+      --skip-files strings          specify the file paths to skip traversal
+      --skip-java-db-update         skip updating Java index database
+      --skip-policy-update          skip fetching rego policy updates
+      --slow                        scan over time with lower CPU and memory utilization
+  -t, --template string             output template
+      --tf-vars strings             specify paths to override the Terraform tfvars files
+      --token string                for authentication in client/server mode
+      --token-header string         specify a header name for token in client/server mode (default "Trivy-Token")
+      --trace                       enable more verbose trace output for custom queries
+      --vuln-type string            comma-separated list of vulnerability types (os,library) (default "os,library")
+```
+
+### Options inherited from parent commands
+
+```
+      --cache-dir string          cache directory (default "/home/shubham/.cache/trivy")
+  -c, --config string             config path (default "trivy.yaml")
+  -d, --debug                     debug mode
+      --generate-default-config   write the default config to trivy-default.yaml
+      --insecure                  allow insecure server connections when using TLS
+  -q, --quiet                     suppress progress bar and log output
+      --timeout duration          timeout (default 5m0s)
+  -v, --version                   show version
+```
+
+### SEE ALSO
+
+* [trivy](trivy.md)	 - Unified security scanner
+
+###### Auto generated by spf13/cobra on 16-Mar-2023

docs/docs/references/cli/trivy_image.md

@@ -0,0 +1,117 @@
+## trivy image
+
+Scan a container image
+
+```
+trivy image [flags] IMAGE_NAME
+```
+
+### Examples
+
+```
+  # Scan a container image
+  $ trivy image python:3.4-alpine
+
+  # Scan a container image from a tar archive
+  $ trivy image --input ruby-3.1.tar
+
+  # Filter by severities
+  $ trivy image --severity HIGH,CRITICAL alpine:3.15
+
+  # Ignore unfixed/unpatched vulnerabilities
+  $ trivy image --ignore-unfixed alpine:3.15
+
+  # Scan a container image in client mode
+  $ trivy image --server http://127.0.0.1:4954 alpine:latest
+
+  # Generate json result
+  $ trivy image --format json --output result.json alpine:3.15
+
+  # Generate a report in the CycloneDX format
+  $ trivy image --format cyclonedx --output result.cdx alpine:3.15
+```
+
+### 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
+      --compliance string              compliance report to generate (docker-cis)
+      --config-data strings            specify paths from which data for the Rego policies will be recursively loaded
+      --config-policy strings          specify paths to the Rego policy files directory, applying config files
+      --custom-headers strings         custom headers in client mode
+      --db-repository string           OCI repository to retrieve trivy-db from (default "ghcr.io/aquasecurity/trivy-db")
+      --dependency-tree                [EXPERIMENTAL] show dependency origin tree of vulnerable packages
+      --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
+      --exit-code int                  specify exit code when any security issues are found
+      --exit-on-eol int                exit with the specified code when the OS reaches end of service/life
+      --file-patterns strings          specify config file patterns
+  -f, --format string                  format (table, json, template, sarif, cyclonedx, spdx, spdx-json, github, cosign-vuln) (default "table")
+      --helm-set strings               specify Helm values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
+      --helm-set-file strings          specify Helm values from respective files specified via the command line (can specify multiple or separate values with commas: key1=path1,key2=path2)
+      --helm-set-string strings        specify Helm string values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
+      --helm-values strings            specify paths to override the Helm values.yaml files
+  -h, --help                           help for image
+      --ignore-policy string           specify the Rego file path to evaluate each vulnerability
+      --ignore-unfixed                 display only fixed vulnerabilities
+      --ignored-licenses strings       specify a list of license to ignore
+      --ignorefile string              specify .trivyignore file (default ".trivyignore")
+      --image-config-scanners string   comma-separated list of what security issues to detect on container image configurations (config,secret)
+      --include-non-failures           include successes and exceptions, available with '--scanners config'
+      --input string                   input file path instead of image name
+      --java-db-repository string      OCI repository to retrieve trivy-java-db from (default "ghcr.io/aquasecurity/trivy-java-db")
+      --license-full                   eagerly look for licenses in source code headers and license files
+      --list-all-pkgs                  enabling the option will output all packages regardless of vulnerability
+      --module-dir string              specify directory to the wasm modules that will be loaded (default "/home/shubham/.trivy/modules")
+      --no-progress                    suppress progress bar
+      --offline-scan                   do not issue API requests to identify dependencies
+  -o, --output string                  output file name
+      --platform string                set platform in the form os/arch if image is multi-platform capable
+      --policy-namespaces strings      Rego namespaces
+      --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
+      --rekor-url string               [EXPERIMENTAL] address of rekor STL server (default "https://rekor.sigstore.dev")
+      --removed-pkgs                   detect vulnerabilities of removed packages (only for Alpine)
+      --report string                  specify a format for the compliance report. (default "summary")
+      --reset                          remove all caches and database
+      --sbom-sources strings           [EXPERIMENTAL] try to retrieve SBOM from the specified sources (rekor)
+      --scanners strings               comma-separated list of what security issues to detect (vuln,config,secret,license) (default [vuln,secret])
+      --secret-config string           specify a path to config file for secret scanning (default "trivy-secret.yaml")
+      --server string                  server address in client mode
+  -s, --severity string                severities of security issues to be displayed (comma separated) (default "UNKNOWN,LOW,MEDIUM,HIGH,CRITICAL")
+      --skip-db-update                 skip updating vulnerability database
+      --skip-dirs strings              specify the directories where the traversal is skipped
+      --skip-files strings             specify the file paths to skip traversal
+      --skip-java-db-update            skip updating Java index database
+      --skip-policy-update             skip fetching rego policy updates
+      --slow                           scan over time with lower CPU and memory utilization
+  -t, --template string                output template
+      --tf-vars strings                specify paths to override the Terraform tfvars files
+      --token string                   for authentication in client/server mode
+      --token-header string            specify a header name for token in client/server mode (default "Trivy-Token")
+      --trace                          enable more verbose trace output for custom queries
+      --vuln-type string               comma-separated list of vulnerability types (os,library) (default "os,library")
+```
+
+### Options inherited from parent commands
+
+```
+      --cache-dir string          cache directory (default "/home/shubham/.cache/trivy")
+  -c, --config string             config path (default "trivy.yaml")
+  -d, --debug                     debug mode
+      --generate-default-config   write the default config to trivy-default.yaml
+      --insecure                  allow insecure server connections when using TLS
+  -q, --quiet                     suppress progress bar and log output
+      --timeout duration          timeout (default 5m0s)
+  -v, --version                   show version
+```
+
+### SEE ALSO
+
+* [trivy](trivy.md)	 - Unified security scanner
+
+###### Auto generated by spf13/cobra on 16-Mar-2023

docs/docs/references/cli/trivy_kubernetes.md

@@ -0,0 +1,104 @@
+## trivy kubernetes
+
+[EXPERIMENTAL] Scan kubernetes cluster
+
+```
+trivy kubernetes [flags] { cluster | all | specific resources like kubectl. eg: pods, pod/NAME }
+```
+
+### Examples
+
+```
+  # cluster scanning
+  $ trivy k8s --report summary cluster
+
+  # namespace scanning:
+  $ trivy k8s -n kube-system --report summary all
+
+  # resources scanning:
+  $ trivy k8s --report=summary deploy
+  $ trivy k8s --namespace=kube-system --report=summary deploy,configmaps
+
+  # resource scanning:
+  $ trivy k8s deployment/orion
+
+```
+
+### 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
+      --compliance string           compliance report to generate (k8s-nsa,k8s-cis, k8s-pss-baseline, k8s-pss-restricted)
+      --components strings          specify which components to scan (default [workload,infra])
+      --config-data strings         specify paths from which data for the Rego policies will be recursively loaded
+      --config-policy strings       specify paths to the Rego policy files directory, applying config files
+      --context string              specify a context to scan
+      --db-repository string        OCI repository to retrieve trivy-db from (default "ghcr.io/aquasecurity/trivy-db")
+      --dependency-tree             [EXPERIMENTAL] show dependency origin tree of vulnerable packages
+      --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
+      --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, template, sarif, cyclonedx, spdx, spdx-json, github, cosign-vuln) (default "table")
+      --helm-set strings            specify Helm values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
+      --helm-set-file strings       specify Helm values from respective files specified via the command line (can specify multiple or separate values with commas: key1=path1,key2=path2)
+      --helm-set-string strings     specify Helm string values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
+      --helm-values strings         specify paths to override the Helm values.yaml files
+  -h, --help                        help for kubernetes
+      --ignore-policy string        specify the Rego file path to evaluate each vulnerability
+      --ignore-unfixed              display only fixed vulnerabilities
+      --ignored-licenses strings    specify a list of license to ignore
+      --ignorefile string           specify .trivyignore file (default ".trivyignore")
+      --include-non-failures        include successes and exceptions, available with '--scanners config'
+      --java-db-repository string   OCI repository to retrieve trivy-java-db from (default "ghcr.io/aquasecurity/trivy-java-db")
+      --k8s-version string          specify k8s version to validate outdated api by it (example: 1.21.0)
+      --kubeconfig string           specify the kubeconfig file path to use
+      --license-full                eagerly look for licenses in source code headers and license files
+      --list-all-pkgs               enabling the option will output all packages regardless of vulnerability
+  -n, --namespace string            specify a namespace to scan
+      --no-progress                 suppress progress bar
+      --offline-scan                do not issue API requests to identify dependencies
+  -o, --output string               output file name
+      --policy-namespaces strings   Rego namespaces
+      --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
+      --rekor-url string            [EXPERIMENTAL] address of rekor STL server (default "https://rekor.sigstore.dev")
+      --report string               specify a report format for the output. (all,summary) (default "all")
+      --reset                       remove all caches and database
+      --sbom-sources strings        [EXPERIMENTAL] try to retrieve SBOM from the specified sources (rekor)
+      --scanners string             comma-separated list of what security issues to detect (vuln,config,secret,license) (default "vuln,config,secret,rbac")
+      --secret-config string        specify a path to config file for secret scanning (default "trivy-secret.yaml")
+  -s, --severity string             severities of security issues to be displayed (comma separated) (default "UNKNOWN,LOW,MEDIUM,HIGH,CRITICAL")
+      --skip-db-update              skip updating vulnerability database
+      --skip-dirs strings           specify the directories where the traversal is skipped
+      --skip-files strings          specify the file paths to skip traversal
+      --skip-java-db-update         skip updating Java index database
+      --skip-policy-update          skip fetching rego policy updates
+      --slow                        scan over time with lower CPU and memory utilization
+  -t, --template string             output template
+      --tf-vars strings             specify paths to override the Terraform tfvars files
+      --trace                       enable more verbose trace output for custom queries
+      --vuln-type string            comma-separated list of vulnerability types (os,library) (default "os,library")
+```
+
+### Options inherited from parent commands
+
+```
+      --cache-dir string          cache directory (default "/home/shubham/.cache/trivy")
+  -c, --config string             config path (default "trivy.yaml")
+  -d, --debug                     debug mode
+      --generate-default-config   write the default config to trivy-default.yaml
+      --insecure                  allow insecure server connections when using TLS
+  -q, --quiet                     suppress progress bar and log output
+      --timeout duration          timeout (default 5m0s)
+  -v, --version                   show version
+```
+
+### SEE ALSO
+
+* [trivy](trivy.md)	 - Unified security scanner
+
+###### Auto generated by spf13/cobra on 16-Mar-2023

docs/docs/references/cli/trivy_module.md

@@ -0,0 +1,32 @@
+## trivy module
+
+Manage modules
+
+### Options
+
+```
+      --enable-modules strings   [EXPERIMENTAL] module names to enable
+  -h, --help                     help for module
+      --module-dir string        specify directory to the wasm modules that will be loaded (default "/home/shubham/.trivy/modules")
+```
+
+### Options inherited from parent commands
+
+```
+      --cache-dir string          cache directory (default "/home/shubham/.cache/trivy")
+  -c, --config string             config path (default "trivy.yaml")
+  -d, --debug                     debug mode
+      --generate-default-config   write the default config to trivy-default.yaml
+      --insecure                  allow insecure server connections when using TLS
+  -q, --quiet                     suppress progress bar and log output
+      --timeout duration          timeout (default 5m0s)
+  -v, --version                   show version
+```
+
+### SEE ALSO
+
+* [trivy](trivy.md)	 - Unified security scanner
+* [trivy module install](trivy_module_install.md)	 - Install a module
+* [trivy module uninstall](trivy_module_uninstall.md)	 - Uninstall a module
+
+###### Auto generated by spf13/cobra on 16-Mar-2023

docs/docs/references/cli/trivy_module_install.md

@@ -0,0 +1,34 @@
+## trivy module install
+
+Install a module
+
+```
+trivy module install [flags] REPOSITORY
+```
+
+### Options
+
+```
+  -h, --help   help for install
+```
+
+### Options inherited from parent commands
+
+```
+      --cache-dir string          cache directory (default "/home/shubham/.cache/trivy")
+  -c, --config string             config path (default "trivy.yaml")
+  -d, --debug                     debug mode
+      --enable-modules strings    [EXPERIMENTAL] module names to enable
+      --generate-default-config   write the default config to trivy-default.yaml
+      --insecure                  allow insecure server connections when using TLS
+      --module-dir string         specify directory to the wasm modules that will be loaded (default "/home/shubham/.trivy/modules")
+  -q, --quiet                     suppress progress bar and log output
+      --timeout duration          timeout (default 5m0s)
+  -v, --version                   show version
+```
+
+### SEE ALSO
+
+* [trivy module](trivy_module.md)	 - Manage modules
+
+###### Auto generated by spf13/cobra on 16-Mar-2023

docs/docs/references/cli/trivy_module_uninstall.md

@@ -0,0 +1,34 @@
+## trivy module uninstall
+
+Uninstall a module
+
+```
+trivy module uninstall [flags] REPOSITORY
+```
+
+### Options
+
+```
+  -h, --help   help for uninstall
+```
+
+### Options inherited from parent commands
+
+```
+      --cache-dir string          cache directory (default "/home/shubham/.cache/trivy")
+  -c, --config string             config path (default "trivy.yaml")
+  -d, --debug                     debug mode
+      --enable-modules strings    [EXPERIMENTAL] module names to enable
+      --generate-default-config   write the default config to trivy-default.yaml
+      --insecure                  allow insecure server connections when using TLS
+      --module-dir string         specify directory to the wasm modules that will be loaded (default "/home/shubham/.trivy/modules")
+  -q, --quiet                     suppress progress bar and log output
+      --timeout duration          timeout (default 5m0s)
+  -v, --version                   show version
+```
+
+### SEE ALSO
+
+* [trivy module](trivy_module.md)	 - Manage modules
+
+###### Auto generated by spf13/cobra on 16-Mar-2023

docs/docs/references/cli/trivy_plugin.md

@@ -0,0 +1,34 @@
+## trivy plugin
+
+Manage plugins
+
+### Options
+
+```
+  -h, --help   help for plugin
+```
+
+### Options inherited from parent commands
+
+```
+      --cache-dir string          cache directory (default "/home/shubham/.cache/trivy")
+  -c, --config string             config path (default "trivy.yaml")
+  -d, --debug                     debug mode
+      --generate-default-config   write the default config to trivy-default.yaml
+      --insecure                  allow insecure server connections when using TLS
+  -q, --quiet                     suppress progress bar and log output
+      --timeout duration          timeout (default 5m0s)
+  -v, --version                   show version
+```
+
+### SEE ALSO
+
+* [trivy](trivy.md)	 - Unified security scanner
+* [trivy plugin info](trivy_plugin_info.md)	 - Show information about the specified plugin
+* [trivy plugin install](trivy_plugin_install.md)	 - Install a plugin
+* [trivy plugin list](trivy_plugin_list.md)	 - List installed plugin
+* [trivy plugin run](trivy_plugin_run.md)	 - Run a plugin on the fly
+* [trivy plugin uninstall](trivy_plugin_uninstall.md)	 - Uninstall a plugin
+* [trivy plugin update](trivy_plugin_update.md)	 - Update an existing plugin
+
+###### Auto generated by spf13/cobra on 16-Mar-2023

docs/docs/references/cli/trivy_plugin_info.md

@@ -0,0 +1,32 @@
+## trivy plugin info
+
+Show information about the specified plugin
+
+```
+trivy plugin info PLUGIN_NAME
+```
+
+### Options
+
+```
+  -h, --help   help for info
+```
+
+### Options inherited from parent commands
+
+```
+      --cache-dir string          cache directory (default "/home/shubham/.cache/trivy")
+  -c, --config string             config path (default "trivy.yaml")
+  -d, --debug                     debug mode
+      --generate-default-config   write the default config to trivy-default.yaml
+      --insecure                  allow insecure server connections when using TLS
+  -q, --quiet                     suppress progress bar and log output
+      --timeout duration          timeout (default 5m0s)
+  -v, --version                   show version
+```
+
+### SEE ALSO
+
+* [trivy plugin](trivy_plugin.md)	 - Manage plugins
+
+###### Auto generated by spf13/cobra on 16-Mar-2023

docs/docs/references/cli/trivy_plugin_install.md

@@ -0,0 +1,32 @@
+## trivy plugin install
+
+Install a plugin
+
+```
+trivy plugin install URL | FILE_PATH
+```
+
+### Options
+
+```
+  -h, --help   help for install
+```
+
+### Options inherited from parent commands
+
+```
+      --cache-dir string          cache directory (default "/home/shubham/.cache/trivy")
+  -c, --config string             config path (default "trivy.yaml")
+  -d, --debug                     debug mode
+      --generate-default-config   write the default config to trivy-default.yaml
+      --insecure                  allow insecure server connections when using TLS
+  -q, --quiet                     suppress progress bar and log output
+      --timeout duration          timeout (default 5m0s)
+  -v, --version                   show version
+```
+
+### SEE ALSO
+
+* [trivy plugin](trivy_plugin.md)	 - Manage plugins
+
+###### Auto generated by spf13/cobra on 16-Mar-2023

docs/docs/references/cli/trivy_plugin_list.md

@@ -1,23 +1,21 @@
-# Module
+## trivy plugin list
 
-```bash
-Manage modules
+List installed plugin
 
-Usage:
-  trivy module [command]
+```
+trivy plugin list
+```
 
-Aliases:
-  module, m
+### Options
 
-Available Commands:
-  install     Install a module
-  uninstall   Uninstall a module
+```
+  -h, --help   help for list
+```
 
-Flags:
-  -h, --help   help for module
+### Options inherited from parent commands
 
-Global Flags:
-      --cache-dir string          cache directory (default "/Users/teppei/Library/Caches/trivy")
+```
+      --cache-dir string          cache directory (default "/home/shubham/.cache/trivy")
   -c, --config string             config path (default "trivy.yaml")
   -d, --debug                     debug mode
       --generate-default-config   write the default config to trivy-default.yaml
@@ -25,6 +23,10 @@ Global Flags:
   -q, --quiet                     suppress progress bar and log output
       --timeout duration          timeout (default 5m0s)
   -v, --version                   show version
+```
 
-Use "trivy module [command] --help" for more information about a command.
-```
+### SEE ALSO
+
+* [trivy plugin](trivy_plugin.md)	 - Manage plugins
+
+###### Auto generated by spf13/cobra on 16-Mar-2023

docs/docs/references/cli/trivy_plugin_run.md

@@ -0,0 +1,32 @@
+## trivy plugin run
+
+Run a plugin on the fly
+
+```
+trivy plugin run URL | FILE_PATH
+```
+
+### Options
+
+```
+  -h, --help   help for run
+```
+
+### Options inherited from parent commands
+
+```
+      --cache-dir string          cache directory (default "/home/shubham/.cache/trivy")
+  -c, --config string             config path (default "trivy.yaml")
+  -d, --debug                     debug mode
+      --generate-default-config   write the default config to trivy-default.yaml
+      --insecure                  allow insecure server connections when using TLS
+  -q, --quiet                     suppress progress bar and log output
+      --timeout duration          timeout (default 5m0s)
+  -v, --version                   show version
+```
+
+### SEE ALSO
+
+* [trivy plugin](trivy_plugin.md)	 - Manage plugins
+
+###### Auto generated by spf13/cobra on 16-Mar-2023

docs/docs/references/cli/trivy_plugin_uninstall.md

@@ -0,0 +1,32 @@
+## trivy plugin uninstall
+
+Uninstall a plugin
+
+```
+trivy plugin uninstall PLUGIN_NAME
+```
+
+### Options
+
+```
+  -h, --help   help for uninstall
+```
+
+### Options inherited from parent commands
+
+```
+      --cache-dir string          cache directory (default "/home/shubham/.cache/trivy")
+  -c, --config string             config path (default "trivy.yaml")
+  -d, --debug                     debug mode
+      --generate-default-config   write the default config to trivy-default.yaml
+      --insecure                  allow insecure server connections when using TLS
+  -q, --quiet                     suppress progress bar and log output
+      --timeout duration          timeout (default 5m0s)
+  -v, --version                   show version
+```
+
+### SEE ALSO
+
+* [trivy plugin](trivy_plugin.md)	 - Manage plugins
+
+###### Auto generated by spf13/cobra on 16-Mar-2023

docs/docs/references/cli/trivy_plugin_update.md

@@ -0,0 +1,32 @@
+## trivy plugin update
+
+Update an existing plugin
+
+```
+trivy plugin update PLUGIN_NAME
+```
+
+### Options
+
+```
+  -h, --help   help for update
+```
+
+### Options inherited from parent commands
+
+```
+      --cache-dir string          cache directory (default "/home/shubham/.cache/trivy")
+  -c, --config string             config path (default "trivy.yaml")
+  -d, --debug                     debug mode
+      --generate-default-config   write the default config to trivy-default.yaml
+      --insecure                  allow insecure server connections when using TLS
+  -q, --quiet                     suppress progress bar and log output
+      --timeout duration          timeout (default 5m0s)
+  -v, --version                   show version
+```
+
+### SEE ALSO
+
+* [trivy plugin](trivy_plugin.md)	 - Manage plugins
+
+###### Auto generated by spf13/cobra on 16-Mar-2023

docs/docs/references/cli/trivy_repository.md

@@ -0,0 +1,95 @@
+## trivy repository
+
+Scan a remote repository
+
+```
+trivy repository [flags] REPO_URL
+```
+
+### Examples
+
+```
+  # Scan your remote git repository
+  $ trivy repo https://github.com/knqyf263/trivy-ci-test
+```
+
+### Options
+
+```
+      --branch string               pass the branch name to be scanned
+      --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
+      --commit string               pass the commit hash to be scanned
+      --config-data strings         specify paths from which data for the Rego policies will be recursively loaded
+      --config-policy strings       specify paths to the Rego policy files directory, applying config files
+      --custom-headers strings      custom headers in client mode
+      --db-repository string        OCI repository to retrieve trivy-db from (default "ghcr.io/aquasecurity/trivy-db")
+      --dependency-tree             [EXPERIMENTAL] show dependency origin tree of vulnerable packages
+      --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
+      --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, template, sarif, cyclonedx, spdx, spdx-json, github, cosign-vuln) (default "table")
+      --helm-set strings            specify Helm values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
+      --helm-set-file strings       specify Helm values from respective files specified via the command line (can specify multiple or separate values with commas: key1=path1,key2=path2)
+      --helm-set-string strings     specify Helm string values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
+      --helm-values strings         specify paths to override the Helm values.yaml files
+  -h, --help                        help for repository
+      --ignore-policy string        specify the Rego file path to evaluate each vulnerability
+      --ignore-unfixed              display only fixed vulnerabilities
+      --ignored-licenses strings    specify a list of license to ignore
+      --ignorefile string           specify .trivyignore file (default ".trivyignore")
+      --include-non-failures        include successes and exceptions, available with '--scanners config'
+      --java-db-repository string   OCI repository to retrieve trivy-java-db from (default "ghcr.io/aquasecurity/trivy-java-db")
+      --license-full                eagerly look for licenses in source code headers and license files
+      --list-all-pkgs               enabling the option will output all packages regardless of vulnerability
+      --module-dir string           specify directory to the wasm modules that will be loaded (default "/home/shubham/.trivy/modules")
+      --no-progress                 suppress progress bar
+      --offline-scan                do not issue API requests to identify dependencies
+  -o, --output string               output file name
+      --policy-namespaces strings   Rego namespaces
+      --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
+      --rekor-url string            [EXPERIMENTAL] address of rekor STL server (default "https://rekor.sigstore.dev")
+      --reset                       remove all caches and database
+      --sbom-sources strings        [EXPERIMENTAL] try to retrieve SBOM from the specified sources (rekor)
+      --scanners strings            comma-separated list of what security issues to detect (vuln,config,secret,license) (default [vuln,secret])
+      --secret-config string        specify a path to config file for secret scanning (default "trivy-secret.yaml")
+      --server string               server address in client mode
+  -s, --severity string             severities of security issues to be displayed (comma separated) (default "UNKNOWN,LOW,MEDIUM,HIGH,CRITICAL")
+      --skip-db-update              skip updating vulnerability database
+      --skip-dirs strings           specify the directories where the traversal is skipped
+      --skip-files strings          specify the file paths to skip traversal
+      --skip-java-db-update         skip updating Java index database
+      --skip-policy-update          skip fetching rego policy updates
+      --slow                        scan over time with lower CPU and memory utilization
+      --tag string                  pass the tag name to be scanned
+  -t, --template string             output template
+      --tf-vars strings             specify paths to override the Terraform tfvars files
+      --token string                for authentication in client/server mode
+      --token-header string         specify a header name for token in client/server mode (default "Trivy-Token")
+      --trace                       enable more verbose trace output for custom queries
+      --vuln-type string            comma-separated list of vulnerability types (os,library) (default "os,library")
+```
+
+### Options inherited from parent commands
+
+```
+      --cache-dir string          cache directory (default "/home/shubham/.cache/trivy")
+  -c, --config string             config path (default "trivy.yaml")
+  -d, --debug                     debug mode
+      --generate-default-config   write the default config to trivy-default.yaml
+      --insecure                  allow insecure server connections when using TLS
+  -q, --quiet                     suppress progress bar and log output
+      --timeout duration          timeout (default 5m0s)
+  -v, --version                   show version
+```
+
+### SEE ALSO
+
+* [trivy](trivy.md)	 - Unified security scanner
+
+###### Auto generated by spf13/cobra on 16-Mar-2023

docs/docs/references/cli/trivy_rootfs.md

@@ -0,0 +1,99 @@
+## trivy rootfs
+
+Scan rootfs
+
+```
+trivy rootfs [flags] ROOTDIR
+```
+
+### Examples
+
+```
+  # Scan unpacked filesystem
+  $ docker export $(docker create alpine:3.10.2) | tar -C /tmp/rootfs -xvf -
+  $ trivy rootfs /tmp/rootfs
+
+  # Scan from inside a container
+  $ docker run --rm -it alpine:3.11
+  / # curl -sfL https://raw.githubusercontent.com/aquasecurity/trivy/main/contrib/install.sh | sh -s -- -b /usr/local/bin
+  / # trivy rootfs /
+```
+
+### 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
+      --config-data strings         specify paths from which data for the Rego policies will be recursively loaded
+      --config-policy strings       specify paths to the Rego policy files directory, applying config files
+      --custom-headers strings      custom headers in client mode
+      --db-repository string        OCI repository to retrieve trivy-db from (default "ghcr.io/aquasecurity/trivy-db")
+      --dependency-tree             [EXPERIMENTAL] show dependency origin tree of vulnerable packages
+      --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
+      --exit-code int               specify exit code when any security issues are found
+      --exit-on-eol int             exit with the specified code when the OS reaches end of service/life
+      --file-patterns strings       specify config file patterns
+  -f, --format string               format (table, json, template, sarif, cyclonedx, spdx, spdx-json, github, cosign-vuln) (default "table")
+      --helm-set strings            specify Helm values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
+      --helm-set-file strings       specify Helm values from respective files specified via the command line (can specify multiple or separate values with commas: key1=path1,key2=path2)
+      --helm-set-string strings     specify Helm string values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
+      --helm-values strings         specify paths to override the Helm values.yaml files
+  -h, --help                        help for rootfs
+      --ignore-policy string        specify the Rego file path to evaluate each vulnerability
+      --ignore-unfixed              display only fixed vulnerabilities
+      --ignored-licenses strings    specify a list of license to ignore
+      --ignorefile string           specify .trivyignore file (default ".trivyignore")
+      --include-non-failures        include successes and exceptions, available with '--scanners config'
+      --java-db-repository string   OCI repository to retrieve trivy-java-db from (default "ghcr.io/aquasecurity/trivy-java-db")
+      --license-full                eagerly look for licenses in source code headers and license files
+      --list-all-pkgs               enabling the option will output all packages regardless of vulnerability
+      --module-dir string           specify directory to the wasm modules that will be loaded (default "/home/shubham/.trivy/modules")
+      --no-progress                 suppress progress bar
+      --offline-scan                do not issue API requests to identify dependencies
+  -o, --output string               output file name
+      --policy-namespaces strings   Rego namespaces
+      --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
+      --rekor-url string            [EXPERIMENTAL] address of rekor STL server (default "https://rekor.sigstore.dev")
+      --reset                       remove all caches and database
+      --sbom-sources strings        [EXPERIMENTAL] try to retrieve SBOM from the specified sources (rekor)
+      --scanners strings            comma-separated list of what security issues to detect (vuln,config,secret,license) (default [vuln,secret])
+      --secret-config string        specify a path to config file for secret scanning (default "trivy-secret.yaml")
+      --server string               server address in client mode
+  -s, --severity string             severities of security issues to be displayed (comma separated) (default "UNKNOWN,LOW,MEDIUM,HIGH,CRITICAL")
+      --skip-db-update              skip updating vulnerability database
+      --skip-dirs strings           specify the directories where the traversal is skipped
+      --skip-files strings          specify the file paths to skip traversal
+      --skip-java-db-update         skip updating Java index database
+      --skip-policy-update          skip fetching rego policy updates
+      --slow                        scan over time with lower CPU and memory utilization
+  -t, --template string             output template
+      --tf-vars strings             specify paths to override the Terraform tfvars files
+      --token string                for authentication in client/server mode
+      --token-header string         specify a header name for token in client/server mode (default "Trivy-Token")
+      --trace                       enable more verbose trace output for custom queries
+      --vuln-type string            comma-separated list of vulnerability types (os,library) (default "os,library")
+```
+
+### Options inherited from parent commands
+
+```
+      --cache-dir string          cache directory (default "/home/shubham/.cache/trivy")
+  -c, --config string             config path (default "trivy.yaml")
+  -d, --debug                     debug mode
+      --generate-default-config   write the default config to trivy-default.yaml
+      --insecure                  allow insecure server connections when using TLS
+  -q, --quiet                     suppress progress bar and log output
+      --timeout duration          timeout (default 5m0s)
+  -v, --version                   show version
+```
+
+### SEE ALSO
+
+* [trivy](trivy.md)	 - Unified security scanner
+
+###### Auto generated by spf13/cobra on 16-Mar-2023

docs/docs/references/cli/trivy_sbom.md

@@ -0,0 +1,84 @@
+## trivy sbom
+
+Scan SBOM for vulnerabilities
+
+```
+trivy sbom [flags] SBOM_PATH
+```
+
+### Examples
+
+```
+  # Scan CycloneDX and show the result in tables
+  $ trivy sbom /path/to/report.cdx
+
+  # Scan CycloneDX and generate a CycloneDX report
+  $ trivy sbom --format cyclonedx /path/to/report.cdx
+
+  # Scan CycloneDX-type attestation and show the result in tables
+  $ trivy sbom /path/to/report.cdx.intoto.jsonl
+
+```
+
+### 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
+      --compliance string           compliance report to generate
+      --custom-headers strings      custom headers in client mode
+      --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
+      --exit-code int               specify exit code when any security issues are found
+      --exit-on-eol int             exit with the specified code when the OS reaches end of service/life
+      --file-patterns strings       specify config file patterns
+  -f, --format string               format (table, json, template, sarif, cyclonedx, spdx, spdx-json, github, cosign-vuln) (default "table")
+  -h, --help                        help for sbom
+      --ignore-policy string        specify the Rego file path to evaluate each vulnerability
+      --ignore-unfixed              display only fixed vulnerabilities
+      --ignorefile string           specify .trivyignore file (default ".trivyignore")
+      --java-db-repository string   OCI repository to retrieve trivy-java-db from (default "ghcr.io/aquasecurity/trivy-java-db")
+      --list-all-pkgs               enabling the option will output all packages regardless of vulnerability
+      --no-progress                 suppress progress bar
+      --offline-scan                do not issue API requests to identify dependencies
+  -o, --output string               output file name
+      --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
+      --rekor-url string            [EXPERIMENTAL] address of rekor STL server (default "https://rekor.sigstore.dev")
+      --reset                       remove all caches and database
+      --sbom-sources strings        [EXPERIMENTAL] try to retrieve SBOM from the specified sources (rekor)
+      --scanners strings            comma-separated list of what security issues to detect (vuln,config,secret,license) (default [vuln,secret])
+      --server string               server address in client mode
+  -s, --severity string             severities of security issues to be displayed (comma separated) (default "UNKNOWN,LOW,MEDIUM,HIGH,CRITICAL")
+      --skip-db-update              skip updating vulnerability database
+      --skip-dirs strings           specify the directories where the traversal is skipped
+      --skip-files strings          specify the file paths to skip traversal
+      --skip-java-db-update         skip updating Java index database
+      --slow                        scan over time with lower CPU and memory utilization
+  -t, --template string             output template
+      --token string                for authentication in client/server mode
+      --token-header string         specify a header name for token in client/server mode (default "Trivy-Token")
+      --vuln-type string            comma-separated list of vulnerability types (os,library) (default "os,library")
+```
+
+### Options inherited from parent commands
+
+```
+      --cache-dir string          cache directory (default "/home/shubham/.cache/trivy")
+  -c, --config string             config path (default "trivy.yaml")
+  -d, --debug                     debug mode
+      --generate-default-config   write the default config to trivy-default.yaml
+      --insecure                  allow insecure server connections when using TLS
+  -q, --quiet                     suppress progress bar and log output
+      --timeout duration          timeout (default 5m0s)
+  -v, --version                   show version
+```
+
+### SEE ALSO
+
+* [trivy](trivy.md)	 - Unified security scanner
+
+###### Auto generated by spf13/cobra on 16-Mar-2023

docs/docs/references/cli/trivy_server.md

@@ -0,0 +1,62 @@
+## trivy server
+
+Server mode
+
+```
+trivy server [flags]
+```
+
+### Examples
+
+```
+  # Run a server
+  $ trivy server
+
+  # Listen on 0.0.0.0:10000
+  $ trivy server --listen 0.0.0.0:10000
+
+```
+
+### 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/shubham/.trivy/modules")
+      --no-progress                 suppress progress bar
+      --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
+      --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")
+```
+
+### Options inherited from parent commands
+
+```
+      --cache-dir string          cache directory (default "/home/shubham/.cache/trivy")
+  -c, --config string             config path (default "trivy.yaml")
+  -d, --debug                     debug mode
+      --generate-default-config   write the default config to trivy-default.yaml
+      --insecure                  allow insecure server connections when using TLS
+  -q, --quiet                     suppress progress bar and log output
+      --timeout duration          timeout (default 5m0s)
+  -v, --version                   show version
+```
+
+### SEE ALSO
+
+* [trivy](trivy.md)	 - Unified security scanner
+
+###### Auto generated by spf13/cobra on 16-Mar-2023

docs/docs/references/cli/trivy_version.md

@@ -0,0 +1,33 @@
+## trivy version
+
+Print the version
+
+```
+trivy version [flags]
+```
+
+### Options
+
+```
+  -f, --format string   version format (json)
+  -h, --help            help for version
+```
+
+### Options inherited from parent commands
+
+```
+      --cache-dir string          cache directory (default "/home/shubham/.cache/trivy")
+  -c, --config string             config path (default "trivy.yaml")
+  -d, --debug                     debug mode
+      --generate-default-config   write the default config to trivy-default.yaml
+      --insecure                  allow insecure server connections when using TLS
+  -q, --quiet                     suppress progress bar and log output
+      --timeout duration          timeout (default 5m0s)
+  -v, --version                   show version
+```
+
+### SEE ALSO
+
+* [trivy](trivy.md)	 - Unified security scanner
+
+###### Auto generated by spf13/cobra on 16-Mar-2023

docs/docs/references/cli/trivy_vm.md

@@ -0,0 +1,94 @@
+## trivy vm
+
+[EXPERIMENTAL] Scan a virtual machine image
+
+```
+trivy vm [flags] VM_IMAGE
+```
+
+### Examples
+
+```
+  # Scan your AWS AMI
+  $ trivy vm --scanners vuln ami:${your_ami_id}
+
+  # Scan your AWS EBS snapshot
+  $ trivy vm ebs:${your_ebs_snapshot_id}
+
+```
+
+### Options
+
+```
+      --aws-region string           AWS region to scan
+      --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
+      --compliance string           compliance report to generate
+      --custom-headers strings      custom headers in client mode
+      --db-repository string        OCI repository to retrieve trivy-db from (default "ghcr.io/aquasecurity/trivy-db")
+      --dependency-tree             [EXPERIMENTAL] show dependency origin tree of vulnerable packages
+      --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
+      --exit-code int               specify exit code when any security issues are found
+      --exit-on-eol int             exit with the specified code when the OS reaches end of service/life
+      --file-patterns strings       specify config file patterns
+  -f, --format string               format (table, json, template, sarif, cyclonedx, spdx, spdx-json, github, cosign-vuln) (default "table")
+      --helm-set strings            specify Helm values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
+      --helm-set-file strings       specify Helm values from respective files specified via the command line (can specify multiple or separate values with commas: key1=path1,key2=path2)
+      --helm-set-string strings     specify Helm string values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
+      --helm-values strings         specify paths to override the Helm values.yaml files
+  -h, --help                        help for vm
+      --ignore-policy string        specify the Rego file path to evaluate each vulnerability
+      --ignore-unfixed              display only fixed vulnerabilities
+      --ignored-licenses strings    specify a list of license to ignore
+      --ignorefile string           specify .trivyignore file (default ".trivyignore")
+      --include-non-failures        include successes and exceptions, available with '--scanners config'
+      --java-db-repository string   OCI repository to retrieve trivy-java-db from (default "ghcr.io/aquasecurity/trivy-java-db")
+      --license-full                eagerly look for licenses in source code headers and license files
+      --list-all-pkgs               enabling the option will output all packages regardless of vulnerability
+      --module-dir string           specify directory to the wasm modules that will be loaded (default "/home/shubham/.trivy/modules")
+      --no-progress                 suppress progress bar
+      --offline-scan                do not issue API requests to identify dependencies
+  -o, --output string               output file name
+      --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
+      --rekor-url string            [EXPERIMENTAL] address of rekor STL server (default "https://rekor.sigstore.dev")
+      --reset                       remove all caches and database
+      --sbom-sources strings        [EXPERIMENTAL] try to retrieve SBOM from the specified sources (rekor)
+      --scanners strings            comma-separated list of what security issues to detect (vuln,config,secret,license) (default [vuln,secret])
+      --secret-config string        specify a path to config file for secret scanning (default "trivy-secret.yaml")
+      --server string               server address in client mode
+  -s, --severity string             severities of security issues to be displayed (comma separated) (default "UNKNOWN,LOW,MEDIUM,HIGH,CRITICAL")
+      --skip-db-update              skip updating vulnerability database
+      --skip-dirs strings           specify the directories where the traversal is skipped
+      --skip-files strings          specify the file paths to skip traversal
+      --skip-java-db-update         skip updating Java index database
+      --slow                        scan over time with lower CPU and memory utilization
+  -t, --template string             output template
+      --tf-vars strings             specify paths to override the Terraform tfvars files
+      --token string                for authentication in client/server mode
+      --token-header string         specify a header name for token in client/server mode (default "Trivy-Token")
+      --vuln-type string            comma-separated list of vulnerability types (os,library) (default "os,library")
+```
+
+### Options inherited from parent commands
+
+```
+      --cache-dir string          cache directory (default "/home/shubham/.cache/trivy")
+  -c, --config string             config path (default "trivy.yaml")
+  -d, --debug                     debug mode
+      --generate-default-config   write the default config to trivy-default.yaml
+      --insecure                  allow insecure server connections when using TLS
+  -q, --quiet                     suppress progress bar and log output
+      --timeout duration          timeout (default 5m0s)
+  -v, --version                   show version
+```
+
+### SEE ALSO
+
+* [trivy](trivy.md)	 - Unified security scanner
+
+###### Auto generated by spf13/cobra on 16-Mar-2023

docs/docs/references/customization/config-file.md

@@ -25,7 +25,8 @@ timeout: 10m
 
 # Same as '--cache-dir'
 # Default is your system cache dir
-cache-dir: $HOME/.cache/trivy
+cache:
+  dir: $HOME/.cache/trivy
 ```
 
 ## Report Options
@@ -41,7 +42,7 @@ report: all
 
 # Same as '--template'
 # Default is empty
-template: 
+template:
 
 # Same as '--dependency-tree'
 # Default is false
@@ -63,6 +64,10 @@ ignore-policy:
 # Default is 0
 exit-code: 0
 
+# Same as '--exit-on-eol'
+# Default is 0
+exit-on-eol: 0
+
 # Same as '--output'
 # Default is empty (stdout)
 output:
@@ -92,19 +97,19 @@ scan:
   skip-dirs:
     - usr/local/
     - etc/
-  
+
   # Same as '--skip-files'
   # Default is empty
   skip-files:
     - package-dev.json
-  
+
   # Same as '--offline-scan'
   # Default is false
   offline-scan: false
-  
-  # Same as '--security-checks'
+
+  # Same as '--scanners'
   # Default depends on subcommand
-  security-checks:
+  scanners:
     - vuln
     - config
     - secret
@@ -115,23 +120,23 @@ scan:
 ```yaml
 cache:
   # Same as '--cache-backend'
-  # Default is 'fs' 
+  # Default is 'fs'
   backend: 'fs'
-  
+
   # Same as '--cache-ttl'
-  # Default is 0 (no ttl) 
+  # Default is 0 (no ttl)
   ttl: 0
-  
+
   # Redis options
   redis:
     # Same as '--redis-ca'
     # Default is empty
     ca:
-    
+
     # Same as '--redis-cert'
     # Default is empty
     cert:
-    
+
     # Same as '--redis-key'
     # Default is empty
     key:
@@ -144,14 +149,35 @@ db:
   # Same as '--skip-db-update'
   # Default is false
   skip-update: false
-  
+
   # Same as '--no-progress'
   # Default is false
   no-progress: false
-  
+
   # Same as '--db-repository'
-  # Default is 'github.com/aquasecurity-trivy-repo'
-  repository: github.com/aquasecurity-trivy-repo
+  # Default is 'ghcr.io/aquasecurity/trivy-db'
+  repository: ghcr.io/aquasecurity/trivy-db
+
+  # Same as '--java-db-repository'
+  # Default is 'ghcr.io/aquasecurity/trivy-java-db'
+  java-repository: ghcr.io/aquasecurity/trivy-java-db
+```
+
+## Registry Options
+
+```yaml
+registry:
+  # Same as '--username'
+  # Default is empty
+  username:
+
+  # Same as '--password'
+  # Default is empty
+  password:
+    
+  # Same as '--registry-token'
+  # Default is empty
+  registry-token:
 ```
 
 ## Image Options
@@ -162,7 +188,7 @@ image:
   # Same as '--input' (available with 'trivy image')
   # Default is empty
   input:
-  
+
   # Same as '--removed-pkgs'
   # Default is false
   removed-pkgs: false
@@ -178,7 +204,7 @@ vulnerability:
   type:
     - os
     - library
-  
+
   # Same as '--ignore-unfixed'
   # Default is false
   ignore-unfixed: false
@@ -265,25 +291,25 @@ kubernetes:
   # Same as '--context'
   # Default is empty
   context:
-  
+
   # Same as '--namespace'
   # Default is empty
   namespace:
 ```
 
 ## Repository Options
-Available with git repository scanning (`trivy repo`) 
+Available with git repository scanning (`trivy repo`)
 
 ```yaml
 repository:
   # Same as '--branch'
   # Default is empty
   branch:
-  
+
   # Same as '--commit'
   # Default is empty
   commit:
-  
+
   # Same as '--tag'
   # Default is empty
   tag:
@@ -297,21 +323,21 @@ server:
   # Same as '--server' (available in client mode)
   # Default is empty
   addr: http://localhost:4954
-  
+
   # Same as '--token'
   # Default is empty
   token: "something-secret"
-  
+
   # Same as '--token-header'
   # Default is 'Trivy-Token'
   token-header: 'My-Token-Header'
-  
+
   # Same as '--custom-headers'
   # Default is empty
   custom-headers:
     - scanner: trivy
     - x-api-token: xxx
-    
+
   # Same as '--listen' (available in server mode)
   # Default is 'localhost:4954'
   listen: 0.0.0.0:10000
@@ -325,18 +351,18 @@ Available for cloud scanning (currently only `trivy aws`)
 cloud:
   # whether to force a cache update for every scan
   update-cache: false
-  
+
   # how old cached results can be before being invalidated
   max-cache-age: 24h
-  
+
   # aws-specific cloud settings
   aws:
     # the aws region to use
     region: us-east-1
-    
+
     # the aws endpoint to use (not required for general use)
     endpoint: https://my.custom.aws.endpoint
-    
+
     # the aws account to use (this will be determined from your environment when not set)
     account: 123456789012
 ```

docs/docs/references/troubleshooting.md

@@ -39,49 +39,23 @@ https://developer.github.com/v3/#rate-limiting
 $ GITHUB_TOKEN=XXXXXXXXXX trivy alpine:3.10
 ```
 
-### Maven rate limiting / inconsistent jar vulnerability reporting
+### Unable to open JAR files
 
 !!! error
     ``` bash
     $ trivy image ...
     ...
-    status 403 Forbidden from http://search.maven.org/solrsearch/select
+    failed to analyze file: failed to analyze usr/lib/jvm/java-1.8-openjdk/lib/tools.jar: unable to open usr/lib/jvm/java-1.8-openjdk/lib/tools.jar: failed to open: unable to read the file: stream error: stream ID 9; PROTOCOL_ERROR; received from peer
     ```
 
-Trivy calls Maven API for better detection of JAR files, but many requests may exceed rate limiting.
-This can easily happen if you are running more than one instance of Trivy which is concurrently scanning multiple images.
-Once this starts happening Trivy's vulnerability reporting on jar files may become inconsistent.
-There are two options to resolve this issue:
+Currently, we're investigating this issue. As a temporary mitigation, you may be able to avoid this issue by downloading the Java DB in advance.
 
-The first is to enable offline scanning using the `--offline-scan` option to stop Trivy from making API requests.
-This option affects only vulnerability scanning. The vulnerability database and builtin policies are downloaded as usual.
-If you want to skip them as well, you can try `--skip-update` and `--skip-policy-update`.
-**Note that a number of vulnerabilities might be fewer than without the `--offline-scan` option.**
-
-The second, more scalable, option is the place Trivy behind a rate-limiting forward-proxy to the Maven Central API.
-One way to achieve this is to use nginx. You can use the following nginx config to enable both rate-limiting and caching (the caching greatly reduces the number of calls to the Maven Central API, especially if you are scanning a lot of similar images):
-
-```nginx
-limit_req_zone global zone=maven:1m rate=10r/s;
-proxy_cache_path /tmp/cache keys_zone=mavencache:10m;
-
-server {
-  listen 80;
-  proxy_cache mavencache;
-
-  location / {
-    limit_req zone=maven burst=1000;
-    proxy_cache_valid any 1h;
-    proxy_pass https://search.maven.org:443;
-  }
-}
+```shell
+$ trivy image --download-java-db-only
+2023-02-01T16:57:04.322+0900    INFO    Downloading the Java DB...
+$ trivy image [YOUR_JAVA_IMAGE]
 ```
 
-This config file will allow a maximum of 10 requests per second to the Maven API, this number was determined experimentally so you might want to use something else if it doesn't fit your needs.
-
-Once nginx is up and running, you need to tell all your Trivy deployments to proxy their Maven API calls through nginx. You can do this by setting the `MAVEN_CENTRAL_URL` environment variable. For example, if your nginx proxy is running at `127.0.0.1`, you can set `MAVEN_CENTRAL_URL=http://127.0.0.1/solrsearch/select`.
-
-
 ### Running in parallel takes same time as series run
 When running trivy on multiple images simultaneously, it will take same time as running trivy in series.
 This is because of a limitation of boltdb.
@@ -91,23 +65,6 @@ Reference : [boltdb: Opening a database][boltdb].
 
 [boltdb]: https://github.com/boltdb/bolt#opening-a-database
 
-### Error downloading vulnerability DB
-
-!!! error
-    FATAL failed to download vulnerability DB
-
-If trivy is running behind corporate firewall, you have to add the following urls to your allowlist.
-
-- ghcr.io
-- pkg-containers.githubusercontent.com
-
-### Old DB schema
-
-!!! error
-    --skip-update cannot be specified with the old DB schema.
-
-Trivy v0.23.0 or later requires Trivy DB v2. Please update your local database or follow [the instruction of air-gapped environment][air-gapped].
-
 ### Multiple Trivy servers
 
 !!! error
@@ -150,6 +107,37 @@ Try:
 $ TMPDIR=/my/custom/path trivy image ...
 ```
 
+## DB
+### Old DB schema
+
+!!! error
+    --skip-update cannot be specified with the old DB schema.
+
+Trivy v0.23.0 or later requires Trivy DB v2. Please update your local database or follow [the instruction of air-gapped environment][air-gapped].
+
+### Error downloading vulnerability DB
+
+!!! error
+    FATAL failed to download vulnerability DB
+
+If trivy is running behind corporate firewall, you have to add the following urls to your allowlist.
+
+- ghcr.io
+- pkg-containers.githubusercontent.com
+
+### Denied
+
+!!! error
+    GET https://ghcr.io/token?scope=repository%3Aaquasecurity%2Ftrivy-db%3Apull&service=ghcr.io: DENIED: denied
+
+Your local GHCR (GitHub Container Registry) token might be expired.
+Please remove the token and try downloading the DB again.
+
+```shell
+docker logout ghcr.io
+```
+
+
 ## Homebrew
 ### Scope error
 !!! error

docs/docs/sbom/cyclonedx.md

@@ -1,6 +1,4 @@
-# CycloneDX
-
-## Generating
+# CycloneDX generation
 Trivy can generate SBOM in the [CycloneDX][cyclonedx] format.
 Note that XML format is not supported at the moment.
 
@@ -15,7 +13,7 @@ By default, `--format cyclonedx` represents SBOM and doesn't include vulnerabili
 
 ```
 $ trivy image --format cyclonedx --output result.json alpine:3.15
-2022-07-19T07:47:27.624Z        INFO    "--format cyclonedx" disables security checks. Specify "--security-checks vuln" explicitly if you want to include vulnerabilities in the CycloneDX report.
+2022-07-19T07:47:27.624Z        INFO    "--format cyclonedx" disables security scanning. Specify "--scanners vuln" explicitly if you want to include vulnerabilities in the CycloneDX report.
 ```
 
 <details>
@@ -239,40 +237,12 @@ $ cat result.json | jq .
 
 </details>
 
-If you want to include vulnerabilities, you can enable vulnerability scanning via `--security-checks vuln`.
+If you want to include vulnerabilities, you can enable vulnerability scanning via `--scanners vuln`.
 
 ```
-$ trivy image --security-checks vuln --format cyclonedx --output result.json alpine:3.15
+$ trivy image --scanners vuln --format cyclonedx --output result.json alpine:3.15
 ```
 
-## Scanning
-Trivy can take CycloneDX as an input and scan for vulnerabilities.
-To scan SBOM, you can use the `sbom` subcommand and pass the path to your CycloneDX report. 
-
-```bash
-$ trivy sbom /path/to/cyclonedx.json
-
-cyclonedx.json (alpine 3.7.1)
-=========================
-Total: 3 (CRITICAL: 3)
-
-┌─────────────┬────────────────┬──────────┬───────────────────┬───────────────┬──────────────────────────────────────────────────────────────┐
-│   Library   │ Vulnerability  │ Severity │ Installed Version │ Fixed Version │                            Title                             │
-├─────────────┼────────────────┼──────────┼───────────────────┼───────────────┼──────────────────────────────────────────────────────────────┤
-│ curl        │ CVE-2018-14618 │ CRITICAL │ 7.61.0-r0         │ 7.61.1-r0     │ curl: NTLM password overflow via integer overflow            │
-│             │                │          │                   │               │ https://avd.aquasec.com/nvd/cve-2018-14618                   │
-├─────────────┼────────────────┼──────────┼───────────────────┼───────────────┼──────────────────────────────────────────────────────────────┤
-│ libbz2      │ CVE-2019-12900 │ CRITICAL │ 1.0.6-r6          │ 1.0.6-r7      │ bzip2: out-of-bounds write in function BZ2_decompress        │
-│             │                │          │                   │               │ https://avd.aquasec.com/nvd/cve-2019-12900                   │
-├─────────────┼────────────────┼──────────┼───────────────────┼───────────────┼──────────────────────────────────────────────────────────────┤
-│ sqlite-libs │ CVE-2019-8457  │ CRITICAL │ 3.21.0-r1         │ 3.25.3-r1     │ sqlite: heap out-of-bound read in function rtreenode()       │
-│             │                │          │                   │               │ https://avd.aquasec.com/nvd/cve-2019-8457                    │
-└─────────────┴────────────────┴──────────┴───────────────────┴───────────────┴──────────────────────────────────────────────────────────────┘
-```
-
-!!! note
-    If you want to generate a CycloneDX report from a CycloneDX input, please be aware that the output stores references to your original CycloneDX report and contains only detected vulnerabilities, not components.
-    The report is called [BOV][bov].
 
 [cyclonedx]: https://cyclonedx.org/
 [sbom]: https://cyclonedx.org/capabilities/sbom/

docs/docs/sbom/index.md

@@ -1,12 +1,12 @@
-# SBOM
+# SBOM generation
 
-## Generating
 Trivy can generate the following SBOM formats.
 
 - [CycloneDX][cyclonedx]
 - [SPDX][spdx]
 
-To generate SBOM, you can use the `--format` option for each subcommand such as `image` and `fs`.
+## CLI commands
+To generate SBOM, you can use the `--format` option for each subcommand such as `image`, `fs` and `vm`.
 
 ```
 $ trivy image --format spdx-json --output result.json alpine:3.15
@@ -177,56 +177,27 @@ $ trivy fs --format cyclonedx --output result.json /app/myproject
 
 </details>
 
-## Scanning
-Trivy also can take the following SBOM formats as an input and scan for vulnerabilities.
+## Supported packages
+Trivy supports the following packages.
 
-- CycloneDX
-- SPDX
-- SPDX JSON
-- CycloneDX-type attestation
+- [OS packages][os_packages]
+- [Language-specific packages][language_packages]
 
-To scan SBOM, you can use the `sbom` subcommand and pass the path to the SBOM.
-
-```bash
-$ trivy sbom /path/to/cyclonedx.json
-```
-
-See [here][cyclonedx] for the detail.
+In addition to the above packages, Trivy also supports the following packages for generating SBOM.
 
 !!! note
-    CycloneDX XML is not supported at the moment.
+    These packages are not supported for vulnerability scanning.
 
-```bash
-$ trivy sbom /path/to/spdx.json
-```
+| Language | File              | Dependency location[^1] |
+|----------|-------------------|:-----------------------:|
+| Python   | conda package[^2] |            -            |
+| Swift    | Podfile.lock      |            -            |
 
-See [here][spdx] for the detail.
-
-
-You can also scan an SBOM attestation.
-In the following example, [Cosign][Cosign] can get an attestation and trivy scan it. You must create CycloneDX-type attestation before trying the example. To learn more about how to create an CycloneDX-Type attestation and attach it to an image, see the [SBOM attestation page][sbom_attestation].
-```bash
-$ cosign verify-attestation --key /path/to/cosign.pub --type cyclonedx <IMAGE> > sbom.cdx.intoto.jsonl
-$ trivy sbom ./sbom.cdx.intoto.jsonl
-
-sbom.cdx.intoto.jsonl (alpine 3.7.3)
-=========================
-Total: 2 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 0, CRITICAL: 2)
-
-┌────────────┬────────────────┬──────────┬───────────────────┬───────────────┬──────────────────────────────────────────────────────────┐
-│  Library   │ Vulnerability  │ Severity │ Installed Version │ Fixed Version │                          Title                           │
-├────────────┼────────────────┼──────────┼───────────────────┼───────────────┼──────────────────────────────────────────────────────────┤
-│ musl       │ CVE-2019-14697 │ CRITICAL │ 1.1.18-r3         │ 1.1.18-r4     │ musl libc through 1.1.23 has an x87 floating-point stack │
-│            │                │          │                   │               │ adjustment im ......                                     │
-│            │                │          │                   │               │ https://avd.aquasec.com/nvd/cve-2019-14697               │
-├────────────┤                │          │                   │               │                                                          │
-│ musl-utils │                │          │                   │               │                                                          │
-│            │                │          │                   │               │                                                          │
-│            │                │          │                   │               │                                                          │
-└────────────┴────────────────┴──────────┴───────────────────┴───────────────┴──────────────────────────────────────────────────────────┘
-```
+[^1]: Use `startline == 1 and endline == 1` for unsupported file types
+[^2]: `envs/*/conda-meta/*.json`
 
 [cyclonedx]: cyclonedx.md
 [spdx]: spdx.md
-[Cosign]: https://github.com/sigstore/cosign
-[sbom_attestation]: ../attestation/sbom.md#sign-with-a-local-key-pair
+
+[os_packages]: ../vulnerability/detection/os.md
+[language_packages]: ../vulnerability/detection/language.md

docs/docs/sbom/spdx.md

@@ -1,6 +1,5 @@
-# SPDX
+# SPDX generation
 
-## Generating
 Trivy can generate SBOM in the [SPDX][spdx] format.
 
 You can use the regular subcommands (like `image`, `fs` and `rootfs`) and specify `spdx` with the `--format` option.
@@ -20,7 +19,7 @@ SPDXID: SPDXRef-DOCUMENT
 DocumentName: alpine:3.15
 DocumentNamespace: http://aquasecurity.github.io/trivy/container_image/alpine:3.15-bebf6b19-a94c-4e2c-af44-065f63923f48
 Creator: Organization: aquasecurity
-Creator: Tool: trivy
+Creator: Tool: trivy-0.38.1
 Created: 2022-04-28T07:32:57.142806Z
 
 ##### Package: zlib
@@ -168,7 +167,7 @@ $ cat result.spdx.json | jq .
 	"creationInfo": {
 		"created": "2022-04-28T08:16:55.328255Z",
 		"creators": [
-			"Tool: trivy",
+			"Tool: trivy-0.38.1",
 			"Organization: aquasecurity"
 		]
 	},
@@ -295,50 +294,5 @@ $ cat result.spdx.json | jq .
 
 </details>
 
-## Scanning
-Trivy can take the SPDX SBOM as an input and scan for vulnerabilities.
-To scan SBOM, you can use the `sbom` subcommand and pass the path to your SPDX report.
-The input format is automatically detected.
-
-The following formats are supported:
-
-- Tag-value (`--format spdx`)
-- JSON (`--format spdx-json`)
-
-```bash
-$ trivy image --format spdx-json --output spdx.json alpine:3.16.0
-$ trivy sbom spdx.json
-2022-09-15T21:32:27.168+0300    INFO    Vulnerability scanning is enabled
-2022-09-15T21:32:27.169+0300    INFO    Detected SBOM format: spdx-json
-2022-09-15T21:32:27.210+0300    INFO    Detected OS: alpine
-2022-09-15T21:32:27.210+0300    INFO    Detecting Alpine vulnerabilities...
-2022-09-15T21:32:27.211+0300    INFO    Number of language-specific files: 0
-
-spdx.json (alpine 3.16.0)
-=========================
-Total: 5 (UNKNOWN: 0, LOW: 0, MEDIUM: 2, HIGH: 2, CRITICAL: 1)
-
-┌──────────────┬────────────────┬──────────┬───────────────────┬───────────────┬────────────────────────────────────────────────────────────┐
-│   Library    │ Vulnerability  │ Severity │ Installed Version │ Fixed Version │                           Title                            │
-├──────────────┼────────────────┼──────────┼───────────────────┼───────────────┼────────────────────────────────────────────────────────────┤
-│ busybox      │ CVE-2022-30065 │ HIGH     │ 1.35.0-r13        │ 1.35.0-r15    │ busybox: A use-after-free in Busybox's awk applet leads to │
-│              │                │          │                   │               │ denial of service...                                       │
-│              │                │          │                   │               │ https://avd.aquasec.com/nvd/cve-2022-30065                 │
-├──────────────┼────────────────┼──────────┼───────────────────┼───────────────┼────────────────────────────────────────────────────────────┤
-│ libcrypto1.1 │ CVE-2022-2097  │ MEDIUM   │ 1.1.1o-r0         │ 1.1.1q-r0     │ openssl: AES OCB fails to encrypt some bytes               │
-│              │                │          │                   │               │ https://avd.aquasec.com/nvd/cve-2022-2097                  │
-├──────────────┤                │          │                   │               │                                                            │
-│ libssl1.1    │                │          │                   │               │                                                            │
-│              │                │          │                   │               │                                                            │
-├──────────────┼────────────────┼──────────┼───────────────────┼───────────────┼────────────────────────────────────────────────────────────┤
-│ ssl_client   │ CVE-2022-30065 │ HIGH     │ 1.35.0-r13        │ 1.35.0-r15    │ busybox: A use-after-free in Busybox's awk applet leads to │
-│              │                │          │                   │               │ denial of service...                                       │
-│              │                │          │                   │               │ https://avd.aquasec.com/nvd/cve-2022-30065                 │
-├──────────────┼────────────────┼──────────┼───────────────────┼───────────────┼────────────────────────────────────────────────────────────┤
-│ zlib         │ CVE-2022-37434 │ CRITICAL │ 1.2.12-r1         │ 1.2.12-r2     │ zlib: a heap-based buffer over-read or buffer overflow in  │
-│              │                │          │                   │               │ inflate in inflate.c...                                    │
-│              │                │          │                   │               │ https://avd.aquasec.com/nvd/cve-2022-37434                 │
-└──────────────┴────────────────┴──────────┴───────────────────┴───────────────┴────────────────────────────────────────────────────────────┘
-```
 
 [spdx]: https://spdx.dev/wp-content/uploads/sites/41/2020/08/SPDX-specification-2-2.pdf

docs/docs/sbom/supported.md

@@ -1,14 +0,0 @@
-## Packages that support vulnerability scanning
-- [OS packages][os_packages]
-- [Language-specific packages][language_packages]
-
-## Other language-specific packages
-
-| Language | File         | Dependency location[^1] |
-|----------|--------------|:-----------------------:|
-| Swift    | Podfile.lock |            -            |
-
-[^1]: Use `startline == 1 and endline == 1` for unsupported file types
-
-[os_packages]: ../vulnerability/detection/os.md
-[language_packages]: ../vulnerability/detection/language.md

docs/docs/secret/examples.md

@@ -15,7 +15,7 @@ $ trivy image --skip-dirs /var/lib --skip-dirs /var/log YOUR_IMAGE
 $ trivy fs --skip-dirs ./my-test-dir --skip-dirs ./my-testing-cert/ /path/to/your_project
 ```
 
-`--skip-fles` also works similarly.
+`--skip-files` also works similarly.
 
 ## Filter by severity
 
@@ -48,10 +48,10 @@ aws-account-id
 ```
 
 ## Disable secret scanning
-If you need vulnerability scanning only, you can disable secret scanning via the `--security-checks` flag.
+If you need vulnerability scanning only, you can disable secret scanning via the `--scanners` flag.
 
 ``` shell
-$ trivy image --security-checks vuln alpine:3.15
+$ trivy image --scanners vuln alpine:3.15
 ```
 
 ## With configuration file
@@ -107,4 +107,4 @@ disable-allow-rules:
 $ trivy fs --secret-config ./secret-config/trivy.yaml /path/to/your_project
 ```
 
-[quick-start]: ./scanning.md#quick-start
+[quick-start]: ./scanning.md#quick-start

docs/docs/secret/scanning.md

@@ -106,10 +106,10 @@ All rules are disabled except for the ones you specify, so it runs very fast.
 On the other hand, you should use `disable-rules` if you just want to disable some built-in rules.
 See the [enable-rules][enable-rules] and [disable-rules][disable-rules] sections for the detail.
 
-If you don't need secret scanning, you can disable it via the `--security-checks` flag.
+If you don't need secret scanning, you can disable it via the `--scanners` flag.
 
 ```shell
-$ trivy image --security-checks vuln alpine:3.15
+$ trivy image --scanners vuln alpine:3.15
 ```
 
 

docs/docs/target/aws.md

@@ -0,0 +1,107 @@
+# Amazon Web Services
+
+!!! warning "EXPERIMENTAL"
+    This feature might change without preserving backwards compatibility.
+
+The Trivy AWS CLI allows you to scan your AWS account for misconfigurations. 
+You can either run the CLI locally or integrate it into your CI/CD pipeline. 
+
+Whilst you can already scan the infrastructure-as-code that defines your AWS resources with `trivy config`, you can now scan your live AWS account(s) directly too.
+
+The included checks cover all of the aspects of the [AWS CIS 1.2](https://docs.aws.amazon.com/securityhub/latest/userguide/securityhub-standards-cis.html) automated benchmarks.
+
+Trivy uses the same [authentication methods](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html) as the AWS CLI to configure and authenticate your access to the AWS platform.
+
+You will need permissions configured to read all AWS resources - we recommend using a group/role with the `ReadOnlyAccess` policy attached.
+
+Once you've scanned your account, you can run additional commands to filter the results without having to run the entire scan again - infrastructure information is cached locally per AWS account/region.
+
+Trivy currently supports the following scanning for AWS accounts.
+
+- Misconfigurations
+
+## CLI Commands
+
+Scan a full AWS account (all supported services):
+
+```shell
+trivy aws --region us-east-1
+```
+
+You can allow Trivy to determine the AWS region etc. by using the standard AWS configuration files and environment variables. The `--region` flag overrides these.
+
+![AWS Summary Report](../../imgs/trivy-aws.png)
+
+The summary view is the default when scanning multiple services.
+
+Scan a specific service:
+
+```shell
+trivy aws --service s3
+```
+
+Scan multiple services:
+
+```shell
+# --service s3,ec2 works too
+trivy aws --service s3 --service ec2
+```
+
+Show results for a specific AWS resource:
+
+```shell
+trivy aws --service s3 --arn arn:aws:s3:::example-bucket
+```
+
+All ARNs with detected issues will be displayed when showing results for their associated service.
+
+## Compliance
+This section describes AWS 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                                                                                            |
+|------------------------------------|------------------|------------------------------------------------------------------------------------------------------|
+| AWS CIS Foundations Benchmark v1.2 | `aws-cis-1.2`    | [link](https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf)            |
+| AWS CIS Foundations Benchmark v1.4 | `aws-cis-1.4`    | [link](https://docs.aws.amazon.com/securityhub/latest/userguide/securityhub-cis-controls-1.4.0.html) |
+
+### Examples
+
+Scan a cloud account and generate a compliance summary report:
+
+```
+$ trivy aws --compliance=<compliance_id> --report=summary
+```
+
+***Note*** : The `Issues` column represent the total number of failed checks for this control.
+
+
+Get all of the detailed output for checks:
+
+```
+$ trivy aws --compliance=<compliance_id> --report all
+```
+
+Report result in JSON format:
+
+```
+$ trivy aws --compliance=<compliance_id> --report all --format json
+```
+
+## Cached Results
+
+By default, Trivy will cache a representation of each AWS service for 24 hours.
+This means you can filter and view results for a service without having to wait for the entire scan to run again.
+If you want to force the cache to be refreshed with the latest data, you can use `--update-cache`.
+Or if you'd like to use cached data for a different timeframe, you can specify `--max-cache-age` (e.g. `--max-cache-age 2h`.).
+Regardless of whether the cache is used or not, rules will be evaluated again with each run of `trivy aws`.
+
+## Custom Policies
+
+You can write custom policies for Trivy to evaluate against your AWS account.
+These policies are written in [Rego](https://www.openpolicyagent.org/docs/latest/policy-language/), the same language used by [Open Policy Agent](https://www.openpolicyagent.org/).
+See the [Custom Policies](../misconfiguration/custom/index.md) page for more information.
+

docs/docs/target/container_image.md

@@ -0,0 +1,484 @@
+# Container Image
+
+Trivy supports two targets for container images.
+
+- Files inside container images
+- Container image metadata
+
+## Files inside container images
+Container images consist of files.
+For instance, new files will be installed if you install a package.
+
+Trivy scans the files inside container images for
+
+- Vulnerabilities
+- Misconfigurations
+- Secrets
+- Licenses
+
+By default, vulnerability and secret scanning are enabled, and you can configure that with `--scanners`.
+
+### Vulnerabilities
+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](../vulnerability/scanning.md) for the detail.
+
+```
+$ trivy image [YOUR_IMAGE_NAME]
+```
+
+For example:
+
+```
+$ trivy image python:3.4-alpine
+```
+
+<details>
+<summary>Result</summary>
+
+```
+2019-05-16T01:20:43.180+0900    INFO    Updating vulnerability database...
+2019-05-16T01:20:53.029+0900    INFO    Detecting Alpine vulnerabilities...
+
+python:3.4-alpine3.9 (alpine 3.9.2)
+===================================
+Total: 1 (UNKNOWN: 0, LOW: 0, MEDIUM: 1, HIGH: 0, CRITICAL: 0)
+
++---------+------------------+----------+-------------------+---------------+--------------------------------+
+| LIBRARY | VULNERABILITY ID | SEVERITY | INSTALLED VERSION | FIXED VERSION |             TITLE              |
++---------+------------------+----------+-------------------+---------------+--------------------------------+
+| openssl | CVE-2019-1543    | MEDIUM   | 1.1.1a-r1         | 1.1.1b-r1     | openssl: ChaCha20-Poly1305     |
+|         |                  |          |                   |               | with long nonces               |
++---------+------------------+----------+-------------------+---------------+--------------------------------+
+```
+
+</details>
+
+To enable only vulnerability scanning, you can specify `--scanners vuln`.
+
+```shell
+$ trivy image --scanners vuln [YOUR_IMAGE_NAME]
+```
+
+### Misconfigurations
+It is supported, but it is not useful in most cases.
+As mentioned [here](../misconfiguration/scanning.md), Trivy mainly supports Infrastructure as Code (IaC) files for misconfigurations.
+If your container image includes IaC files such as Kubernetes YAML files or Terraform files, you should enable this feature with `--scanners config`.
+
+```
+$ trivy image --scanners config [YOUR_IMAGE_NAME]
+```
+
+### Secrets
+It is enabled by default.
+See [here](../secret/scanning.md) for the detail.
+
+```shell
+$ trivy image [YOUR_IMAGE_NAME]
+```
+
+### Licenses
+It is disabled by default.
+See [here](../licenses/scanning.md) for the detail.
+
+```shell
+$ trivy image --scanners license [YOUR_IMAGE_NAME]
+```
+
+## Container image metadata
+Container images have [configuration](https://github.com/opencontainers/image-spec/blob/2fb996805b3734779bf9a3a84dc9a9691ad7efdd/config.md).
+`docker inspect` and `docker history` show the information according to the configuration.
+
+Trivy scans the configuration of container images for
+
+- Misconfigurations
+- Secrets
+
+They are disabled by default.
+You can enable them with `--image-config-scanners`.
+ 
+!!! tips
+    The configuration can be exported as the JSON file by `docker save`.
+
+### Misconfigurations
+Trivy detects misconfigurations on the configuration of container images.
+The image config is converted into Dockerfile and Trivy handles it as Dockerfile.
+See [here](../misconfiguration/scanning.md) for the detail of Dockerfile scanning.
+
+It is disabled by default.
+You can enable it with `--image-config-scanners config`.
+
+```
+$ trivy image --image-config-scanners config [YOUR_IMAGE_NAME]
+```
+
+If you just want to scan the image config, you can disable scanners with `--scanners none`.
+For example:
+
+```
+$ trivy image --scanners none --image-config-scanners config alpine:3.17.0
+```
+
+<details>
+<summary>Result</summary>
+
+```
+alpine:3.17 (dockerfile)
+========================
+Tests: 24 (SUCCESSES: 21, FAILURES: 3, EXCEPTIONS: 0)
+Failures: 3 (UNKNOWN: 0, LOW: 2, MEDIUM: 0, HIGH: 1, CRITICAL: 0)
+
+HIGH: Specify at least 1 USER command in Dockerfile with non-root user as argument
+════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════
+Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.
+
+See https://avd.aquasec.com/misconfig/ds002
+────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
+
+
+LOW: Consider using 'COPY file:e4d600fc4c9c293efe360be7b30ee96579925d1b4634c94332e2ec73f7d8eca1 in /' command instead of 'ADD file:e4d600fc4c9c293efe360be7b30ee96579925d1b4634c94332e2ec73f7d8eca1 in /'
+════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════
+You should use COPY instead of ADD unless you want to extract a tar file. Note that an ADD command will extract a tar file, which adds the risk of Zip-based vulnerabilities. Accordingly, it is advised to use a COPY command, which does not extract tar files.
+
+See https://avd.aquasec.com/misconfig/ds005
+────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
+ alpine:3.17:1
+────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
+   1 [ ADD file:e4d600fc4c9c293efe360be7b30ee96579925d1b4634c94332e2ec73f7d8eca1 in /
+────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
+
+
+LOW: Add HEALTHCHECK instruction in your Dockerfile
+════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════
+You shoud add HEALTHCHECK instruction in your docker container images to perform the health check on running containers.
+
+See https://avd.aquasec.com/misconfig/ds026
+────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
+```
+</details>
+
+!!! tip
+    You can see how each layer is created with `docker history`.
+
+### Secrets
+Trivy detects secrets on the configuration of container images.
+The image config is converted into JSON and Trivy scans the file for secrets.
+It is especially useful for environment variables that are likely to have credentials by accident.
+See [here](../secret/scanning.md) for the detail.
+
+```shell
+$ trivy image --image-config-scanners secret [YOUR_IMAGE_NAME]
+```
+
+If you just want to scan the image config, you can disable scanners with `--scanners none`.
+For example:
+
+```shell
+$ trivy image --scanners none --image-config-scanners secret vuln-image
+```
+
+<details>
+<summary>Result</summary>
+
+```
+vuln-image (alpine 3.17.1)
+==========================
+Total: 0 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 0, CRITICAL: 0)
+
+
+vuln-image (secrets)
+====================
+Total: 2 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 0, CRITICAL: 2)
+
+CRITICAL: GitHub (github-pat)
+════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════
+GitHub Personal Access Token
+────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
+ test:16
+────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
+  14     {
+  15     "created": "2023-01-09T17:05:20Z",
+  16 [   "created_by": "ENV secret=****************************************",
+  17     "comment": "buildkit.dockerfile.v0",
+────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
+
+
+CRITICAL: GitHub (github-pat)
+════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════
+GitHub Personal Access Token
+────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
+ test:34
+────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
+  32     "Env": [
+  33     "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
+  34 [   "secret=****************************************"
+  35     ]
+────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
+
+```
+
+</details>
+
+!!! tip
+    You can see environment variables with `docker inspect`.
+
+## Supported
+### Docker Engine
+Trivy tries to looks for the specified image in your local Docker Engine.
+It will be skipped if Docker Engine is not running locally.
+
+If your docker socket is not the default path, you can override it via `DOCKER_HOST`.
+
+### containerd
+
+!!! warning "EXPERIMENTAL"
+    This feature might change without preserving backwards compatibility.
+    
+Trivy tries to looks for the specified image in your local [containerd](https://containerd.io/).
+It will be skipped if containerd is not running locally.
+
+Specify your image name in containerd running locally.
+
+```bash
+$ nerdctl images
+REPOSITORY        TAG       IMAGE ID        CREATED         PLATFORM       SIZE         BLOB SIZE
+aquasec/nginx    latest    2bcabc23b454    3 hours ago     linux/amd64    149.1 MiB    54.1 MiB
+$ trivy image aquasec/nginx
+```
+
+If your containerd socket is not the default path (`//run/containerd/containerd.sock`), you can override it via `CONTAINERD_ADDRESS`.
+
+```bash
+$ export CONTAINERD_ADDRESS=/run/k3s/containerd/containerd.sock
+$ trivy image aquasec/nginx
+```
+
+If your scan targets are images in a namespace other than containerd's default namespace (`default`), you can override it via `CONTAINERD_NAMESPACE`.
+
+```bash
+$ export CONTAINERD_NAMESPACE=k8s.io
+$ trivy image aquasec/nginx
+```
+
+### Podman
+
+!!! warning "EXPERIMENTAL"
+    This feature might change without preserving backwards compatibility.
+
+Scan your image in Podman (>=2.0) running locally. The remote Podman is not supported.
+Before performing Trivy commands, you must enable the podman.sock systemd service on your machine.
+For more details, see [here](https://github.com/containers/podman/blob/master/docs/tutorials/remote_client.md#enable-the-podman-service-on-the-server-machine).
+
+
+```bash
+$ systemctl --user enable --now podman.socket
+```
+
+Then, you can scan your image in Podman.
+
+```bash
+$ cat Dockerfile
+FROM alpine:3.12
+RUN apk add --no-cache bash
+$ podman build -t test .
+$ podman images
+REPOSITORY                TAG     IMAGE ID      CREATED      SIZE
+localhost/test            latest  efc372d4e0de  About a minute ago  7.94 MB
+$ trivy image test
+```
+
+### Container Registry
+Trivy supports registries that comply with the following specifications.
+
+- [Docker Registry HTTP API V2](https://docs.docker.com/registry/spec/api/)
+- [OCI Distribution Specification](https://github.com/opencontainers/distribution-spec)
+
+You can configure credentials with `docker login`.
+See [here](../advanced/private-registries/index.md) for the detail.
+
+### Tar Files
+Trivy supports image tar files generated by the following tools.
+
+- [Docker Image Specification](https://github.com/moby/moby/tree/master/image/spec)
+    - [Moby Project](https://github.com/moby/moby/)
+    - [Buildah](https://github.com/containers/buildah)
+    - [Podman](https://github.com/containers/podman)
+    - [img](https://github.com/genuinetools/img)
+- [Kaniko](https://github.com/GoogleContainerTools/kaniko)
+
+```
+$ docker pull ruby:3.1-alpine3.15
+$ docker save ruby:3.1-alpine3.15 -o ruby-3.1.tar
+$ trivy image --input ruby-3.1.tar
+```
+
+<details>
+<summary>Result</summary>
+
+```
+2022-02-03T10:08:19.127Z        INFO    Detected OS: alpine
+2022-02-03T10:08:19.127Z        WARN    This OS version is not on the EOL list: alpine 3.15
+2022-02-03T10:08:19.127Z        INFO    Detecting Alpine vulnerabilities...
+2022-02-03T10:08:19.127Z        INFO    Number of language-specific files: 2
+2022-02-03T10:08:19.127Z        INFO    Detecting gemspec vulnerabilities...
+2022-02-03T10:08:19.128Z        INFO    Detecting node-pkg vulnerabilities...
+2022-02-03T10:08:19.128Z        WARN    This OS version is no longer supported by the distribution: alpine 3.15.0
+2022-02-03T10:08:19.128Z        WARN    The vulnerability detection may be insufficient because security updates are not provided
+
+ruby-3.1.tar (alpine 3.15.0)
+============================
+Total: 3 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 3, CRITICAL: 0)
+
++----------+------------------+----------+-------------------+---------------+---------------------------------------+
+| LIBRARY  | VULNERABILITY ID | SEVERITY | INSTALLED VERSION | FIXED VERSION |                 TITLE                 |
++----------+------------------+----------+-------------------+---------------+---------------------------------------+
+| gmp      | CVE-2021-43618   | HIGH     | 6.2.1-r0          | 6.2.1-r1      | gmp: Integer overflow and resultant   |
+|          |                  |          |                   |               | buffer overflow via crafted input     |
+|          |                  |          |                   |               | -->avd.aquasec.com/nvd/cve-2021-43618 |
++----------+                  +          +                   +               +                                       +
+| gmp-dev  |                  |          |                   |               |                                       |
+|          |                  |          |                   |               |                                       |
+|          |                  |          |                   |               |                                       |
++----------+                  +          +                   +               +                                       +
+| libgmpxx |                  |          |                   |               |                                       |
+|          |                  |          |                   |               |                                       |
+|          |                  |          |                   |               |                                       |
++----------+------------------+----------+-------------------+---------------+---------------------------------------+
+
+Node.js (node-pkg)
+==================
+Total: 0 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 0, CRITICAL: 0)
+
+
+Ruby (gemspec)
+==============
+Total: 0 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 0, CRITICAL: 0)
+```
+
+</details>
+
+### OCI Layout
+Trivy supports image directories compliant with [Open Container Image Layout Specification](https://github.com/opencontainers/image-spec/blob/master/spec.md).
+
+Buildah:
+
+```
+$ buildah push docker.io/library/alpine:3.11 oci:/path/to/alpine
+$ trivy image --input /path/to/alpine
+```
+
+Skopeo:
+
+```
+$ skopeo copy docker-daemon:alpine:3.11 oci:/path/to/alpine
+$ trivy image --input /path/to/alpine
+```
+
+## SBOM
+Trivy supports the generation of Software Bill of Materials (SBOM) for container images and the search for SBOMs during vulnerability scanning.
+
+### Generation
+Trivy can generate SBOM for container images.
+See [here](../sbom/index.md) for the detail.
+
+### Discovery
+Trivy can search for Software Bill of Materials (SBOMs) that reference container images.
+If an SBOM is found, the vulnerability scan is performed using the SBOM instead of the container image.
+By using the SBOM, you can perform a vulnerability scan more quickly, as it allows you to skip pulling the container image and analyzing its layers.
+
+To enable this functionality, you need to specify the `--sbom-sources` flag.
+The following two sources are supported:
+
+- OCI Registry (`oci`)
+- Rekor (`rekor`)
+
+Example:
+
+```bash
+$ trivy image --sbom-sources oci ghcr.io/knqyf263/oci-referrers
+2023-03-05T17:36:55.278+0200    INFO    Vulnerability scanning is enabled
+2023-03-05T17:36:58.103+0200    INFO    Detected SBOM format: cyclonedx-json
+2023-03-05T17:36:58.129+0200    INFO    Found SBOM (cyclonedx) in the OCI referrers
+...
+
+ghcr.io/knqyf263/oci-referrers (alpine 3.16.2)
+==============================================
+Total: 17 (UNKNOWN: 0, LOW: 0, MEDIUM: 5, HIGH: 9, CRITICAL: 3)
+```
+
+The OCI Registry utilizes the [Referrers API](https://github.com/opencontainers/distribution-spec/blob/main/spec.md#listing-referrers).
+For more information about Rekor, please refer to [its documentation](../attestation/rekor.md).
+
+## Compliance
+
+!!! warning "EXPERIMENTAL"
+    This feature might change without preserving backwards compatibility.
+
+This section describes container image 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                             | Version | Name for command | More info                                                                                   |
+|----------------------------------------|---------|------------------|---------------------------------------------------------------------------------------------|
+| CIS Docker Community Edition Benchmark | 1.1.0   | `docker-cis`     | [Link](https://www.aquasec.com/cloud-native-academy/docker-container/docker-cis-benchmark/) |
+
+### Examples
+
+Scan a container image configuration and generate a compliance summary report:
+
+```
+$ trivy image --compliance docker-cis [YOUR_IMAGE_NAME]
+```
+
+!!! note
+    The `Issues` column represent the total number of failed checks for this control.
+
+## Authentication
+Please reference [this page](../advanced/private-registries/index.md).
+
+## Options
+### Scan Image on a specific Architecture and OS
+By default, Trivy loads an image on a "linux/amd64" machine.
+To customise this, pass a `--platform` argument in the format OS/Architecture for the image:
+
+```
+$ trivy image --platform=os/architecture [YOUR_IMAGE_NAME]
+```
+
+For example:
+
+```
+$ trivy image --platform=linux/arm alpine:3.16.1
+```
+
+<details>
+<summary>Result</summary>
+
+```
+2022-10-25T21:00:50.972+0300    INFO    Vulnerability scanning is enabled
+2022-10-25T21:00:50.972+0300    INFO    Secret scanning is enabled
+2022-10-25T21:00:50.972+0300    INFO    If your scanning is slow, please try '--scanners vuln' to disable secret scanning
+2022-10-25T21:00:50.972+0300    INFO    Please see also https://aquasecurity.github.io/trivy/dev/docs/secret/scanning/#recommendation for faster secret detection
+2022-10-25T21:00:56.190+0300    INFO    Detected OS: alpine
+2022-10-25T21:00:56.190+0300    INFO    Detecting Alpine vulnerabilities...
+2022-10-25T21:00:56.191+0300    INFO    Number of language-specific files: 0
+
+alpine:3.16.1 (alpine 3.16.1)
+=============================
+Total: 1 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 0, CRITICAL: 1)
+
+┌─────────┬────────────────┬──────────┬───────────────────┬───────────────┬─────────────────────────────────────────────────────────────┐
+│ Library │ Vulnerability  │ Severity │ Installed Version │ Fixed Version │                            Title                            │
+├─────────┼────────────────┼──────────┼───────────────────┼───────────────┼─────────────────────────────────────────────────────────────┤
+│ zlib    │ CVE-2022-37434 │ CRITICAL │ 1.2.12-r1         │ 1.2.12-r2     │ zlib: heap-based buffer over-read and overflow in inflate() │
+│         │                │          │                   │               │ in inflate.c via a...                                       │
+│         │                │          │                   │               │ https://avd.aquasec.com/nvd/cve-2022-37434                  │
+└─────────┴────────────────┴──────────┴───────────────────┴───────────────┴─────────────────────────────────────────────────────────────┘
+```
+
+</details>
+

docs/docs/target/filesystem.md

@@ -0,0 +1,93 @@
+# Filesystem
+
+Scan your local projects for
+
+- Vulnerabilities
+- Misconfigurations
+- Secrets
+- Licenses
+ 
+By default, vulnerability and secret scanning are enabled, and you can configure that with `--scanners`.
+
+```bash
+$ trivy fs /path/to/project
+```
+
+It's also possible to scan a single file.
+
+```
+$ trivy fs ~/src/github.com/aquasecurity/trivy-ci-test/Pipfile.lock
+```
+
+## 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](../vulnerability/scanning.md) for the detail.
+
+```
+$ trivy fs ~/src/github.com/aquasecurity/trivy-ci-test
+```
+
+<details>
+<summary>Result</summary>
+
+```
+2020-06-01T17:06:58.652+0300    WARN    OS is not detected and vulnerabilities in OS packages are not detected.
+2020-06-01T17:06:58.652+0300    INFO    Detecting pipenv vulnerabilities...
+2020-06-01T17:06:58.691+0300    INFO    Detecting cargo vulnerabilities...
+
+Pipfile.lock
+============
+Total: 10 (UNKNOWN: 2, LOW: 0, MEDIUM: 6, HIGH: 2, CRITICAL: 0)
+
++---------------------+------------------+----------+-------------------+------------------------+------------------------------------+
+|       LIBRARY       | VULNERABILITY ID | SEVERITY | INSTALLED VERSION |     FIXED VERSION      |               TITLE                |
++---------------------+------------------+----------+-------------------+------------------------+------------------------------------+
+| django              | CVE-2020-7471    | HIGH     | 2.0.9             | 3.0.3, 2.2.10, 1.11.28 | django: potential                  |
+|                     |                  |          |                   |                        | SQL injection via                  |
+|                     |                  |          |                   |                        | StringAgg(delimiter)               |
++                     +------------------+----------+                   +------------------------+------------------------------------+
+|                     | CVE-2019-19844   | MEDIUM   |                   | 3.0.1, 2.2.9, 1.11.27  | Django: crafted email address      |
+|                     |                  |          |                   |                        | allows account takeover            |
++                     +------------------+          +                   +------------------------+------------------------------------+
+|                     | CVE-2019-3498    |          |                   | 2.1.5, 2.0.10, 1.11.18 | python-django: Content             |
+|                     |                  |          |                   |                        | spoofing via URL path in           |
+|                     |                  |          |                   |                        | default 404 page                   |
++                     +------------------+          +                   +------------------------+------------------------------------+
+|                     | CVE-2019-6975    |          |                   | 2.1.6, 2.0.11, 1.11.19 | python-django:                     |
+|                     |                  |          |                   |                        | memory exhaustion in               |
+|                     |                  |          |                   |                        | django.utils.numberformat.format() |
++---------------------+------------------+----------+-------------------+------------------------+------------------------------------+
+...
+```
+
+</details>
+
+### Misconfigurations
+It is disabled by default and can be enabled with `--scanners config`.
+See [here](../misconfiguration/scanning.md) for the detail.
+
+```shell
+$ trivy fs --scanners config /path/to/project
+```
+
+### Secrets
+It is enabled by default.
+See [here](../secret/scanning.md) for the detail.
+
+```shell
+$ trivy fs /path/to/project
+```
+
+### Licenses
+It is disabled by default.
+See [here](../licenses/scanning.md) for the detail.
+
+```shell
+$ trivy fs --scanners license /path/to/project
+```
+
+## SBOM generation
+Trivy can generate SBOM for local projects.
+See [here](../sbom/index.md) for the detail.

docs/docs/target/git-repository.md

@@ -1,6 +1,23 @@
 # Git Repository
 
-Scan your remote git repository
+Scan your remote git repositories for
+
+- Vulnerabilities
+- Misconfigurations
+- Secrets
+- Licenses
+ 
+By default, vulnerability and secret scanning are enabled, and you can configure that with `--scanners`.
+
+```bash
+$ trivy repo [YOUR_REPO_URL]
+```
+
+## 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](../vulnerability/scanning.md) for the detail.
 
 ```
 $ trivy repo https://github.com/knqyf263/trivy-ci-test
@@ -147,7 +164,36 @@ Total: 20 (UNKNOWN: 3, LOW: 0, MEDIUM: 7, HIGH: 5, CRITICAL: 5)
 
 </details>
 
-## Scanning a Branch
+### Misconfigurations
+It is disabled by default and can be enabled with `--scanners config`.
+See [here](../misconfiguration/scanning.md) for the detail.
+
+```shell
+$ trivy repo --scanners config [YOUR_REPO_URL]
+```
+
+### Secrets
+It is enabled by default.
+See [here](../secret/scanning.md) for the detail.
+
+```shell
+$ trivy repo [YOUR_REPO_URL]
+```
+
+### Licenses
+It is disabled by default.
+See [here](../licenses/scanning.md) for the detail.
+
+```shell
+$ trivy repo --scanners license [YOUR_REPO_URL]
+```
+
+## SBOM generation
+Trivy can generate SBOM for git repositories.
+See [here](../sbom/index.md) for the detail.
+
+## References
+### Scanning a Branch
 
 Pass a `--branch` argument with a valid branch name on the remote repository provided:
 
@@ -155,7 +201,7 @@ Pass a `--branch` argument with a valid branch name on the remote repository pro
 $ trivy repo --branch <branch-name> <repo-name>
 ```
 
-## Scanning upto a Commit
+### Scanning upto a Commit
 
 Pass a `--commit` argument with a valid commit hash on the remote repository provided:
 
@@ -163,7 +209,7 @@ Pass a `--commit` argument with a valid commit hash on the remote repository pro
 $ trivy repo --commit <commit-hash> <repo-name>
 ```
 
-## Scanning a Tag
+### Scanning a Tag
 
 Pass a `--tag` argument with a valid tag on the remote repository provided:
 
@@ -171,12 +217,13 @@ Pass a `--tag` argument with a valid tag on the remote repository provided:
 $ trivy repo --tag <tag-name> <repo-name>
 ```
 
-## Scanning Private Repositories
-
+### Scanning Private Repositories
 In order to scan private GitHub or GitLab repositories, the environment variable `GITHUB_TOKEN` or `GITLAB_TOKEN` must be set, respectively, with a valid token that has access to the private repository being scanned.
 
 The `GITHUB_TOKEN` environment variable will take precedence over `GITLAB_TOKEN`, so if a private GitLab repository will be scanned, then `GITHUB_TOKEN` must be unset.
 
+You can find how to generate your GitHub Token in the following [GitHub documentation.](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)
+
 For example:
 
 ```
@@ -187,65 +234,3 @@ $ # or
 $ export GITLAB_TOKEN="your_private_gitlab_token"
 $ trivy repo <your private GitLab repo URL>
 ```
-
-## Client/Server mode
-You must launch Trivy server in advance.
-
-```sh
-$ trivy server
-```
-
-Then, Trivy works as a client if you specify the `--server` option.
-
-```sh
-$ trivy repo https://github.com/knqyf263/trivy-ci-test --server http://localhost:4954
-```
-
-<details>
-<summary>Result</summary>
-
-```
-Cargo.lock (cargo)
-==================
-Total: 2 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 1, CRITICAL: 1)
-
-┌───────────┬─────────────────────┬──────────┬───────────────────┬───────────────┬─────────────────────────────────────────────────────────────┐
-│  Library  │    Vulnerability    │ Severity │ Installed Version │ Fixed Version │                            Title                            │
-├───────────┼─────────────────────┼──────────┼───────────────────┼───────────────┼─────────────────────────────────────────────────────────────┤
-│ openssl   │ CVE-2018-20997      │ CRITICAL │ 0.8.3             │ 0.10.9        │ Use after free in openssl                                   │
-│           │                     │          │                   │               │ https://avd.aquasec.com/nvd/cve-2018-20997                  │
-│           ├─────────────────────┼──────────┤                   ├───────────────┼─────────────────────────────────────────────────────────────┤
-│           │ CVE-2016-10931      │ HIGH     │                   │ 0.9.0         │ Improper Certificate Validation in openssl                  │
-│           │                     │          │                   │               │ https://avd.aquasec.com/nvd/cve-2016-10931                  │
-└───────────┴─────────────────────┴──────────┴───────────────────┴───────────────┴─────────────────────────────────────────────────────────────┘
-
-Pipfile.lock (pipenv)
-=====================
-Total: 5 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 3, CRITICAL: 2)
-
-┌─────────────────────┬────────────────┬──────────┬───────────────────┬────────────────────────┬──────────────────────────────────────────────────────────────┐
-│       Library       │ Vulnerability  │ Severity │ Installed Version │     Fixed Version      │                            Title                             │
-├─────────────────────┼────────────────┼──────────┼───────────────────┼────────────────────────┼──────────────────────────────────────────────────────────────┤
-│ py                  │ CVE-2020-29651 │ HIGH     │ 1.8.0             │ 1.10.0                 │ python-py: ReDoS in the py.path.svnwc component via          │
-│                     │                │          │                   │                        │ mailicious input to blame functionality...                   │
-│                     │                │          │                   │                        │ https://avd.aquasec.com/nvd/cve-2020-29651                   │
-│                     ├────────────────┤          │                   ├────────────────────────┼──────────────────────────────────────────────────────────────┤
-│                     │ CVE-2022-42969 │          │                   │                        │ The py library through 1.11.0 for Python allows remote       │
-│                     │                │          │                   │                        │ attackers to co...                                           │
-│                     │                │          │                   │                        │ https://avd.aquasec.com/nvd/cve-2022-42969                   │
-├─────────────────────┼────────────────┤          ├───────────────────┼────────────────────────┼──────────────────────────────────────────────────────────────┤
-│ pyjwt               │ CVE-2022-29217 │          │ 1.7.1             │ 2.4.0                  │ python-jwt: Key confusion through non-blocklisted public key │
-│                     │                │          │                   │                        │ formats                                                      │
-│                     │                │          │                   │                        │ https://avd.aquasec.com/nvd/cve-2022-29217                   │
-├─────────────────────┼────────────────┼──────────┼───────────────────┼────────────────────────┼──────────────────────────────────────────────────────────────┤
-│ pyyaml              │ CVE-2019-20477 │ CRITICAL │ 5.1               │ 5.2b1                  │ PyYAML: command execution through python/object/apply        │
-│                     │                │          │                   │                        │ constructor in FullLoader                                    │
-│                     │                │          │                   │                        │ https://avd.aquasec.com/nvd/cve-2019-20477                   │
-│                     ├────────────────┤          │                   ├────────────────────────┼──────────────────────────────────────────────────────────────┤
-│                     │ CVE-2020-1747  │          │                   │ 5.3.1                  │ PyYAML: arbitrary command execution through                  │
-│                     │                │          │                   │                        │ python/object/new when FullLoader is used                    │
-│                     │                │          │                   │                        │ https://avd.aquasec.com/nvd/cve-2020-1747                    │
-└─────────────────────┴────────────────┴──────────┴───────────────────┴────────────────────────┴──────────────────────────────────────────────────────────────┘
-
-```
-</details>

docs/docs/target/kubernetes.md

@@ -3,13 +3,21 @@
 !!! warning "EXPERIMENTAL"
     This feature might change without preserving backwards compatibility.
 
-The Trivy K8s CLI allows you to scan your Kubernetes cluster for Vulnerabilities, Secrets and Misconfigurations. 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.
+## CLI
+The Trivy K8s CLI allows you to scan your Kubernetes cluster for 
 
-If you are looking for continuous cluster audit scanning, have a look at the [Trivy K8s operator.](../operator/index.md)
+- 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.
+
+If you are looking for continuous cluster audit scanning, have a look at the Trivy K8s operator below.
 
 Trivy uses your local kubectl configuration to access the API server to list artifacts.
 
-## CLI Commands
+### Commands
 
 Scan a full cluster and generate a simple summary report:
 
@@ -17,7 +25,7 @@ Scan a full cluster and generate a simple summary report:
 $ trivy k8s --report=summary cluster
 ```
 
-![k8s Summary Report](../../../imgs/trivy-k8s.png)
+![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`.
 
@@ -27,12 +35,12 @@ Filter by severity:
 $ trivy k8s --severity=CRITICAL --report=all cluster
 ```
 
-Filter by security check (Vulnerabilities, Secrets or Misconfigurations):
+Filter by scanners (Vulnerabilities, Secrets or Misconfigurations):
 
 ```
-$ trivy k8s --security-checks=secret --report=summary cluster
+$ trivy k8s --scanners=secret --report=summary cluster
 # or
-$ trivy k8s --security-checks=config --report=summary cluster
+$ trivy k8s --scanners=config --report=summary cluster
 ```
 
 Scan a specific namespace:
@@ -233,7 +241,7 @@ $ trivy k8s --format json -o results.json cluster
 
 
 
-## Infra checks
+### 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
@@ -263,17 +271,69 @@ 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 `--security-checks=config`
+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 --security-checks=config # scan only infra
+$ 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 --security-checks=config # scan all components besides infra
+$ trivy k8s cluster --report summary --components=workload --scanners=config # scan all components besides infra
 ```
 
-	
+### 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                                                                                                           |
+|----------------------------------------------|----------------------|---------------------------------------------------------------------------------------------------------------------|
+| NSA, CISA Kubernetes Hardening Guidance v1.2 | `k8s-nsa`            | [Link](https://media.defense.gov/2022/Aug/29/2003066362/-1/-1/0/CTR_KUBERNETES_HARDENING_GUIDANCE_1.2_20220829.PDF) |
+| CIS Benchmark for Kubernetes v1.23           | `k8s-cis`            | [Link](https://www.cisecurity.org/benchmark/kubernetes)                                                             |
+| 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
+
+Scan a full cluster and generate a compliance summary report:
+
+```
+$ trivy k8s cluster --compliance=<compliance_id> --report summary
+```
+
+***Note*** : The `Issues` column represent the total number of failed checks for this control.
+
+
+Get all of the detailed output for checks:
+
+```
+trivy k8s cluster --compliance=<compliance_id> --report all
+```
+
+Report result in JSON format:
+
+```
+trivy k8s cluster --compliance=<compliance_id> --report summary --format json
+```
+
+```
+trivy k8s cluster --compliance=<compliance_id> --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

docs/docs/target/rootfs.md

@@ -0,0 +1,15 @@
+# Rootfs
+Rootfs scanning is for special use cases such as
+
+- Host machine
+- [Root filesystem](../advanced/container/embed-in-dockerfile.md)
+- [Unpacked filesystem](../advanced/container/unpacked-filesystem.md)
+ 
+```bash
+$ 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](../vulnerability/detection/language.md) for the differences.

docs/docs/target/sbom.md

@@ -0,0 +1,113 @@
+# SBOM scanning
+Trivy can take the following SBOM formats as an input and scan for vulnerabilities.
+
+- CycloneDX
+- SPDX
+- SPDX JSON
+- CycloneDX-type attestation
+
+To scan SBOM, you can use the `sbom` subcommand and pass the path to the SBOM.
+The input format is automatically detected.
+
+```bash
+$ trivy sbom /path/to/sbom_file
+```
+
+!!! note
+    Passing SBOMs generated by tool other than Trivy may result in inaccurate detection 
+    because Trivy relies on custom properties in SBOM for accurate scanning.
+
+## CycloneDX
+Trivy supports CycloneDX as an input.
+
+!!! note
+    CycloneDX XML is not supported at the moment.
+
+
+```bash
+$ trivy sbom /path/to/cyclonedx.json
+```
+
+!!! note
+    If you want to generate a CycloneDX report from a CycloneDX input, please be aware that the output stores references to your original CycloneDX report and contains only detected vulnerabilities, not components.
+    The report is called [BOV](https://cyclonedx.org/capabilities/sbom/).
+
+## SPDX
+Trivy supports the SPDX SBOM as an input.
+
+The following SPDX formats are supported:
+
+- Tag-value (`--format spdx`)
+- JSON (`--format spdx-json`)
+
+```bash
+$ trivy image --format spdx-json --output spdx.json alpine:3.16.0
+$ trivy sbom spdx.json
+```
+
+<details>
+<summary>Result</summary>
+
+```
+2022-09-15T21:32:27.168+0300    INFO    Vulnerability scanning is enabled
+2022-09-15T21:32:27.169+0300    INFO    Detected SBOM format: spdx-json
+2022-09-15T21:32:27.210+0300    INFO    Detected OS: alpine
+2022-09-15T21:32:27.210+0300    INFO    Detecting Alpine vulnerabilities...
+2022-09-15T21:32:27.211+0300    INFO    Number of language-specific files: 0
+
+spdx.json (alpine 3.16.0)
+=========================
+Total: 5 (UNKNOWN: 0, LOW: 0, MEDIUM: 2, HIGH: 2, CRITICAL: 1)
+
+┌──────────────┬────────────────┬──────────┬───────────────────┬───────────────┬────────────────────────────────────────────────────────────┐
+│   Library    │ Vulnerability  │ Severity │ Installed Version │ Fixed Version │                           Title                            │
+├──────────────┼────────────────┼──────────┼───────────────────┼───────────────┼────────────────────────────────────────────────────────────┤
+│ busybox      │ CVE-2022-30065 │ HIGH     │ 1.35.0-r13        │ 1.35.0-r15    │ busybox: A use-after-free in Busybox's awk applet leads to │
+│              │                │          │                   │               │ denial of service...                                       │
+│              │                │          │                   │               │ https://avd.aquasec.com/nvd/cve-2022-30065                 │
+├──────────────┼────────────────┼──────────┼───────────────────┼───────────────┼────────────────────────────────────────────────────────────┤
+│ libcrypto1.1 │ CVE-2022-2097  │ MEDIUM   │ 1.1.1o-r0         │ 1.1.1q-r0     │ openssl: AES OCB fails to encrypt some bytes               │
+│              │                │          │                   │               │ https://avd.aquasec.com/nvd/cve-2022-2097                  │
+├──────────────┤                │          │                   │               │                                                            │
+│ libssl1.1    │                │          │                   │               │                                                            │
+│              │                │          │                   │               │                                                            │
+├──────────────┼────────────────┼──────────┼───────────────────┼───────────────┼────────────────────────────────────────────────────────────┤
+│ ssl_client   │ CVE-2022-30065 │ HIGH     │ 1.35.0-r13        │ 1.35.0-r15    │ busybox: A use-after-free in Busybox's awk applet leads to │
+│              │                │          │                   │               │ denial of service...                                       │
+│              │                │          │                   │               │ https://avd.aquasec.com/nvd/cve-2022-30065                 │
+├──────────────┼────────────────┼──────────┼───────────────────┼───────────────┼────────────────────────────────────────────────────────────┤
+│ zlib         │ CVE-2022-37434 │ CRITICAL │ 1.2.12-r1         │ 1.2.12-r2     │ zlib: a heap-based buffer over-read or buffer overflow in  │
+│              │                │          │                   │               │ inflate in inflate.c...                                    │
+│              │                │          │                   │               │ https://avd.aquasec.com/nvd/cve-2022-37434                 │
+└──────────────┴────────────────┴──────────┴───────────────────┴───────────────┴────────────────────────────────────────────────────────────┘
+```
+
+</details>
+
+## SBOM attestation
+
+You can also scan an SBOM attestation.
+In the following example, [Cosign](https://github.com/sigstore/cosign) gets an attestation and Trivy scans it.
+You must create CycloneDX-type attestation before trying the example.
+To learn more about how to create an CycloneDX-Type attestation and attach it to an image, see the [SBOM attestation page](../attestation/sbom.md#sign-with-a-local-key-pair).
+
+```bash
+$ cosign verify-attestation --key /path/to/cosign.pub --type cyclonedx <IMAGE> > sbom.cdx.intoto.jsonl
+$ trivy sbom ./sbom.cdx.intoto.jsonl
+
+sbom.cdx.intoto.jsonl (alpine 3.7.3)
+=========================
+Total: 2 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 0, CRITICAL: 2)
+
+┌────────────┬────────────────┬──────────┬───────────────────┬───────────────┬──────────────────────────────────────────────────────────┐
+│  Library   │ Vulnerability  │ Severity │ Installed Version │ Fixed Version │                          Title                           │
+├────────────┼────────────────┼──────────┼───────────────────┼───────────────┼──────────────────────────────────────────────────────────┤
+│ musl       │ CVE-2019-14697 │ CRITICAL │ 1.1.18-r3         │ 1.1.18-r4     │ musl libc through 1.1.23 has an x87 floating-point stack │
+│            │                │          │                   │               │ adjustment im ......                                     │
+│            │                │          │                   │               │ https://avd.aquasec.com/nvd/cve-2019-14697               │
+├────────────┤                │          │                   │               │                                                          │
+│ musl-utils │                │          │                   │               │                                                          │
+│            │                │          │                   │               │                                                          │
+│            │                │          │                   │               │                                                          │
+└────────────┴────────────────┴──────────┴───────────────────┴───────────────┴──────────────────────────────────────────────────────────┘
+```

docs/docs/target/vm.md

@@ -3,20 +3,21 @@
 !!! warning "EXPERIMENTAL"
     This feature might change without preserving backwards compatibility.
 
-## Scanning
-Trivy supports VM image scanning for vulnerabilities, secrets, etc.
+To scan virtual machine (VM) images, you can use the `vm` subcommand.
+
+## Targets
 The following targets are currently supported:
 
 - Local file
-- [AWS EC2][aws]
-
-To scan VM images, you can use the `vm` subcommand.
-
+- AWS EC2
+    - Amazon Machine Image (AMI)
+    - Amazon Elastic Block Store (EBS) Snapshot
+ 
 ### Local file
 Pass the path to your local VM image file.
 
 ```bash
-$ trivy vm --security-checks vuln disk.vmdk
+$ trivy vm --scanners vuln disk.vmdk
 ```
 
 <details>
@@ -62,11 +63,126 @@ Total: 802 (UNKNOWN: 0, LOW: 17, MEDIUM: 554, HIGH: 221, CRITICAL: 10)
 
 </details>
 
-### AWS EC2
+### Amazon Machine Image (AMI)
+You can specify your AMI ID with the `ami:` prefix.
 
-See [here][aws] for the detail.
+```shell
+$ trivy vm ami:${your_ami_id}
+```
 
-## Supported architectures
+!!! note
+    AMIs in the marketplace are not supported because the EBS direct APIs don't support that.
+    See [the AWS documentation][ebsapi-elements] for the detail.
+
+#### Example
+
+```shell
+$ trivy vm --scanners vuln ami:ami-0123456789abcdefg
+```
+
+If you want to scan a AMI of non-default setting region, you can set any region via `--aws-region` option.
+
+```shell
+$ trivy vm --aws-region ap-northeast-1 ami:ami-0123456789abcdefg
+```
+
+
+#### Required Actions
+Some actions on EBS are also necessary since Trivy scans an EBS snapshot tied to the specified AMI under the hood.
+
+- ec2:DescribeImages
+- ebs:ListSnapshotBlocks
+- ebs:GetSnapshotBlock
+
+### Amazon Elastic Block Store (EBS) Snapshot
+You can specify your EBS snapshot ID with the `ebs:` prefix.
+
+```shell
+$ trivy vm ebs:${your_ebs_snapshot_id}
+```
+
+!!! note
+    Public snapshots are not supported because the EBS direct APIs don't support that.
+    See [the AWS documentation][ebsapi-elements] for the detail.
+
+#### Example
+
+```shell
+$ trivy vm --scanners vuln ebs:snap-0123456789abcdefg
+```
+
+
+If you want to scan an EBS Snapshot of non-default setting region, you can set any region via `--aws-region` option.
+
+```shell
+$ trivy vm --aws-region ap-northeast-1 ebs:ebs-0123456789abcdefg
+```
+
+The above command takes a while as it calls EBS API and fetches the EBS blocks.
+If you want to scan the same snapshot several times, you can download the snapshot locally by using [coldsnap][coldsnap] maintained by AWS.
+Then, Trivy can scan the local VM image file.
+
+```shell
+$ coldsnap download snap-0123456789abcdefg disk.img
+$ trivy vm ./disk.img
+```
+
+#### Required Actions
+
+- ebs:ListSnapshotBlocks
+- ebs:GetSnapshotBlock
+
+## Scanners
+Trivy supports VM image scanning for
+
+- Vulnerabilities
+- Misconfigurations
+- Secrets
+- Licenses
+
+### Vulnerabilities
+It is enabled by default.
+You can simply specify your VM image location.
+It detects known vulnerabilities in your VM image.
+See [here](../vulnerability/scanning.md) for the detail.
+
+```
+$ trivy vm [YOUR_VM_IMAGE]
+```
+
+### Misconfigurations
+It is supported, but it is not useful in most cases.
+As mentioned [here](../misconfiguration/scanning.md), Trivy mainly supports Infrastructure as Code (IaC) files for misconfigurations.
+If your VM image includes IaC files such as Kubernetes YAML files or Terraform files, you should enable this feature with `--scanners config`.
+
+```
+$ trivy vm --scanners config [YOUR_VM_IMAGE]
+```
+
+### Secrets
+It is enabled by default.
+See [here](../secret/scanning.md) for the detail.
+
+```shell
+$ trivy vm [YOUR_VM_IMAGE]
+```
+
+!!! tip
+    The scanning could be faster if you enable only vulnerability scanning (`--scanners vuln`) because Trivy tries to download only necessary blocks for vulnerability detection.
+
+### Licenses
+It is disabled by default.
+See [here](../licenses/scanning.md) for the detail.
+
+```shell
+$ trivy vm --scanners license [YOUR_VM_IMAGE]
+```
+
+## SBOM generation
+Trivy can generate SBOM for VM images.
+See [here](../sbom/index.md) for the detail.
+
+## Supported Architectures
 
 ### Virtual machine images
 
@@ -117,5 +233,9 @@ Reference: [VMware Virtual Disk Format 1.1.pdf][vmdk]
 | EXT2/3            |         |
 | ZFS               |         |
 
-[aws]: ./aws.md
-[vmdk]: https://www.vmware.com/app/vmdk/?src=vmdk
+
+[aws]: ../vm/aws.md
+[vmdk]: https://www.vmware.com/app/vmdk/?src=vmdk
+[ebsapi-elements]: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-accessing-snapshot.html#ebsapi-elements
+[coldsnap]: https://github.com/awslabs/coldsnap
+

docs/docs/vm/aws.md

@@ -1,83 +0,0 @@
-# AWS EC2
-
-Trivy can scan the following targets in AWS EC2.
-
-- Amazon Machine Image (AMI)
-- Elastic Block Store (EBS) Snapshot
-
-## Amazon Machine Image (AMI)
-You can specify your AMI ID with the `ami:` prefix.
-
-```shell
-$ trivy vm ami:${your_ami_id}
-```
-
-!!! note
-    AMIs in the marketplace are not supported because the EBS direct APIs don't support that.
-    See [the AWS documentation][ebsapi-elements] for the detail.
-
-### Example
-
-```shell
-$ trivy vm --security-checks vuln ami:ami-0123456789abcdefg
-```
-
-!!! tip
-    The scanning could be faster if you enable only vulnerability scanning (`--security-checks vuln`) because Trivy tries to download only necessary blocks for vulnerability detection.
-
-If you want to scan a AMI of non-default setting region, you can set any region via `--aws-region` option.
-
-```shell
-$ trivy vm --aws-region ap-northeast-1 ami:ami-0123456789abcdefg
-```
-
-
-### Required Actions
-Some actions on EBS are also necessary since Trivy scans an EBS snapshot tied to the specified AMI under the hood.
-
-- ec2:DescribeImages
-- ebs:ListSnapshotBlocks
-- ebs:GetSnapshotBlock
-
-## Elastic Block Store (EBS) Snapshot
-You can specify your EBS snapshot ID with the `ebs:` prefix.
-
-```shell
-$ trivy vm ebs:${your_ebs_snapshot_id}
-```
-
-!!! note
-    Public snapshots are not supported because the EBS direct APIs don't support that.
-    See [the AWS documentation][ebsapi-elements] for the detail.
-
-### Example
-```shell
-$ trivy vm --security-checks vuln ebs:snap-0123456789abcdefg
-```
-
-!!! tip
-The scanning could be faster if you enable only vulnerability scanning (`--security-checks vuln`) because Trivy tries to download only necessary blocks for vulnerability detection.
-
-If you want to scan an EBS Snapshot of non-default setting region, you can set any region via `--aws-region` option.
-
-```shell
-$ trivy vm --aws-region ap-northeast-1 ebs:ebs-0123456789abcdefg
-```
-
-
-The above command takes a while as it calls EBS API and fetches the EBS blocks.
-If you want to scan the same snapshot several times, you can download the snapshot locally by using [coldsnap][coldsnap] maintained by AWS.
-Then, Trivy can scan the local VM image file.
-
-```shell
-$ coldsnap download snap-0123456789abcdefg disk.img
-$ trivy vm ./disk.img
-```
-
-### Required Actions
-
-- ebs:ListSnapshotBlocks
-- ebs:GetSnapshotBlock
-
-[ebsapi-elements]: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-accessing-snapshot.html#ebsapi-elements
-[coldsnap]: https://github.com/awslabs/coldsnap

docs/docs/vulnerability/db.md

@@ -0,0 +1,38 @@
+# 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](./examples/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/vulnerability/detection/data-source.md

@@ -37,6 +37,7 @@
 | 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
@@ -79,6 +80,7 @@ The severity is from the selected data source. If the data source does not provi
 [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
 
 [php]: https://github.com/FriendsOfPHP/security-advisories

docs/docs/vulnerability/detection/language.md

@@ -6,12 +6,12 @@
 |----------|--------------------------------------------------------------------------------------------|:---------:|:----------:|:---------------:|:---------------:|------------------|:------------------------:|
 | Ruby     | Gemfile.lock                                                                               |     -     |     -      |        ✅        |        ✅        | included         |            -             |
 |          | gemspec                                                                                    |     ✅     |     ✅      |        -        |        -        | included         |            -             |
-| Python   | Pipfile.lock                                                                               |     -     |     -      |        ✅        |        ✅        | excluded         |            -             |
+| Python   | Pipfile.lock                                                                               |     -     |     -      |        ✅        |        ✅        | excluded         |            ✅             |
 |          | poetry.lock                                                                                |     -     |     -      |        ✅        |        ✅        | excluded         |            -             |
 |          | requirements.txt                                                                           |     -     |     -      |        ✅        |        ✅        | included         |            -             |
 |          | egg package[^1]                                                                            |     ✅     |     ✅      |        -        |        -        | excluded         |            -             |
 |          | wheel package[^2]                                                                          |     ✅     |     ✅      |        -        |        -        | excluded         |            -             |
-| PHP      | composer.lock                                                                              |     ✅     |     ✅      |        ✅        |        ✅        | excluded         |            -             |
+| PHP      | composer.lock                                                                              |     ✅     |     ✅      |        ✅        |        ✅        | excluded         |            ✅             |
 | Node.js  | package-lock.json                                                                          |     -     |     -      |        ✅        |        ✅        | excluded         |            ✅             |
 |          | yarn.lock                                                                                  |     -     |     -      |        ✅        |        ✅        | included         |            ✅             |
 |          | pnpm-lock.yaml                                                                             |     -     |     -      |        ✅        |        ✅        | excluded         |            -             |
@@ -24,10 +24,11 @@
 |          | *gradle.lockfile                                                                           |     -     |     -      |        ✅        |        ✅        | excluded         |            -             |
 | Go       | Binaries built by Go[^6]                                                                   |     ✅     |     ✅      |        -        |        -        | excluded         |            -             |
 |          | go.mod[^7]                                                                                 |     -     |     -      |        ✅        |        ✅        | included         |            -             |
-| Rust     | Cargo.lock                                                                                 |     ✅     |     ✅      |        ✅        |        ✅        | included         |            -             |
+| Rust     | Cargo.lock                                                                                 |     ✅     |     ✅      |        ✅        |        ✅        | excluded         |            ✅             |
 |          | Binaries built with [cargo-auditable](https://github.com/rust-secure-code/cargo-auditable) |     ✅     |     ✅      |        -        |        -        | excluded         |            -             |
 | C/C++    | conan.lock[^13]                                                                            |     -     |     -      |        ✅        |        ✅        | excluded         |            -             |   
 | Elixir   | mix.lock[^13]                                                                              |     -     |     -      |        ✅        |        ✅        | excluded         |            ✅             |
+| Dart     | pubspec.lock                                                                               |     ✅     |     ✅      |        -        |        -        | included         |            -             |
 
 The path of these files does not matter.
 
@@ -46,3 +47,4 @@ Example: [Dockerfile](https://github.com/aquasecurity/trivy-ci-test/blob/main/Do
 [^11]: ✅ means "enabled" and `-` means "disabled" in the git repository scanning
 [^12]: ✅ means that Trivy detects line numbers where each dependency is declared in the scanned file. Only supported in [json](../examples/report.md#json) and [sarif](../examples/report.md#sarif) formats. SARIF uses `startline == 1 and endline == 1` for unsupported file types
 [^13]: To scan a filename other than the default filename use [file-patterns](../examples/others.md#file-patterns)
+[^14]: When you scan `Cargo.lock` and `Cargo.toml` together. See about it [here](../languages/rust.md#cargo).

docs/docs/vulnerability/detection/os.md

@@ -9,11 +9,11 @@ The unfixed/unfixable vulnerabilities mean that the patch has not yet been provi
 | 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                                         | Installed by yum/rpm          |                  NO                  |
-| Rocky Linux                      | 8                                         | Installed by yum/rpm          |                  NO                  |
+| 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, 2022                                | Installed by yum/rpm          |                  NO                  |
+| 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                  |
@@ -21,5 +21,60 @@ The unfixed/unfixable vulnerabilities mean that the patch has not yet been provi
 | Ubuntu                           | All versions supported by Canonical       | Installed by apt/apt-get/dpkg |                 YES                  |
 | Distroless[^2]                   | Any                                       | Installed by apt/apt-get/dpkg |                 YES                  |
 
+## Distributions
+### CBL-Mariner
+Trivy scans [CBL-Mariner][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
+
+### Data source
+See [here][source].
+
+[mariner]: https://github.com/microsoft/CBL-Mariner
+[source]: data-source.md

docs/docs/vulnerability/detection/supported.md

@@ -1,23 +0,0 @@
-# Supported
-
-## Container Runtime
-- [Docker Engine](https://docs.docker.com/engine/)
-- [Podman](../../advanced/container/podman.md)
-- [containerd](../../advanced/container/containerd.md)
-
-## Container Registry
-- [Docker Registry HTTP API V2](https://docs.docker.com/registry/spec/api/)
-- [OCI Distribution Specification](https://github.com/opencontainers/distribution-spec)
-
-## Image Tar Formats
-Trivy scans a tar image with the following format.
-
-- [Docker Image Specification](https://github.com/moby/moby/tree/master/image/spec)
-    - [Moby Project](https://github.com/moby/moby/)
-    - [Buildah](https://github.com/containers/buildah)
-    - [Podman](https://github.com/containers/podman)
-    - [img](https://github.com/genuinetools/img)
-- [Kaniko](https://github.com/GoogleContainerTools/kaniko)
-
-## Image Layout
-- [OCI Image Format Specification](https://github.com/opencontainers/image-spec)

docs/docs/vulnerability/distributions.md

@@ -1,58 +0,0 @@
-## CBL-Mariner
-Trivy scans [CBL-Mariner][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)
-    ```
-
-=== "fs"
-    ```
-    ➜ docker run  -it --rm --entrypoint bin/bash mcr.microsoft.com/cbl-mariner/base/core:2.0 
-    
-    root [ / ]# tdnf -y install ca-certificates
-    ...
-
-    root [ / ]# rpm -ivh https://github.com/aquasecurity/trivy/releases/download/v0.30.4/trivy_0.30.4_Linux-64bit.rpm
-    ...
-    
-    root [ / ]# trivy fs /
-    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 '--security-checks 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)
-    ```
-
-### Data source
-See [here][source].
-
-[mariner]: https://github.com/microsoft/CBL-Mariner
-[source]: detection/data-source.md

docs/docs/vulnerability/examples/cache.md

@@ -44,13 +44,18 @@ Two options:
 $ trivy server --cache-backend redis://localhost:6379
 ```
 
-Trivy also support for connecting to Redis using TLS, you only need to specify `--redis-ca` , `--redis-cert` , and `--redis-key` option.
+If you want to use TLS with Redis, you can enable it by specifying the `--redis-tls` flag.
+
+```shell
+$ trivy server --cache-backend redis://localhost:6379 --redis-tls
+```
+
+Trivy also supports for connecting to Redis with your certificates.
+You need to specify `--redis-ca` , `--redis-cert` , and `--redis-key` options.
 
 ```
 $ trivy server --cache-backend redis://localhost:6379 \
   --redis-ca /path/to/ca-cert.pem \
   --redis-cert /path/to/cert.pem \
   --redis-key /path/to/key.pem
-```
-
-TLS option for redis is hidden from Trivy command-line flag, but you still can use it.
+```

docs/docs/vulnerability/examples/db.md

@@ -1,9 +1,7 @@
 # Vulnerability DB
 
 ## Skip update of vulnerability DB
-`Trivy` downloads its vulnerability database every 12 hours when it starts operating.
-This is usually fast, as the size of the DB is only 10~30MB.
-But if you want to skip even that, use the `--skip-db-update` option.
+If you want to skip downloading the vulnerability database, use the `--skip-db-update` option.
 
 ```
 $ trivy image --skip-db-update python:3.4-alpine3.9
@@ -43,3 +41,13 @@ $ trivy image --download-db-only
 ```
 $ trivy image --db-repository registry.gitlab.com/gitlab-org/security-products/dependencies/trivy-db
 ```
+
+## Java Vulnerability DB
+The same options are also available for the Java index DB, which is used for scanning Java applications.
+Skipping an update can be done by using the `--skip-java-db-update` option, while `--download-java-db-only` can be used to only download the Java index DB.
+
+Downloading the Java index DB from an external OCI registry can be done by using the `--java-db-repository` option.
+
+```
+$ trivy image --java-db-repository registry.gitlab.com/gitlab-org/security-products/dependencies/trivy-java-db --download-java-db-only
+```