chore(deps): bump github.com/sigstore/rekor from 1.2.0 to 1.2.1 (#4533)

Co-authored-by: DmitriyLewen <91113035+DmitriyLewen@users.noreply.github.com>
Co-authored-by: DmitriyLewen <dmitriy.lewen@smartforce.io>

.github/DISCUSSION_TEMPLATE/bugs.yml

@@ -0,0 +1,122 @@
+labels: ["kind/bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        #### Note
+        Feel free to raise a bug report if something doesn't work as expected.
+        Please ensure that you're not creating a duplicate report by searching the [issues](https://github.com/aquasecurity/trivy/issues)/[discussions](https://github.com/aquasecurity/trivy/discussions) beforehand.
+        If you see any false positives or false negatives, please file a ticket [here](https://github.com/aquasecurity/trivy/discussions/new?category=false-detection).
+        
+        Please also check [our contribution guidelines](https://aquasecurity.github.io/trivy/latest/community/contribute/discussion/).
+  - type: textarea
+    attributes:
+      label: Description
+      description: Briefly describe the problem you are having in a few paragraphs.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Desired Behavior
+      description: What did you expect to happen?
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Actual Behavior
+      description: What happened instead?
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Reproduction Steps
+      description: How do you trigger this bug? Please walk us through it step by step.
+      value: |
+        1.
+        2.
+        3.
+        ...
+      render: bash
+    validations:
+      required: true
+  - type: dropdown
+    attributes:
+      label: Target
+      description: Which target are you scanning? It is equal to which subcommand you are using.
+      options:
+        - Container Image
+        - Filesystem
+        - Git Repository
+        - Virtual Machine Image
+        - Kubernetes
+        - AWS
+        - SBOM
+    validations:
+      required: false
+  - type: dropdown
+    attributes:
+      label: Scanner
+      description: Which scanner are you using?
+      options:
+        - Vulnerability
+        - Misconfiguration
+        - Secret
+        - License
+    validations:
+      required: false
+  - type: dropdown
+    attributes:
+      label: Output Format
+      description: Which output format are you using?
+      options:
+        - Table
+        - JSON
+        - Template
+        - SARIF
+        - CycloneDX
+        - SPDX
+    validations:
+      required: false
+  - type: dropdown
+    attributes:
+      label: Mode
+      description: Which mode are you using? Specify "Standalone" if you are not using `trivy server`.
+      options:
+        - Standalone
+        - Client/Server
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Debug Output
+      description: Output of run with `--debug`
+      placeholder: "$ trivy <target> <subject> --debug"
+      render: bash
+    validations:
+      required: true
+  - type: input
+    attributes:
+      label: Operating System
+      description: On what operating system are you running Trivy?
+      placeholder: "e.g. macOS Big Sur"
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Version
+      description: Output of `trivy --version`
+      placeholder: "$ trivy --version"
+      render: bash
+    validations:
+      required: true
+  - type: checkboxes
+    attributes:
+      label: Checklist
+      description: Have you tried the following?
+      options:
+        - label: Run `trivy --reset`
+        - label: Read [the troubleshooting](https://aquasecurity.github.io/trivy/latest/docs/references/troubleshooting/)
+  - type: markdown
+    attributes:
+      value: |
+        We would be happy if you could share how you are using Trivy [here](https://github.com/aquasecurity/trivy/discussions/new?category=show-and-tell).

.github/DISCUSSION_TEMPLATE/documentation.yml

@@ -0,0 +1,28 @@
+labels: ["kind/documentation"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        #### Note
+        Feel free to create a docs report if something doesn't work as expected or is unclear in the documentation.
+        Please ensure that you're not creating a duplicate report by searching the [issues](https://github.com/aquasecurity/trivy/issues)/[discussions](https://github.com/aquasecurity/trivy/discussions) beforehand.
+        
+        Please also check [our contribution guidelines](https://aquasecurity.github.io/trivy/latest/community/contribute/discussion/).
+  - type: textarea
+    attributes:
+      label: Description
+      description: Briefly describe the what has been unclear in the existing documentation
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Link
+      description: Please provide a link to the current documentation or where you thought to find the information you were looking for
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Suggestions
+      description: What would you like to have added or changed in the documentation?
+    validations:
+      required: true

.github/DISCUSSION_TEMPLATE/false-detection.yml

@@ -0,0 +1,94 @@
+body:
+  - type: markdown
+    attributes:
+      value: |
+        #### Note
+        Feel free to raise a bug report if something doesn't work as expected.
+        Please ensure that you're not creating a duplicate report by searching the [issues](https://github.com/aquasecurity/trivy/issues)/[discussions](https://github.com/aquasecurity/trivy/discussions) beforehand.
+        
+        Please also check [our contribution guidelines](https://aquasecurity.github.io/trivy/latest/community/contribute/discussion/).
+  - type: input
+    attributes:
+      label: IDs
+      description: List the IDs of vulnerabilities, misconfigurations, secrets, or licenses that are either not detected or mistakenly detected.
+      placeholder: "e.g. CVE-2021-44228, CVE-2022-22965"
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Description
+      description: Describe the false detection.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Reproduction Steps
+      description: How do you trigger this bug? Please walk us through it step by step.
+      value: |
+        1.
+        2.
+        3.
+        ...
+      render: bash
+    validations:
+      required: true
+  - type: dropdown
+    attributes:
+      label: Target
+      description: Which target are you scanning? It is equal to which subcommand you are using.
+      options:
+        - Container Image
+        - Filesystem
+        - Git Repository
+        - Virtual Machine Image
+        - Kubernetes
+        - AWS
+        - SBOM
+    validations:
+      required: true
+  - type: dropdown
+    attributes:
+      label: Scanner
+      description: Which scanner are you using?
+      options:
+        - Vulnerability
+        - Misconfiguration
+        - Secret
+        - License
+    validations:
+      required: true
+  - type: input
+    attributes:
+      label: Target OS
+      description: What operating system are you scanning? Fill in this field if the scanning target is an operating system.
+      placeholder: "Example: Ubuntu 22.04"
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Debug Output
+      description: Output of run with `--debug`
+      placeholder: "$ trivy <target> <subject> --debug"
+      render: bash
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Version
+      description: Output of `trivy --version`
+      placeholder: "$ trivy --version"
+      render: bash
+    validations:
+      required: true
+  - type: checkboxes
+    attributes:
+      label: Checklist
+      options:
+        - label: Read [the documentation regarding wrong detection](https://aquasecurity.github.io/trivy/dev/community/contribute/discussion/#false-detection)
+        - label: Ran Trivy with `-f json` that shows data sources and confirmed that the security advisory in data sources was correct
+    validations:
+      required: true
+  - type: markdown
+    attributes:
+      value: |
+        We would be happy if you could share how you are using Trivy [here](https://github.com/aquasecurity/trivy/discussions/new?category=show-and-tell).

.github/DISCUSSION_TEMPLATE/ideas.yml

@@ -0,0 +1,45 @@
+labels: ["kind/feature"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        #### Note
+        Feel free to share your idea.
+        Please ensure that you're not creating a duplicate ticket by searching the [issues](https://github.com/aquasecurity/trivy/issues)/[discussions](https://github.com/aquasecurity/trivy/discussions) beforehand.
+        
+        Please also check [our contribution guidelines](https://aquasecurity.github.io/trivy/latest/community/contribute/discussion/).
+  - type: textarea
+    attributes:
+      label: Description
+      description: Describe your idea.
+    validations:
+      required: true
+  - type: dropdown
+    attributes:
+      label: Target
+      description: Which target is your idea related to?
+      options:
+        - Container Image
+        - Filesystem
+        - Git Repository
+        - Virtual Machine Image
+        - Kubernetes
+        - AWS
+        - SBOM
+    validations:
+      required: false
+  - type: dropdown
+    attributes:
+      label: Scanner
+      description: Which scanner is your idea related to?
+      options:
+        - Vulnerability
+        - Misconfiguration
+        - Secret
+        - License
+    validations:
+      required: false
+  - type: markdown
+    attributes:
+      value: |
+        We would be happy if you could share how you are using Trivy [here](https://github.com/aquasecurity/trivy/discussions/new?category=show-and-tell).

.github/DISCUSSION_TEMPLATE/q-a.yml

@@ -0,0 +1,82 @@
+labels: ["triage/support"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        #### Note
+        If you have any troubles/questions, feel free to ask.
+        Please ensure that you're not asking a duplicate question by searching the [issues](https://github.com/aquasecurity/trivy/issues)/[discussions](https://github.com/aquasecurity/trivy/discussions) beforehand.
+        
+        Please also check [our contribution guidelines](https://aquasecurity.github.io/trivy/latest/community/contribute/discussion/).
+  - type: textarea
+    attributes:
+      label: Question
+      description: What kind of problem are you facing? Or, what questions do you have?
+    validations:
+      required: true
+  - type: dropdown
+    attributes:
+      label: Target
+      description: Which target are you scanning? It is equal to which subcommand you are using.
+      options:
+        - Container Image
+        - Filesystem
+        - Git Repository
+        - Virtual Machine Image
+        - Kubernetes
+        - AWS
+        - SBOM
+    validations:
+      required: false
+  - type: dropdown
+    attributes:
+      label: Scanner
+      description: Which scanner are you using?
+      options:
+        - Vulnerability
+        - Misconfiguration
+        - Secret
+        - License
+    validations:
+      required: false
+  - type: dropdown
+    attributes:
+      label: Output Format
+      description: Which output format are you using?
+      options:
+        - Table
+        - JSON
+        - Template
+        - SARIF
+        - CycloneDX
+        - SPDX
+    validations:
+      required: false
+  - type: dropdown
+    attributes:
+      label: Mode
+      description: Which mode are you using? Specify "Standalone" if you are not using `trivy server`.
+      options:
+        - Standalone
+        - Client/Server
+    validations:
+      required: false
+  - type: input
+    attributes:
+      label: Operating System
+      description: What operating system are you using?
+      placeholder: "Example: macOS Big Sur"
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Version
+      description: Output of `trivy --version`
+      placeholder: "$ trivy --version"
+      render: bash
+    validations:
+      required: false
+  - type: markdown
+    attributes:
+      value: |
+        We would be happy if you could share how you are using Trivy [here](https://github.com/aquasecurity/trivy/discussions/new?category=show-and-tell).

.github/ISSUE_TEMPLATE/BUG_REPORT.md

@@ -1,31 +0,0 @@
----
-name: Bug Report
-labels: kind/bug
-about: If something isn't working as expected.
----
-
-## Description
-
-<!--
-Briefly describe the problem you are having in a few paragraphs.
--->
-
-## What did you expect to happen?
-
-
-## What happened instead?
-
-
-## Output of run with `-debug`:
-
-```
-(paste your output here)
-```
-
-## Output of `trivy -v`:
-
-```
-(paste your output here)
-```
-
-## Additional details (base image name, container registry info...):

.github/ISSUE_TEMPLATE/FEATURE_REQUEST.md

@@ -1,9 +0,0 @@
----
-name: Feature Request
-labels: kind/feature
-about: I have a suggestion (and might want to implement myself)!
----
-
-<!--
-If this is a FEATURE REQUEST, request format does not matter!
--->

.github/ISSUE_TEMPLATE/SUPPORT_QUESTION.md

@@ -1,10 +0,0 @@
----
-name: Support Question
-labels: triage/support
-about: If you have a question about Trivy.
----
-
-<!--
-If you have a trouble, feel free to ask.
-Make sure you're not asking duplicate question by searching on the issues lists.
--->

.github/ISSUE_TEMPLATE/WRONG_DETECTION.md

@@ -1,33 +0,0 @@
----
-name: Wrong Detection
-labels: ["kind/bug"]
-about: If Trivy doesn't detect something, or shows false positive detection
----
-
-## Checklist
-- [ ] I've read [the documentation regarding wrong detection](https://aquasecurity.github.io/trivy/latest/community/contribute/issue/#wrong-detection).
-- [ ] I've confirmed that a security advisory in data sources was correct.
-    - Run Trivy with `-f json` that shows data sources and make sure that the security advisory is correct.
-
-
-## Description
-
-<!--
-Briefly describe the CVE that aren't detected and information about artifacts with this CVE.
--->
-
-## JSON Output of run with `-debug`:
-
-```
-(paste your output here)
-```
-
-## Output of `trivy -v`:
-
-```
-(paste your output here)
-```
-
-## Additional details (base image name, container registry info...):
-
-

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,17 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Report a false detection
+    url: https://github.com/aquasecurity/trivy/discussions/new?category=false-detection
+    about: Report false positives/negatives
+  - name: Report a bug
+    url: https://github.com/aquasecurity/trivy/discussions/new?category=bugs
+    about: Report bugs
+  - name: Enhance documentation
+    url: https://github.com/aquasecurity/trivy/discussions/new?category=documentation
+    about: Make suggestions to the documentation
+  - name: Request a feature enhancement
+    url: https://github.com/aquasecurity/trivy/discussions/new?category=ideas
+    about: Share ideas for new features
+  - name: Ask the community for help
+    url: https://github.com/aquasecurity/trivy/discussions/new?category=q-a
+    about: Ask questions and discuss with other community members

.github/workflows/canary.yaml

@@ -16,7 +16,7 @@ jobs:
     uses: ./.github/workflows/reusable-release.yaml
     with:
       goreleaser_config: goreleaser-canary.yml
-      goreleaser_options: '--snapshot --rm-dist --timeout 60m' # will not release
+      goreleaser_options: '--snapshot --clean --timeout 60m' # will not release
     secrets: inherit
 
   upload-binaries:

.github/workflows/release.yaml

@@ -10,7 +10,7 @@ jobs:
     uses: ./.github/workflows/reusable-release.yaml
     with:
       goreleaser_config: goreleaser.yml
-      goreleaser_options: '--rm-dist --timeout 90m'
+      goreleaser_options: '--clean --timeout 90m'
     secrets: inherit
 
   deploy-packages:

.github/workflows/reusable-release.yaml

@@ -27,7 +27,7 @@ jobs:
       contents: read  # Not required for public repositories, but for clarity
     steps:
       - name: Cosign install
-        uses: sigstore/cosign-installer@9becc617647dfa20ae7b1151972e9b3a2c338a2b
+        uses: sigstore/cosign-installer@204a51a57a74d190b284a0ce69b44bc37201f343
 
       - name: Set up QEMU
         uses: docker/setup-qemu-action@v2
@@ -75,16 +75,29 @@ jobs:
           args: mod -licenses -json -output bom.json
           version: ^v1
 
+      - name: "save gpg key"
+        env:
+          GPG_KEY: ${{ secrets.GPG_KEY }}
+        run: |
+          echo "$GPG_KEY" > gpg.key
+
       - name: GoReleaser
         uses: goreleaser/goreleaser-action@v4
         with:
-          version: v1.4.1
+          version: v1.16.2
           args: release -f=${{ inputs.goreleaser_config}} ${{ inputs.goreleaser_options}}
         env:
           GITHUB_TOKEN: ${{ secrets.ORG_REPO_TOKEN }}
+          NFPM_DEFAULT_RPM_PASSPHRASE: ${{ secrets.GPG_PASSPHRASE }}
+          GPG_FILE: "gpg.key"
 
-      ## push images to registries
-      ## only for canary build
+      - name: "remove gpg key"
+        run: |
+          rm gpg.key
+
+      # Push images to registries (only for canary build)
+      # The custom Dockerfile.canary is necessary
+      # because GoReleaser Free doesn't support pushing images with the `--snapshot` flag.
       - name: Build and push
         if: ${{ inputs.goreleaser_config == 'goreleaser-canary.yml' }}
         uses: docker/build-push-action@v4

.github/workflows/semantic-pr.yaml

@@ -47,6 +47,7 @@ jobs:
 
             alpine
             wolfi
+            chainguard
             redhat
             alma
             rocky

.github/workflows/stale-issues.yaml

@@ -7,7 +7,7 @@ jobs:
     timeout-minutes: 1
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/stale@v7
+    - uses: actions/stale@v8
       with:
         repo-token: ${{ secrets.GITHUB_TOKEN }}
         stale-issue-message: 'This issue is stale because it has been labeled with inactivity.'

.github/workflows/test.yaml

@@ -47,9 +47,10 @@ jobs:
         if: matrix.operating-system == 'ubuntu-latest'
 
       - name: Install tools
-        uses: aquaproj/aqua-installer@v2.0.2
+        uses: aquaproj/aqua-installer@v2.1.1
         with:
           aqua_version: v1.25.0
+          aqua_opts: ""
 
       - name: Check if CLI references are up-to-date
         run: |
@@ -76,13 +77,33 @@ jobs:
           go-version-file: go.mod
 
       - name: Install tools
-        uses: aquaproj/aqua-installer@v2.0.2
+        uses: aquaproj/aqua-installer@v2.1.1
         with:
           aqua_version: v1.25.0
 
       - name: Run integration tests
         run: mage test:integration
 
+  k8s-integration:
+    name: K8s Integration Test
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out code into the Go module directory
+        uses: actions/checkout@v3
+
+      - name: Set up Go
+        uses: actions/setup-go@v4
+        with:
+          go-version-file: go.mod
+
+      - name: Install tools
+        uses: aquaproj/aqua-installer@v2.1.1
+        with:
+          aqua_version: v1.25.0
+
+      - name: Run k8s integration tests
+        run: mage test:k8s
+
   module-test:
     name: Module Integration Test
     runs-on: ubuntu-latest
@@ -96,7 +117,7 @@ jobs:
           go-version-file: go.mod
 
       - name: Install tools
-        uses: aquaproj/aqua-installer@v2.0.2
+        uses: aquaproj/aqua-installer@v2.1.1
         with:
           aqua_version: v1.25.0
 
@@ -132,6 +153,7 @@ jobs:
     - name: Run GoReleaser
       uses: goreleaser/goreleaser-action@v4
       with:
-        version: v1.4.1
-        args: release --skip-sign --snapshot --rm-dist --skip-publish --timeout 90m
-
+        version: v1.16.2
+        args: release --skip-sign --snapshot --clean --skip-publish --timeout 90m
+      env:
+        GPG_FILE: "nogpg.key"

.github/workflows/vm-test.yaml

@@ -28,7 +28,7 @@ jobs:
         with:
           go-version-file: go.mod
       - name: Install tools
-        uses: aquaproj/aqua-installer@v2.0.2
+        uses: aquaproj/aqua-installer@v2.1.1
         with:
           aqua_version: v1.25.0
       - name: Run vm integration tests

.gitignore

@@ -38,3 +38,4 @@ dist
 
 # Signing
 gpg.key
+cmd/trivy/trivy

Dockerfile

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

Dockerfile.canary

@@ -1,10 +1,11 @@
-FROM alpine:3.17.3
+FROM alpine:3.18.0
 RUN apk --no-cache add ca-certificates git
 
 # binaries were created with GoReleaser
 # need to copy binaries from folder with correct architecture
 # example architecture folder: dist/trivy_canary_build_linux_arm64/trivy
+# GoReleaser adds _v* to the folder name, but only when GOARCH is amd64 
 ARG TARGETARCH
-COPY "dist/trivy_canary_build_linux_${TARGETARCH}/trivy" /usr/local/bin/trivy
+COPY "dist/trivy_canary_build_linux_${TARGETARCH}*/trivy" /usr/local/bin/trivy
 COPY contrib/*.tpl contrib/
 ENTRYPOINT ["trivy"]

README.md

@@ -103,11 +103,14 @@ trivy k8s --report summary cluster
 
 `tri` is pronounced like **tri**gger, `vy` is pronounced like en**vy**.
 
----
+## Community
 
 Trivy is an [Aqua Security][aquasec] open source project.  
 Learn about our open source work and portfolio [here][oss].  
 Contact us about any matter by opening a GitHub Discussion [here][discussions]
+Join our [Slack community][slack] to stay up to date with community efforts.
+
+Please ensure to abide by our [Code of Conduct][code-of-conduct] during all interactions.
 
 [test]: https://github.com/aquasecurity/trivy/actions/workflows/test.yaml
 [test-img]: https://github.com/aquasecurity/trivy/actions/workflows/test.yaml/badge.svg
@@ -122,6 +125,8 @@ Contact us about any matter by opening a GitHub Discussion [here][discussions]
 [homepage]: https://trivy.dev
 [docs]: https://aquasecurity.github.io/trivy
 [pronunciation]: #how-to-pronounce-the-name-trivy
+[slack]: https://slack.aquasec.com
+[code-of-conduct]: https://github.com/aquasecurity/community/blob/main/CODE_OF_CONDUCT.md
 
 [Installation]:https://aquasecurity.github.io/trivy/latest/getting-started/installation/
 [Ecosystem]: https://aquasecurity.github.io/trivy/latest/ecosystem/

aqua.yaml

@@ -3,7 +3,8 @@
 # https://aquaproj.github.io/
 registries:
 - type: standard
-  ref: v3.106.0 # renovate: depName=aquaproj/aqua-registry
+  ref: v3.157.0 # renovate: depName=aquaproj/aqua-registry
 packages:
-- name: tinygo-org/tinygo@v0.26.0
+- name: tinygo-org/tinygo@v0.27.0
+- name: WebAssembly/binaryen@version_112
 - name: magefile/mage@v1.14.0

ci/deploy-rpm.sh

@@ -2,6 +2,25 @@
 
 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_common_rpm_repo () {
+        rpm_path=$1
+
+        ARCHES=("x86_64" "aarch64")
+        for arch in ${ARCHES[@]}; do
+                prefix=$arch
+                if [ "$arch" == "x86_64" ]; then
+                        prefix="64bit"
+                elif [ "$arch" == "aarch64" ]; then
+                        prefix="ARM64"
+                fi
+
+                mkdir -p $rpm_path/$arch
+                cp ../dist/*${prefix}.rpm ${rpm_path}/$arch/
+                createrepo_c -u https://github.com/aquasecurity/trivy/releases/download/ --location-prefix="v"$TRIVY_VERSION --update $rpm_path/$arch
+                rm ${rpm_path}/$arch/*${prefix}.rpm
+        done
+}
+
 function create_rpm_repo () {
         version=$1
         rpm_path=rpm/releases/${version}/x86_64
@@ -18,6 +37,9 @@ echo "Create RPM releases for Trivy v$TRIVY_VERSION"
 
 cd trivy-repo
 
+echo "Processing common repository for RHEL/CentOS..."
+create_common_rpm_repo rpm/releases
+
 VERSIONS=(5 6 7 8 9)
 for version in ${VERSIONS[@]}; do
         echo "Processing RHEL/CentOS $version..."

contrib/install.sh

@@ -79,6 +79,7 @@ get_binaries() {
     openbsd/amd64) BINARIES="trivy" ;;
     openbsd/arm64) BINARIES="trivy" ;;
     openbsd/armv7) BINARIES="trivy" ;;
+    windows/amd64) BINARIES="trivy" ;;
     *)
       log_crit "platform $PLATFORM is not supported.  Make sure this script is up-to-date and file request at https://github.com/${PREFIX}/issues/new"
       exit 1
@@ -102,6 +103,9 @@ tag_to_version() {
 }
 adjust_format() {
   # change format (tar.gz or zip) based on OS
+  case ${OS} in
+    windows) FORMAT=zip ;;
+  esac
   true
 }
 adjust_os() {
@@ -127,6 +131,7 @@ adjust_arch() {
     386) ARCH=32bit ;;
     amd64) ARCH=64bit ;;
     arm) ARCH=ARM ;;
+    armv7) ARCH=ARM ;;
     arm64) ARCH=ARM64 ;;
     ppc64le) OS=PPC64LE ;;
     darwin) ARCH=macOS ;;

docs/community/contribute/discussion.md

@@ -0,0 +1,49 @@
+# Discussions
+Thank you for taking interest in contributing to Trivy!
+
+Trivy uses [GitHub Discussion](https://github.com/aquasecurity/trivy/discussions) for bug reports, feature requests, and questions.
+If maintainers decide to accept a new feature or confirm that it is a bug, they will close the discussion and create a [GitHub Issue](https://github.com/aquasecurity/trivy/issues) associated with that discussion.
+
+- Feel free to open discussions for any reason. When you open a new discussion, you'll have to select a discussion category as described below.
+- Please spend a small amount of time giving due diligence to the issue/discussion tracker. Your discussion might be a duplicate. If it is, please add your comment to the existing issue/discussion.
+- Remember that users might search for your issue/discussion in the future, so please give it a meaningful title to help others.
+- The issue should clearly explain the reason for opening, the proposal if you have any, and any relevant technical information.
+
+There are 4 categories:
+
+- 💡 [Ideas](https://github.com/aquasecurity/trivy/discussions/categories/ideas)
+    - Share ideas for new features
+- 🔎 [False Detection](https://github.com/aquasecurity/trivy/discussions/categories/false-detection)
+    - Report false positives/negatives
+- 🐛 [Bugs](https://github.com/aquasecurity/trivy/discussions/categories/bugs)
+    - Report something that is not working as expected
+- 🙏 [Q&A](https://github.com/aquasecurity/trivy/discussions/categories/q-a)
+    - Ask the community for help
+
+!!! note
+    If you find any false positives or false negatives, please make sure to report them under the "False Detection" category, not "Bugs".
+
+## False detection
+Trivy depends on [multiple data sources](https://aquasecurity.github.io/trivy/latest/docs/vulnerability/detection/data-source/).
+Sometime these databases contain mistakes.
+
+If Trivy can't detect any CVE-IDs or shows false positive result, at first please follow the next steps:
+
+1. Run Trivy with `-f json` that shows data sources.
+2. According to the shown data source, make sure that the security advisory in the data source is correct.
+
+If the data source is correct and Trivy shows wrong results, please raise an issue on Trivy.
+
+### GitHub Advisory Database
+Visit [here](https://github.com/advisories) and search CVE-ID.
+
+If you find a problem, it'll be nice to fix it: [How to contribute to a GitHub security advisory](https://github.blog/2022-02-22-github-advisory-database-now-open-to-community-contributions/)
+ 
+### GitLab Advisory Database
+Visit [here](https://advisories.gitlab.com/) and search CVE-ID.
+
+If you find a problem, it'll be nice to fix it: [Create an issue to GitLab Advisory Database](https://gitlab.com/gitlab-org/security-products/gemnasium-db/-/issues/new)
+ 
+### Red Hat CVE Database
+Visit [here](https://access.redhat.com/security/security-updates/?cwe=476#/cve) and search CVE-ID.
+

docs/community/contribute/issue.md

@@ -1,31 +1,4 @@
+# Issues
 Thank you for taking interest in contributing to Trivy!
 
-- Feel free to open issues for any reason. When you open a new issue, you'll have to select an issue kind: bug/feature/support and fill the required information based on the selected template.
-- Please spend a small amount of time giving due diligence to the issue tracker. Your issue might be a duplicate. If it is, please add your comment to the existing issue.
-- Remember that users might search for your issue in the future, so please give it a meaningful title to help others.
-- The issue should clearly explain the reason for opening, the proposal if you have any, and any relevant technical information.
-
-## Wrong detection
-Trivy depends on [multiple data sources](https://aquasecurity.github.io/trivy/latest/docs/vulnerability/detection/data-source/).
-Sometime these databases contain mistakes.
-
-If Trivy can't detect any CVE-IDs or shows false positive result, at first please follow the next steps:
-
-1. Run Trivy with `-f json` that shows data sources.
-2. According to the shown data source, make sure that the security advisory in the data source is correct.
-
-If the data source is correct and Trivy shows wrong results, please raise an issue on Trivy.
-
-### GitHub Advisory Database
-Visit [here](https://github.com/advisories) and search CVE-ID.
-
-If you find a problem, it'll be nice to fix it: [How to contribute to a GitHub security advisory](https://github.blog/2022-02-22-github-advisory-database-now-open-to-community-contributions/)
- 
-### GitLab Advisory Database
-Visit [here](https://advisories.gitlab.com/) and search CVE-ID.
-
-If you find a problem, it'll be nice to fix it: [Create an issue to GitLab Advisory Database](https://gitlab.com/gitlab-org/security-products/gemnasium-db/-/issues/new)
- 
-### Red Hat CVE Database
-Visit [here](https://access.redhat.com/security/security-updates/?cwe=476#/cve) and search CVE-ID.
-
+Trivy uses [GitHub Discussion](./discussion.md) for bug reports, feature requests, and questions.

docs/docs/advanced/air-gap.md

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

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

@@ -18,7 +18,7 @@ $ TRIVY_PASSWORD=YOUR_PASSWORD trivy image --username YOUR_USERNAME YOUR_PRIVATE
     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).
+For more information, please refer to [the documentation](../../references/configuration/config-file.md).
 
 It can handle multiple sets of credentials as well:
 

docs/docs/configuration/cache.md

@@ -1,4 +1,12 @@
 # Cache
+The cache directory includes 
+
+- [Vulnerability Database][trivy-db][^1]
+- [Java Index Database][trivy-java-db][^2]
+- [Misconfiguration Policies][misconf-policies][^3]
+- Cache of previous scans.
+ 
+The cache option is common to all scanners.
 
 ## Clear Caches
 The `--clear-cache` option removes caches.
@@ -58,4 +66,12 @@ $ 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
-```
+```
+
+[trivy-db]: ./db.md#vulnerability-database
+[trivy-java-db]: ./db.md#java-index-database
+[misconf-policies]: ../scanner/misconfiguration/policy/builtin.md
+
+[^1]: Downloaded when scanning for vulnerabilities
+[^2]: Downloaded when scanning `jar/war/par/ear` files
+[^3]: Downloaded when scanning for misconfigurations

docs/docs/configuration/db.md

@@ -1,6 +1,18 @@
-# Vulnerability DB
+# DB
 
-## Skip update of vulnerability DB
+|     Scanner      | Supported |
+|:----------------:|:---------:|
+|  Vulnerability   |     ✓     |
+| Misconfiguration |           |
+|      Secret      |           |
+|     License      |           |
+
+The vulnerability database and the Java index database are needed only for vulnerability scanning.
+See [here](../scanner/vulnerability/index.md) for the detail.
+
+## Vulnerability Database
+
+### Skip update of vulnerability DB
 If you want to skip downloading the vulnerability database, use the `--skip-db-update` option.
 
 ```
@@ -27,7 +39,7 @@ Total: 1 (UNKNOWN: 0, LOW: 0, MEDIUM: 1, HIGH: 0, CRITICAL: 0)
 
 </details>
 
-## Only download vulnerability database
+### Only download vulnerability database
 You can also ask `Trivy` to simply retrieve the vulnerability database.
 This is useful to initialize workers in Continuous Integration systems.
 
@@ -35,14 +47,14 @@ This is useful to initialize workers in Continuous Integration systems.
 $ trivy image --download-db-only
 ```
 
-## DB Repository
+### DB Repository
 `Trivy` could also download the vulnerability database from an external OCI registry by using `--db-repository` option.
 
 ```
 $ trivy image --db-repository registry.gitlab.com/gitlab-org/security-products/dependencies/trivy-db
 ```
 
-## Java Vulnerability DB
+## Java Index Database
 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.
 
@@ -51,3 +63,10 @@ Downloading the Java index DB from an external OCI registry can be done by using
 ```
 $ trivy image --java-db-repository registry.gitlab.com/gitlab-org/security-products/dependencies/trivy-java-db --download-java-db-only
 ```
+
+## Remove DBs
+The `--reset` flag removes all caches and databases.
+
+```
+$ trivy image --reset
+```

docs/docs/configuration/filtering.md

@@ -1,8 +1,18 @@
-# Filter Vulnerabilities
+# Filtering
+Trivy provides various methods for filtering the results.
+
 
 ## Hide Unfixed Vulnerabilities
 
-By default, `Trivy` also detects unpatched/unfixed vulnerabilities. This means you can't fix these vulnerabilities even if you update all packages.
+|     Scanner      | Supported |
+|:----------------:|:---------:|
+|  Vulnerability   |     ✓     |
+| Misconfiguration |           |
+|      Secret      |           |
+|     License      |           |
+
+By default, `Trivy` also detects unpatched/unfixed vulnerabilities.
+This means you can't fix these vulnerabilities even if you update all packages.
 If you would like to ignore them, use the `--ignore-unfixed` option.
 
 ```bash
@@ -50,6 +60,13 @@ Total: 4730 (UNKNOWN: 1, LOW: 145, MEDIUM: 3487, HIGH: 1014, CRITICAL: 83)
 
 ## By Severity
 
+|     Scanner      | Supported |
+|:----------------:|:---------:|
+|  Vulnerability   |     ✓     |
+| Misconfiguration |     ✓     |
+|      Secret      |     ✓     |
+|     License      |     ✓     |
+
 Use `--severity` option.
 
 ```bash
@@ -113,7 +130,69 @@ Total: 1785 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 1680, CRITICAL: 105)
 
 </details>
 
-## By Vulnerability IDs
+```bash
+trivy conf --severity HIGH,CRITICAL examples/misconf/mixed
+```
+
+<details>
+<summary>Result</summary>
+
+```shell
+2022-05-16T13:50:42.718+0100	INFO	Detected config files: 3
+
+Dockerfile (dockerfile)
+=======================
+Tests: 17 (SUCCESSES: 16, FAILURES: 1, EXCEPTIONS: 0)
+Failures: 1 (HIGH: 1, CRITICAL: 0)
+
+HIGH: Last USER command in Dockerfile should not be 'root'
+═══════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════
+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
+───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
+ Dockerfile:3
+───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
+   3 [ USER root
+───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
+
+
+
+deployment.yaml (kubernetes)
+============================
+Tests: 8 (SUCCESSES: 8, FAILURES: 0, EXCEPTIONS: 0)
+Failures: 0 (HIGH: 0, CRITICAL: 0)
+
+
+main.tf (terraform)
+===================
+Tests: 1 (SUCCESSES: 0, FAILURES: 1, EXCEPTIONS: 0)
+Failures: 1 (HIGH: 0, CRITICAL: 1)
+
+CRITICAL: Classic resources should not be used.
+═══════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════
+AWS Classic resources run in a shared environment with infrastructure owned by other AWS customers. You should run
+resources in a VPC instead.
+
+See https://avd.aquasec.com/misconfig/avd-aws-0081
+───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
+ main.tf:2-4
+───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
+   2 ┌ resource "aws_db_security_group" "sg" {
+   3 │
+   4 └ }
+───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
+```
+</details>
+
+## By Finding IDs
+
+|     Scanner      | Supported |
+|:----------------:|:---------:|
+|  Vulnerability   |     ✓     |
+| Misconfiguration |     ✓     |
+|      Secret      |     ✓     |
+|     License      |           |
 
 Use `.trivyignore`.
 
@@ -128,6 +207,15 @@ CVE-2019-14697 exp:2023-01-01
 # No impact in our settings
 CVE-2019-1543
 
+# Ignore misconfigurations
+AVD-DS-0002
+
+# Ignore secrets
+generic-unwanted-rule
+aws-account-id
+```
+
+```bash
 $ trivy image python:3.4-alpine3.9
 ```
 
@@ -146,7 +234,14 @@ Total: 0 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 0, CRITICAL: 0)
 
 </details>
 
-## By Type
+## By Vulnerability Target
+|     Scanner      | Supported |
+|:----------------:|:---------:|
+|  Vulnerability   |     ✓     |
+| Misconfiguration |           |
+|      Secret      |           |
+|     License      |           |
+
 Use `--vuln-type` option.
 
 ```bash
@@ -154,6 +249,7 @@ $ trivy image --vuln-type os ruby:2.4.0
 ```
 
 Available values:
+
 - library
 - os
 
@@ -169,7 +265,8 @@ Available values:
 2019-05-22T19:36:53.406+0200    INFO    Detecting pipenv vulnerabilities...
 
 ruby:2.4.0 (debian 8.7)
-Total: 4751 (UNKNOWN: 1, LOW: 150, MEDIUM: 3504, HIGH: 1013, CRITICAL: 83)
+=======================
+Total: 7 (UNKNOWN: 0, LOW: 1, MEDIUM: 1, HIGH: 3, CRITICAL: 2)
 
 +---------+------------------+----------+-------------------+---------------+----------------------------------+
 | LIBRARY | VULNERABILITY ID | SEVERITY | INSTALLED VERSION | FIXED VERSION |              TITLE               |
@@ -180,23 +277,6 @@ Total: 4751 (UNKNOWN: 1, LOW: 150, MEDIUM: 3504, HIGH: 1013, CRITICAL: 83)
 |         | CVE-2018-16839   | HIGH     |                   | 7.61.1-r1     | curl: Integer overflow leading   |
 |         |                  |          |                   |               | to heap-based buffer overflow in |
 |         |                  |          |                   |               | Curl_sasl_create_plain_message() |
-+         +------------------+          +                   +---------------+----------------------------------+
-|         | CVE-2019-3822    |          |                   | 7.61.1-r2     | curl: NTLMv2 type-3 header       |
-|         |                  |          |                   |               | stack buffer overflow            |
-+         +------------------+          +                   +---------------+----------------------------------+
-|         | CVE-2018-16840   |          |                   | 7.61.1-r1     | curl: Use-after-free when        |
-|         |                  |          |                   |               | closing "easy" handle in         |
-|         |                  |          |                   |               | Curl_close()                     |
-+         +------------------+----------+                   +---------------+----------------------------------+
-|         | CVE-2019-3823    | MEDIUM   |                   | 7.61.1-r2     | curl: SMTP end-of-response       |
-|         |                  |          |                   |               | out-of-bounds read               |
-+         +------------------+          +                   +               +----------------------------------+
-|         | CVE-2018-16890   |          |                   |               | curl: NTLM type-2 heap           |
-|         |                  |          |                   |               | out-of-bounds buffer read        |
-+         +------------------+          +                   +---------------+----------------------------------+
-|         | CVE-2018-16842   |          |                   | 7.61.1-r1     | curl: Heap-based buffer          |
-|         |                  |          |                   |               | over-read in the curl tool       |
-|         |                  |          |                   |               | warning formatting               |
 +---------+------------------+----------+-------------------+---------------+----------------------------------+
 | git     | CVE-2018-17456   | HIGH     | 2.15.2-r0         | 2.15.3-r0     | git: arbitrary code execution    |
 |         |                  |          |                   |               | via .gitmodules                  |
@@ -208,67 +288,6 @@ Total: 4751 (UNKNOWN: 1, LOW: 150, MEDIUM: 3504, HIGH: 1013, CRITICAL: 83)
 | libssh2 | CVE-2019-3855    | CRITICAL | 1.8.0-r2          | 1.8.1-r0      | libssh2: Integer overflow in     |
 |         |                  |          |                   |               | transport read resulting in      |
 |         |                  |          |                   |               | out of bounds write...           |
-+         +------------------+----------+                   +               +----------------------------------+
-|         | CVE-2019-3861    | MEDIUM   |                   |               | libssh2: Out-of-bounds reads     |
-|         |                  |          |                   |               | with specially crafted SSH       |
-|         |                  |          |                   |               | packets                          |
-+         +------------------+          +                   +               +----------------------------------+
-|         | CVE-2019-3857    |          |                   |               | libssh2: Integer overflow in     |
-|         |                  |          |                   |               | SSH packet processing channel    |
-|         |                  |          |                   |               | resulting in out of...           |
-+         +------------------+          +                   +               +----------------------------------+
-|         | CVE-2019-3856    |          |                   |               | libssh2: Integer overflow in     |
-|         |                  |          |                   |               | keyboard interactive handling    |
-|         |                  |          |                   |               | resulting in out of bounds...    |
-+         +------------------+          +                   +               +----------------------------------+
-|         | CVE-2019-3863    |          |                   |               | libssh2: Integer overflow        |
-|         |                  |          |                   |               | in user authenticate             |
-|         |                  |          |                   |               | keyboard interactive allows      |
-|         |                  |          |                   |               | out-of-bounds writes             |
-+         +------------------+          +                   +               +----------------------------------+
-|         | CVE-2019-3862    |          |                   |               | libssh2: Out-of-bounds memory    |
-|         |                  |          |                   |               | comparison with specially        |
-|         |                  |          |                   |               | crafted message channel          |
-|         |                  |          |                   |               | request                          |
-+         +------------------+          +                   +               +----------------------------------+
-|         | CVE-2019-3860    |          |                   |               | libssh2: Out-of-bounds reads     |
-|         |                  |          |                   |               | with specially crafted SFTP      |
-|         |                  |          |                   |               | packets                          |
-+         +------------------+          +                   +               +----------------------------------+
-|         | CVE-2019-3858    |          |                   |               | libssh2: Zero-byte allocation    |
-|         |                  |          |                   |               | with a specially crafted SFTP    |
-|         |                  |          |                   |               | packed leading to an...          |
-+         +------------------+          +                   +               +----------------------------------+
-|         | CVE-2019-3859    |          |                   |               | libssh2: Unchecked use of        |
-|         |                  |          |                   |               | _libssh2_packet_require and      |
-|         |                  |          |                   |               | _libssh2_packet_requirev         |
-|         |                  |          |                   |               | resulting in out-of-bounds       |
-|         |                  |          |                   |               | read                             |
-+---------+------------------+          +-------------------+---------------+----------------------------------+
-| libxml2 | CVE-2018-14404   |          | 2.9.7-r0          | 2.9.8-r1      | libxml2: NULL pointer            |
-|         |                  |          |                   |               | dereference in                   |
-|         |                  |          |                   |               | xpath.c:xmlXPathCompOpEval()     |
-|         |                  |          |                   |               | can allow attackers to cause     |
-|         |                  |          |                   |               | a...                             |
-+         +------------------+          +                   +               +----------------------------------+
-|         | CVE-2018-14567   |          |                   |               | libxml2: Infinite loop when      |
-|         |                  |          |                   |               | --with-lzma is used allows for   |
-|         |                  |          |                   |               | denial of service...             |
-+         +------------------+----------+                   +               +----------------------------------+
-|         | CVE-2018-9251    | LOW      |                   |               | libxml2: infinite loop in        |
-|         |                  |          |                   |               | xz_decomp function in xzlib.c    |
-+---------+------------------+----------+-------------------+---------------+----------------------------------+
-| openssh | CVE-2019-6109    | MEDIUM   | 7.5_p1-r9         | 7.5_p1-r10    | openssh: Missing character       |
-|         |                  |          |                   |               | encoding in progress display     |
-|         |                  |          |                   |               | allows for spoofing of scp...    |
-+         +------------------+          +                   +               +----------------------------------+
-|         | CVE-2019-6111    |          |                   |               | openssh: Improper validation     |
-|         |                  |          |                   |               | of object names allows           |
-|         |                  |          |                   |               | malicious server to overwrite    |
-|         |                  |          |                   |               | files...                         |
-+         +------------------+----------+                   +               +----------------------------------+
-|         | CVE-2018-20685   | LOW      |                   |               | openssh: scp client improper     |
-|         |                  |          |                   |               | directory name validation        |
 +---------+------------------+----------+-------------------+---------------+----------------------------------+
 | sqlite  | CVE-2018-20346   | MEDIUM   | 3.21.0-r1         | 3.25.3-r0     | CVE-2018-20505 CVE-2018-20506    |
 |         |                  |          |                   |               | sqlite: Multiple flaws in        |
@@ -283,13 +302,20 @@ Total: 4751 (UNKNOWN: 1, LOW: 150, MEDIUM: 3504, HIGH: 1013, CRITICAL: 83)
 
 </details>
 
-
 ## By Open Policy Agent
 
+|     Scanner      | Supported |
+|:----------------:|:---------:|
+|  Vulnerability   |     ✓     |
+| Misconfiguration |     ✓     |
+|      Secret      |           |
+|     License      |           |
+
 !!! warning "EXPERIMENTAL"
     This feature might change without preserving backwards compatibility.
 
-Trivy supports Open Policy Agent (OPA) to filter vulnerabilities. You can specify a Rego file with `--ignore-policy` option.
+Trivy supports Open Policy Agent (OPA) to filter vulnerabilities.
+You can specify a Rego file with `--ignore-policy` option.
 
 The Rego package name must be `trivy` and it must include a rule called `ignore` which determines if each individual vulnerability should be excluded (ignore=true) or not (ignore=false). In the policy, each vulnerability will be available for inspection as the `input` variable. The structure of each vulnerability input is the same as for the Trivy JSON output.  
 There is a built-in Rego library with helper functions that you can import into your policy using: `import data.lib.trivy`. For more info about the helper functions, look at the library [here][helper]
@@ -357,3 +383,28 @@ Total: 9 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 4, CRITICAL: 5)
 
 [helper]: https://github.com/aquasecurity/trivy/tree/{{ git.tag }}/pkg/result/module.go
 [policy]: https://github.com/aquasecurity/trivy/tree/{{ git.tag }}/contrib/example_policy
+
+## By Inline Comments
+
+|     Scanner      | Supported |
+|:----------------:|:---------:|
+|  Vulnerability   |           |
+| Misconfiguration |     ✓     |
+|      Secret      |           |
+|     License      |           |
+
+Some configuration file formats (e.g. Terraform) support inline comments.
+
+In cases where trivy can detect comments of a specific format immediately adjacent to resource definitions, it is possible to filter/ignore findings from a single point of resource definition (in contrast to `.trivyignore`, which has a directory-wide scope on all of the files scanned).
+
+The format for these comments is `trivy:ignore:<Vulnerability ID>` immediately following the format-specific line-comment token.
+
+For example, to filter a Vulnerability ID "AVD-GCP-0051" in a Terraform HCL file:
+
+```terraform
+#trivy:ignore:AVD-GCP-0051
+resource "google_container_cluster" "one_off_test" {
+  name     = var.cluster_name
+  location = var.region
+}
+```

docs/docs/configuration/index.md

@@ -0,0 +1,31 @@
+# Configuration
+Trivy can be configured using the following ways. Each item takes precedence over the item below it:
+
+- CLI flags
+- Environment variables
+- Configuration file
+
+## CLI Flags
+You can view the list of available flags using the `--help` option.
+For more details, please refer to [the CLI reference](../references/configuration/cli/trivy.md).
+
+## Environment Variables
+Trivy can be customized by environment variables.
+The environment variable key is the flag name converted by the following procedure.
+
+- Add `TRIVY_` prefix
+- Make it all uppercase
+- Replace `-` with `_`
+
+For example,
+
+- `--debug` => `TRIVY_DEBUG`
+- `--cache-dir` => `TRIVY_CACHE_DIR`
+
+```
+$ TRIVY_DEBUG=true TRIVY_SEVERITY=CRITICAL trivy image alpine:3.15
+```
+
+## Configuration File
+By default, Trivy reads the `trivy.yaml` file.
+For more details, please refer to [the page](../references/configuration/config-file.md).

docs/docs/configuration/others.md

@@ -1,59 +1,31 @@
 # Others
 
-## Skip Files
-Trivy traversals directories and looks for all lock files by default.
-If your image contains lock files which are not maintained by you, you can skip the file.
+## Enable/Disable Scanners
+You can enable/disable scanners with the `--scanners` flag.
 
+Supported values:
+
+- vuln
+- config
+- secret
+- license
+ 
+For example, container image scanning enables vulnerability and secret scanners by default.
+If you don't need secret scanning, it can be disabled.
+
+``` shell
+$ trivy image --scanners vuln alpine:3.15
 ```
-$ trivy image --skip-files "/Gemfile.lock" --skip-files "/var/lib/gems/2.5.0/gems/http_parser.rb-0.6.0/Gemfile.lock" quay.io/fluentd_elasticsearch/fluentd:v2.9.0
-```
-
-It's possible to specify globs as part of the value.
-
-```bash
-$ trivy image --skip-files "./testdata/*/bar" .
-```
-
-Will skip any file named `bar` in the subdirectories of testdata.
-
-## Skip Directories
-Trivy traversals directories and look for all lock files by default.
-If your image contains lock files which are not maintained by you, you can skip traversal in the specific directory.
-
-```
-$ trivy image --skip-dirs /var/lib/gems/2.5.0/gems/fluent-plugin-detect-exceptions-0.0.13 --skip-dirs "/var/lib/gems/2.5.0/gems/http_parser.rb-0.6.0" quay.io/fluentd_elasticsearch/fluentd:v2.9.0
-```
-
-It's possible to specify globs as part of the value.
-
-```bash
-$ trivy image --skip-dirs "./testdata/*" .
-```
-
-Will skip all subdirectories of the testdata directory.
-
-!!! tip
-    Glob patters work with any trivy subcommand (image, config, etc.) and can be specified to skip both directories (with `--skip-dirs`) and files (with `--skip-files`).
-
-
-## File patterns
-When a directory is given as an input, Trivy will recursively look for and test all files based on file patterns.
-The default file patterns are [here](../../misconfiguration/custom/index.md).
-
-In addition to the default file patterns, the `--file-patterns` option takes regexp patterns to look for your files.
-For example, it may be useful when your file name of Dockerfile doesn't match the default patterns.
-
-This can be repeated for specifying multiple file patterns.
-
-A file pattern contains the analyzer it is used for, and the pattern itself, joined by a semicolon. For example:
-```
---file-patterns "dockerfile:.*.docker" --file-patterns "yaml:deployment" --file-patterns "pip:requirements-.*\.txt"
-```
-
-For more details, see [an example](https://github.com/aquasecurity/trivy/tree/{{ git.commit }}/examples/misconf/file-patterns)
 
 ## Exit Code
-By default, `Trivy` exits with code 0 even when vulnerabilities are detected.
+|     Scanner      | Supported |
+|:----------------:|:---------:|
+|  Vulnerability   |     ✓     |
+| Misconfiguration |     ✓     |
+|      Secret      |     ✓     |
+|     License      |     ✓     |
+
+By default, `Trivy` exits with code 0 even when security issues are detected.
 Use the `--exit-code` option if you want to exit with a non-zero exit code.
 
 ```
@@ -89,6 +61,13 @@ $ trivy image --exit-code 1 --severity CRITICAL ruby:2.4.0
 ```
 
 ## Exit on EOL
+|     Scanner      | Supported |
+|:----------------:|:---------:|
+|  Vulnerability   |     ✓     |
+| Misconfiguration |           |
+|      Secret      |           |
+|     License      |           |
+
 Sometimes you may surprisingly get 0 vulnerabilities in an old image:
 
 - Enabling `--ignore-unfixed` option while all packages have no fixed versions.
@@ -138,20 +117,3 @@ The following example will fail when a critical vulnerability is found or the OS
 ```
 $ trivy image --exit-code 1 --exit-on-eol 1 --severity CRITICAL alpine:3.16.3
 ```
-
-## Reset
-The `--reset` option removes all caches and database.
-After this, it takes a long time as the vulnerability database needs to be rebuilt locally.
-
-```
-$ trivy image --reset
-```
-
-<details>
-<summary>Result</summary>
-
-```
-2019-05-16T13:05:31.935+0900    INFO    Resetting...
-```
-
-</details>

docs/docs/configuration/reporting.md

@@ -1,12 +1,35 @@
-# Report Formats
+# Reporting
 
-## Table (Default)
+## Supported Formats
+Trivy supports the following formats:
+
+- Table
+- JSON
+- [SARIF](https://docs.github.com/en/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning)
+- Template
+- SBOM
+
+### Table (Default)
+
+|     Scanner      | Supported |
+|:----------------:|:---------:|
+|  Vulnerability   |     ✓     |
+| Misconfiguration |     ✓     |
+|      Secret      |     ✓     |
+|     License      |     ✓     |
 
 ```
 $ trivy image -f table golang:1.12-alpine
 ```
 
-### Show origins of vulnerable dependencies
+#### Show origins of vulnerable dependencies
+
+|     Scanner      | Supported |
+|:----------------:|:---------:|
+|  Vulnerability   |     ✓     |
+| Misconfiguration |           |
+|      Secret      |           |
+|     License      |           |
 
 !!! warning "EXPERIMENTAL"
     This feature might change without preserving backwards compatibility.
@@ -83,15 +106,19 @@ Also, **glob-parent@3.1.0** with some vulnerabilities is included through chain
 
 Then, you can try to update **axios@0.21.4** and **cra-append-sw@2.7.0** to resolve vulnerabilities in **follow-redirects@1.14.6** and **glob-parent@3.1.0**.
 
-## JSON
+### JSON
+
+|     Scanner      | Supported |
+|:----------------:|:---------:|
+|  Vulnerability   |     ✓     |
+| Misconfiguration |     ✓     |
+|      Secret      |     ✓     |
+|     License      |     ✓     |
 
 ```
 $ trivy image -f json -o results.json golang:1.12-alpine
 ```
 
-!!! caution
-    v0.20.0 changes the JSON schema. For more details, see [here][new-json].
-
 <details>
 <summary>Result</summary>
 
@@ -213,8 +240,15 @@ $ trivy image -f json -o results.json golang:1.12-alpine
 
 `VulnerabilityID`, `PkgName`, `InstalledVersion`, and `Severity` in `Vulnerabilities` are always filled with values, but other fields might be empty.
 
-## SARIF
-[Sarif][sarif] can be generated with the `--format sarif` option.
+### SARIF
+|     Scanner      | Supported |
+|:----------------:|:---------:|
+|  Vulnerability   |     ✓     |
+| Misconfiguration |     ✓     |
+|      Secret      |     ✓     |
+|     License      |           |
+
+[SARIF][sarif] can be generated with the `--format sarif` flag.
 
 ```
 $ trivy image --format sarif -o report.sarif  golang:1.12-alpine
@@ -222,9 +256,16 @@ $ trivy image --format sarif -o report.sarif  golang:1.12-alpine
 
 This SARIF file can be uploaded to GitHub code scanning results, and there is a [Trivy GitHub Action][action] for automating this process.
 
-## Template
+### Template
 
-### Custom Template
+|     Scanner      | Supported |
+|:----------------:|:---------:|
+|  Vulnerability   |     ✓     |
+| Misconfiguration |     ✓     |
+|      Secret      |     ✓     |
+|     License      |     ✓     |
+
+#### Custom Template
 
 {% raw %}
 ```
@@ -261,27 +302,47 @@ Critical: 0, High: 2
 
 For other features of sprig, see the official [sprig][sprig] documentation.
 
-### Load templates from a file
+#### Load templates from a file
 You can load templates from a file prefixing the template path with an @.
 
 ```
 $ trivy image --format template --template "@/path/to/template" golang:1.12-alpine
 ```
 
-### Default Templates
+#### Default Templates
 
 If Trivy is installed using rpm then default templates can be found at `/usr/local/share/trivy/templates`.
 
-#### XML
+##### JUnit
+|     Scanner      | Supported |
+|:----------------:|:---------:|
+|  Vulnerability   |     ✓     |
+| Misconfiguration |     ✓     |
+|      Secret      |           |
+|     License      |           |
+
 In the following example using the template `junit.tpl` XML can be generated.
 ```
 $ trivy image --format template --template "@contrib/junit.tpl" -o junit-report.xml  golang:1.12-alpine
 ```
 
-#### ASFF
+##### ASFF
+|     Scanner      | Supported |
+|:----------------:|:---------:|
+|  Vulnerability   |     ✓     |
+| Misconfiguration |     ✓     |
+|      Secret      |     ✓     |
+|     License      |           |
+
 Trivy also supports an [ASFF template for reporting findings to AWS Security Hub][asff]
 
-#### HTML
+##### HTML
+|     Scanner      | Supported |
+|:----------------:|:---------:|
+|  Vulnerability   |     ✓     |
+| Misconfiguration |     ✓     |
+|      Secret      |           |
+|     License      |           |
 
 ```
 $ trivy image --format template --template "@contrib/html.tpl" -o report.html golang:1.12-alpine
@@ -293,9 +354,36 @@ The following example shows use of default HTML template when Trivy is installed
 $ trivy image --format template --template "@/usr/local/share/trivy/templates/html.tpl" -o report.html golang:1.12-alpine
 ```
 
+### SBOM
+See [here](../supply-chain/sbom.md) for details.
+
+## Converting
+To generate multiple reports, you can generate the JSON report first and convert it to other formats with the `convert` subcommand.
+
+```shell
+$ trivy image --format json -o result.json --list-all-pkgs debian:11
+$ trivy convert --format cyclonedx --output result.cdx result.json
+```
+
+!!! note
+    Please note that if you want to convert to a format that requires a list of packages, 
+    such as SBOM, you need to add the `--list-all-pkgs` flag when outputting in JSON.
+
+[Filtering options](./filtering.md) such as `--severity` are also available with `convert`.
+
+```shell
+# Output all severities in JSON
+$ trivy image --format json -o result.json --list-all-pkgs debian:11
+
+# Output only critical issues in table format
+$ trivy convert --format table --severity CRITICAL result.json
+```
+
+!!! note
+    JSON reports from "trivy aws" and "trivy k8s" are not yet supported.
+
 [cargo-auditable]: https://github.com/rust-secure-code/cargo-auditable/
-[new-json]: https://github.com/aquasecurity/trivy/discussions/1050
 [action]: https://github.com/aquasecurity/trivy-action
-[asff]: ../../../tutorials/integrations/aws-security-hub.md
+[asff]: ../../tutorials/integrations/aws-security-hub.md
 [sarif]: https://docs.github.com/en/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-results-from-code-scanning
 [sprig]: http://masterminds.github.io/sprig/

docs/docs/configuration/skipping.md

@@ -0,0 +1,85 @@
+# Skipping Files and Directories
+
+This section details ways to specify the files and directories that Trivy should not scan.
+
+## Skip Files
+|     Scanner      | Supported |
+|:----------------:|:---------:|
+|  Vulnerability   |     ✓     |
+| Misconfiguration |     ✓     |
+|      Secret      |     ✓     |
+|     License      |     ✓     |
+
+By default, Trivy traverses directories and searches for all necessary files for scanning.
+You can skip files that you don't maintain using the `--skip-files` flag.
+
+```
+$ trivy image --skip-files "/Gemfile.lock" --skip-files "/var/lib/gems/2.5.0/gems/http_parser.rb-0.6.0/Gemfile.lock" quay.io/fluentd_elasticsearch/fluentd:v2.9.0
+```
+
+It's possible to specify globs as part of the value.
+
+```bash
+$ trivy image --skip-files "./testdata/*/bar" .
+```
+
+Will skip any file named `bar` in the subdirectories of testdata.
+
+## Skip Directories
+|     Scanner      | Supported |
+|:----------------:|:---------:|
+|  Vulnerability   |     ✓     |
+| Misconfiguration |     ✓     |
+|      Secret      |     ✓     |
+|     License      |     ✓     |
+
+By default, Trivy traverses directories and searches for all necessary files for scanning.
+You can skip directories that you don't maintain using the `--skip-dirs` flag.
+
+```
+$ trivy image --skip-dirs /var/lib/gems/2.5.0/gems/fluent-plugin-detect-exceptions-0.0.13 --skip-dirs "/var/lib/gems/2.5.0/gems/http_parser.rb-0.6.0" quay.io/fluentd_elasticsearch/fluentd:v2.9.0
+```
+
+It's possible to specify globs as part of the value.
+
+```bash
+$ trivy image --skip-dirs "./testdata/*" .
+```
+
+Will skip all subdirectories of the testdata directory.
+
+!!! tip
+    Glob patterns work with any trivy subcommand (image, config, etc.) and can be specified to skip both directories (with `--skip-dirs`) and files (with `--skip-files`).
+
+
+### Advanced globbing
+Trivy also supports the [globstar](https://www.gnu.org/savannah-checkouts/gnu/bash/manual/bash.html#Pattern-Matching) pattern matching. 
+
+```bash
+$ trivy image --skip-files "**/foo" image:tag
+```
+
+Will skip the file `foo` that happens to be nested under any parent(s). 
+
+## File patterns
+|     Scanner      | Supported |
+|:----------------:|:---------:|
+|  Vulnerability   |     ✓     |
+| Misconfiguration |     ✓     |
+|      Secret      |           |
+|     License      |           |
+
+When a directory is given as an input, Trivy will recursively look for and test all files based on file patterns.
+The default file patterns are [here](../scanner/misconfiguration/custom/index.md).
+
+In addition to the default file patterns, the `--file-patterns` option takes regexp patterns to look for your files.
+For example, it may be useful when your file name of Dockerfile doesn't match the default patterns.
+
+This can be repeated for specifying multiple file patterns.
+
+A file pattern contains the analyzer it is used for, and the pattern itself, joined by a semicolon. For example:
+```
+--file-patterns "dockerfile:.*.docker" --file-patterns "kubernetes:*.tpl" --file-patterns "pip:requirements-.*\.txt"
+```
+
+The prefixes are listed [here](https://github.com/aquasecurity/trivy/tree/{{ git.commit }}/pkg/fanal/analyzer/const.go)

docs/docs/misconfiguration/custom/examples.md

@@ -1,296 +0,0 @@
-# Examples
-
-## Custom Policy
-### Kubernetes
-See [here][k8s].
-
-The custom policy is defined in `user.kubernetes.ID001` package.
-You need to pass the package prefix you want to evaluate through `--namespaces` option.
-In this case, the package prefix should be `user`, `user.kubernetes`, or `user.kubernetes.ID001`.
-
-### Dockerfile
-See [here][dockerfile].
-
-The input will be a dictionary of stages.
-
-#### Single Stage
-
-??? example
-    Dockerfile
-    ```dockerfile
-    FROM foo
-    COPY . /
-    RUN echo hello
-    ```
-
-    Rego Input
-    ```json
-    {
-        "stages": {
-            "foo": [
-                {
-                    "Cmd": "from",
-                    "EndLine": 1,
-                    "Flags": [],
-                    "JSON": false,
-                    "Original": "FROM foo",
-                    "Stage": 0,
-                    "StartLine": 1,
-                    "SubCmd": "",
-                    "Value": [
-                        "foo"
-                    ]
-                },
-                {
-                    "Cmd": "copy",
-                    "EndLine": 2,
-                    "Flags": [],
-                    "JSON": false,
-                    "Original": "COPY . /",
-                    "Stage": 0,
-                    "StartLine": 2,
-                    "SubCmd": "",
-                    "Value": [
-                        ".",
-                        "/"
-                    ]
-                },
-                {
-                    "Cmd": "run",
-                    "EndLine": 3,
-                    "Flags": [],
-                    "JSON": false,
-                    "Original": "RUN echo hello",
-                    "Stage": 0,
-                    "StartLine": 3,
-                    "SubCmd": "",
-                    "Value": [
-                        "echo hello"
-                    ]
-                }
-            ]
-        }
-    }
-    ```
-
-#### Multi Stage
-
-??? example
-    Dockerfile
-    ```dockerfile
-    FROM golang:1.16 AS builder
-    WORKDIR /go/src/github.com/alexellis/href-counter/
-    RUN go get -d -v golang.org/x/net/html
-    COPY app.go .
-    RUN CGO_ENABLED=0 GOOS=linux go build -a -installsuffix cgo -o app .
-    
-    FROM alpine:latest
-    RUN apk --no-cache add ca-certificates \
-    && apk add --no-cache bash
-    WORKDIR /root/
-    COPY --from=builder /go/src/github.com/alexellis/href-counter/app .
-    CMD ["./app"]
-    ```
-
-    Rego Input
-    ```json
-    {
-        "stages": {
-            "alpine:latest": [
-                {
-                    "Cmd": "from",
-                    "EndLine": 7,
-                    "Flags": [],
-                    "JSON": false,
-                    "Original": "FROM alpine:latest",
-                    "Stage": 1,
-                    "StartLine": 7,
-                    "SubCmd": "",
-                    "Value": [
-                        "alpine:latest"
-                    ]
-                },
-                {
-                    "Cmd": "run",
-                    "EndLine": 9,
-                    "Flags": [],
-                    "JSON": false,
-                    "Original": "RUN apk --no-cache add ca-certificates     \u0026\u0026 apk add --no-cache bash",
-                    "Stage": 1,
-                    "StartLine": 8,
-                    "SubCmd": "",
-                    "Value": [
-                        "apk --no-cache add ca-certificates     \u0026\u0026 apk add --no-cache bash"
-                    ]
-                },
-                {
-                    "Cmd": "workdir",
-                    "EndLine": 10,
-                    "Flags": [],
-                    "JSON": false,
-                    "Original": "WORKDIR /root/",
-                    "Stage": 1,
-                    "StartLine": 10,
-                    "SubCmd": "",
-                    "Value": [
-                        "/root/"
-                    ]
-                },
-                {
-                    "Cmd": "copy",
-                    "EndLine": 11,
-                    "Flags": [
-                        "--from=builder"
-                    ],
-                    "JSON": false,
-                    "Original": "COPY --from=builder /go/src/github.com/alexellis/href-counter/app .",
-                    "Stage": 1,
-                    "StartLine": 11,
-                    "SubCmd": "",
-                    "Value": [
-                        "/go/src/github.com/alexellis/href-counter/app",
-                        "."
-                    ]
-                },
-                {
-                    "Cmd": "cmd",
-                    "EndLine": 12,
-                    "Flags": [],
-                    "JSON": true,
-                    "Original": "CMD [\"./app\"]",
-                    "Stage": 1,
-                    "StartLine": 12,
-                    "SubCmd": "",
-                    "Value": [
-                        "./app"
-                    ]
-                }
-            ],
-            "golang:1.16 AS builder": [
-                {
-                    "Cmd": "from",
-                    "EndLine": 1,
-                    "Flags": [],
-                    "JSON": false,
-                    "Original": "FROM golang:1.16 AS builder",
-                    "Stage": 0,
-                    "StartLine": 1,
-                    "SubCmd": "",
-                    "Value": [
-                        "golang:1.16",
-                        "AS",
-                        "builder"
-                    ]
-                },
-                {
-                    "Cmd": "workdir",
-                    "EndLine": 2,
-                    "Flags": [],
-                    "JSON": false,
-                    "Original": "WORKDIR /go/src/github.com/alexellis/href-counter/",
-                    "Stage": 0,
-                    "StartLine": 2,
-                    "SubCmd": "",
-                    "Value": [
-                        "/go/src/github.com/alexellis/href-counter/"
-                    ]
-                    },
-                {
-                    "Cmd": "run",
-                    "EndLine": 3,
-                    "Flags": [],
-                    "JSON": false,
-                    "Original": "RUN go get -d -v golang.org/x/net/html",
-                    "Stage": 0,
-                    "StartLine": 3,
-                    "SubCmd": "",
-                    "Value": [
-                        "go get -d -v golang.org/x/net/html"
-                    ]
-                },
-                {
-                    "Cmd": "copy",
-                    "EndLine": 4,
-                    "Flags": [],
-                    "JSON": false,
-                    "Original": "COPY app.go .",
-                    "Stage": 0,
-                    "StartLine": 4,
-                    "SubCmd": "",
-                    "Value": [
-                        "app.go",
-                        "."
-                    ]
-                },
-                {
-                    "Cmd": "run",
-                    "EndLine": 5,
-                    "Flags": [],
-                    "JSON": false,
-                    "Original": "RUN CGO_ENABLED=0 GOOS=linux go build -a -installsuffix cgo -o app .",
-                    "Stage": 0,
-                    "StartLine": 5,
-                    "SubCmd": "",
-                    "Value": [
-                        "CGO_ENABLED=0 GOOS=linux go build -a -installsuffix cgo -o app ."
-                    ]
-                }
-            ]
-        }
-    }
-    ```
-
-### Docker Compose
-See [here][compose].
-
-Docker Compose uses YAML format for configurations. You can apply your Rego policies to `docker-compose.yml`.
-
-### HCL
-See [here][hcl].
-
-Trivy parses HCL files and converts into structured data.
-
-!!! warning
-    Terraform HCL files are not supported yet.
-
-### Terraform Plan
-See [here][tfplan].
-
-Use the command [terraform show][terraform-show] to convert the Terraform plan into JSON so that OPA can read the plan.
-
-```bash
-$ terraform init
-$ terraform plan --out tfplan.binary
-$ terraform show -json tfplan.binary > tfplan.json
-```
-
-For more details, see also [OPA document][opa-terraform].
-
-### Serverless Framework
-See [here][serverless].
-
-Server Framework uses YAML format for configurations. You can apply your Rego policies to `serverless.yaml`.
-
-## Custom Data
-See [here][data].
-
-## Combined Input
-See [here][combine].
-
-## Go Testing
-See [here][go-testing].
-
-[k8s]:https://github.com/aquasecurity/trivy/tree/{{ git.commit }}/examples/misconf/custom-policy/kubernetes/
-[dockerfile]:https://github.com/aquasecurity/trivy/tree/{{ git.commit }}/examples/misconf/custom-policy/dockerfile/
-[compose]:https://github.com/aquasecurity/trivy/tree/{{ git.commit }}/examples/misconf/custom-policy/docker-compose/
-[hcl]:https://github.com/aquasecurity/trivy/tree/{{ git.commit }}/examples/misconf/custom-policy/hcl/
-[serverless]:https://github.com/aquasecurity/trivy/tree/{{ git.commit }}/examples/misconf/custom-policy/serverless/
-[tfplan]:https://github.com/aquasecurity/trivy/tree/{{ git.commit }}/examples/misconf/custom-policy/terraform-plan/
-[terraform-show]: https://www.terraform.io/docs/cli/commands/show.html
-[opa-terraform]: https://www.openpolicyagent.org/docs/latest/terraform/
-
-[custom]: https://github.com/aquasecurity/trivy/tree/{{ git.commit }}/examples/misconf/custom-policy
-[data]: https://github.com/aquasecurity/trivy/tree/{{ git.commit }}/examples/misconf/custom-data
-[combine]: https://github.com/aquasecurity/trivy/tree/{{ git.commit }}/examples/misconf/combine
-[go-testing]: https://github.com/aquasecurity/trivy/tree/{{ git.commit }}/examples/misconf/go-testing
-

docs/docs/misconfiguration/options/filter.md

@@ -1,60 +0,0 @@
-# Filter Misconfigurations
-
-## By Severity
-
-Use `--severity` option.
-
-```bash
-trivy conf --severity HIGH,CRITICAL examples/misconf/mixed
-```
-
-<details>
-<summary>Result</summary>
-
-```shell
-2022-05-16T13:50:42.718+0100	INFO	Detected config files: 3
-
-Dockerfile (dockerfile)
-=======================
-Tests: 17 (SUCCESSES: 16, FAILURES: 1, EXCEPTIONS: 0)
-Failures: 1 (HIGH: 1, CRITICAL: 0)
-
-HIGH: Last USER command in Dockerfile should not be 'root'
-═══════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════
-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
-───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
- Dockerfile:3
-───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
-   3 [ USER root
-───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
-
-
-
-deployment.yaml (kubernetes)
-============================
-Tests: 8 (SUCCESSES: 8, FAILURES: 0, EXCEPTIONS: 0)
-Failures: 0 (HIGH: 0, CRITICAL: 0)
-
-
-main.tf (terraform)
-===================
-Tests: 1 (SUCCESSES: 0, FAILURES: 1, EXCEPTIONS: 0)
-Failures: 1 (HIGH: 0, CRITICAL: 1)
-
-CRITICAL: Classic resources should not be used.
-═══════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════
-AWS Classic resources run in a shared environment with infrastructure owned by other AWS customers. You should run
-resources in a VPC instead.
-
-See https://avd.aquasec.com/misconfig/avd-aws-0081
-───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
- main.tf:2-4
-───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
-   2 ┌ resource "aws_db_security_group" "sg" {
-   3 │
-   4 └ }
-───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
-```
-</details>

docs/docs/misconfiguration/options/others.md

@@ -1,4 +0,0 @@
-# Others
-
-!!! hint
-    See also [Others](../../vulnerability/examples/others.md) in Vulnerability section.

docs/docs/misconfiguration/options/policy.md

@@ -1,35 +0,0 @@
-# Policy
-
-## Pass custom policies
-You can pass directories including your custom policies through `--policy` option.
-This can be repeated for specifying multiple directories.
-
-```bash
-cd examplex/misconf/
-trivy conf --policy custom-policy/policy --policy combine/policy --namespaces user misconf/mixed
-```
-
-For more details, see [Custom Policies](../custom/index.md).
-
-!!! tip
-    You also need to specify `--namespaces` option.
-
-## Pass custom data
-You can pass directories including your custom data through `--data` option.
-This can be repeated for specifying multiple directories.
-
-```bash
-cd examples/misconf/custom-data
-trivy conf --policy ./policy --data ./data --namespaces user ./configs
-```
-
-For more details, see [Custom Data](../custom/data.md).
-
-## Pass namespaces
-By default, Trivy evaluates policies defined in `builtin.*`.
-If you want to evaluate custom policies in other packages, you have to specify package prefixes through `--namespaces` option.
-This can be repeated for specifying multiple packages.
-
-``` bash
-trivy conf --policy ./policy --namespaces main --namespaces user ./configs
-```

docs/docs/misconfiguration/options/report.md

@@ -1,6 +0,0 @@
-# Report Formats
-
-See [Reports Formats](../../vulnerability/examples/report.md) in Vulnerability section.
-
-!!! caution
-    Misconfiguration scanning doesn't support default templates such as XML for now.

docs/docs/misconfiguration/options/values.md

@@ -1,48 +0,0 @@
-# Value Overrides
-
-Value files can be passed for supported scannable config files.
-
-## Terraform value overrides
-You can pass `tf-vars` files to Trivy to override default values found in the Terraform HCL code.
-
-```bash
-trivy conf --tf-vars dev.terraform.tfvars ./infrastructure/tf
-```
-
-## Helm value overrides
-There are a number of options for overriding values in Helm charts. When override values are passed to the Helm scanner, the values will be used during the Manifest rendering process and will become part of the scanned artifact.
-
-### Setting inline value overrides
-Overrides can be set inline on the command line
-
-```bash
-trivy conf --helm-set securityContext.runAsUser=0 ./charts/mySql
-```
-
-### Setting value file overrides
-Overrides can be in a file that has the key=value set. 
-
-```yaml
-# Example override file (overrides.yaml)
-
-securityContext:
-  runAsUser: 0
-```
-
-```bash
-trivy conf --helm-values overrides.yaml ./charts/mySql
-``` 
-
-### Setting value as explicit string
-the `--helm-set-string` is the same as `--helm-set` but explicitly retains the value as a string
-
-```bash
-trivy config --helm-set-string name=false ./infrastructure/tf
-```
-
-### Setting specific values from files
-Specific override values can come from specific files
-
-```bash
-trivy conf --helm-set-file environment=dev.values.yaml ./charts/mySql
-```

docs/docs/references/cli/trivy_filesystem.md

@@ -1,98 +0,0 @@
-## 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/.trivy/modules")
-      --no-progress                 suppress progress bar
-      --offline-scan                do not issue API requests to identify dependencies
-  -o, --output string               output file name
-      --password strings            password. Comma-separated passwords allowed. TRIVY_PASSWORD should be used for security reasons.
-      --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
-      --redis-tls                   enable redis TLS with public certificates, if using redis as cache backend
-      --registry-token string       registry token
-      --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 (oci,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
-      --username strings            username. Comma-separated usernames allowed.
-      --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 "/path/to/cache")
-  -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
-  -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
-

docs/docs/references/cli/trivy_image.md

@@ -1,120 +0,0 @@
-## 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/.trivy/modules")
-      --no-progress                    suppress progress bar
-      --offline-scan                   do not issue API requests to identify dependencies
-  -o, --output string                  output file name
-      --password strings               password. Comma-separated passwords allowed. TRIVY_PASSWORD should be used for security reasons.
-      --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
-      --redis-tls                      enable redis TLS with public certificates, if using redis as cache backend
-      --registry-token string          registry token
-      --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 (oci,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
-      --username strings               username. Comma-separated usernames allowed.
-      --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 "/path/to/cache")
-  -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
-  -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
-

docs/docs/references/cli/trivy_kubernetes.md

@@ -1,106 +0,0 @@
-## 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
-      --parallel int                number (between 1-20) of goroutines enabled for parallel scanning (default 5)
-      --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
-      --redis-tls                   enable redis TLS with public certificates, 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 (oci,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
-      --tolerations strings         specify node-collector job tolerations (example: key1=value1:NoExecute,key2=value2:NoSchedule)
-      --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 "/path/to/cache")
-  -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
-  -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
-

docs/docs/references/cli/trivy_repository.md

@@ -1,98 +0,0 @@
-## 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/.trivy/modules")
-      --no-progress                 suppress progress bar
-      --offline-scan                do not issue API requests to identify dependencies
-  -o, --output string               output file name
-      --password strings            password. Comma-separated passwords allowed. TRIVY_PASSWORD should be used for security reasons.
-      --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
-      --redis-tls                   enable redis TLS with public certificates, if using redis as cache backend
-      --registry-token string       registry token
-      --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 (oci,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
-      --username strings            username. Comma-separated usernames allowed.
-      --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 "/path/to/cache")
-  -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
-  -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
-

docs/docs/references/cli/trivy_rootfs.md

@@ -1,102 +0,0 @@
-## 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/.trivy/modules")
-      --no-progress                 suppress progress bar
-      --offline-scan                do not issue API requests to identify dependencies
-  -o, --output string               output file name
-      --password strings            password. Comma-separated passwords allowed. TRIVY_PASSWORD should be used for security reasons.
-      --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
-      --redis-tls                   enable redis TLS with public certificates, if using redis as cache backend
-      --registry-token string       registry token
-      --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 (oci,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
-      --username strings            username. Comma-separated usernames allowed.
-      --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 "/path/to/cache")
-  -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
-  -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
-

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

@@ -45,6 +45,7 @@ trivy [global flags] command [flags] target
 
 * [trivy aws](trivy_aws.md)	 - [EXPERIMENTAL] Scan AWS account
 * [trivy config](trivy_config.md)	 - Scan config files for misconfigurations
+* [trivy convert](trivy_convert.md)	 - Convert Trivy JSON report into a different format
 * [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

docs/docs/references/configuration/cli/trivy_aws.md

@@ -88,6 +88,7 @@ trivy aws [flags]
       --policy-namespaces strings   Rego namespaces
       --region string               AWS Region to scan
       --report string               specify a report format for the output. (all,summary) (default "all")
+      --reset-policy-bundle         remove policy bundle
       --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

docs/docs/references/configuration/cli/trivy_config.md

@@ -12,6 +12,7 @@ trivy config [flags] DIR
       --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
       --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
@@ -35,6 +36,8 @@ trivy config [flags] DIR
       --redis-key string            redis key file location, if using redis as cache backend
       --redis-tls                   enable redis TLS with public certificates, if using redis as cache backend
       --registry-token string       registry token
+      --report string               specify a compliance report format for the output. (all,summary) (default "all")
+      --reset-policy-bundle         remove policy bundle
   -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

docs/docs/references/configuration/cli/trivy_convert.md

@@ -0,0 +1,52 @@
+## trivy convert
+
+Convert Trivy JSON report into a different format
+
+```
+trivy convert [flags] RESULT_JSON
+```
+
+### Examples
+
+```
+  # report conversion
+  $ trivy image --format json --output result.json --list-all-pkgs debian:11
+  $ trivy convert --format cyclonedx --output result.cdx result.json
+
+```
+
+### Options
+
+```
+      --compliance string      compliance report to generate
+      --dependency-tree        [EXPERIMENTAL] show dependency origin tree of vulnerable packages
+      --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
+  -f, --format string          format (table, json, template, sarif, cyclonedx, spdx, spdx-json, github, cosign-vuln) (default "table")
+  -h, --help                   help for convert
+      --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
+```
+
+### Options inherited from parent commands
+
+```
+      --cache-dir string          cache directory (default "/path/to/cache")
+  -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
+  -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
+

docs/docs/references/configuration/cli/trivy_filesystem.md

@@ -0,0 +1,102 @@
+## 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
+      --compliance string                compliance report to generate
+      --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-confidence-level float   specify license classifier's confidence level (default 0.9)
+      --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/.trivy/modules")
+      --no-progress                      suppress progress bar
+      --offline-scan                     do not issue API requests to identify dependencies
+  -o, --output string                    output file name
+      --password strings                 password. Comma-separated passwords allowed. TRIVY_PASSWORD should be used for security reasons.
+      --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
+      --redis-tls                        enable redis TLS with public certificates, if using redis as cache backend
+      --registry-token string            registry token
+      --rekor-url string                 [EXPERIMENTAL] address of rekor STL server (default "https://rekor.sigstore.dev")
+      --report string                    specify a compliance report format for the output. (all,summary) (default "all")
+      --reset                            remove all caches and database
+      --reset-policy-bundle              remove policy bundle
+      --sbom-sources strings             [EXPERIMENTAL] try to retrieve SBOM from the specified sources (oci,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
+      --username strings                 username. Comma-separated usernames allowed.
+      --vuln-type strings                comma-separated list of vulnerability types (os,library) (default [os,library])
+```
+
+### Options inherited from parent commands
+
+```
+      --cache-dir string          cache directory (default "/path/to/cache")
+  -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
+  -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
+

docs/docs/references/configuration/cli/trivy_image.md

@@ -0,0 +1,124 @@
+## 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
+      --docker-host string               unix domain socket path to use for docker scanning
+      --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)
+      --image-src strings                image source(s) to use, in priority order (docker,containerd,podman,remote) (default [docker,containerd,podman,remote])
+      --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-confidence-level float   specify license classifier's confidence level (default 0.9)
+      --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/.trivy/modules")
+      --no-progress                      suppress progress bar
+      --offline-scan                     do not issue API requests to identify dependencies
+  -o, --output string                    output file name
+      --password strings                 password. Comma-separated passwords allowed. TRIVY_PASSWORD should be used for security reasons.
+      --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
+      --redis-tls                        enable redis TLS with public certificates, if using redis as cache backend
+      --registry-token string            registry token
+      --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
+      --reset-policy-bundle              remove policy bundle
+      --sbom-sources strings             [EXPERIMENTAL] try to retrieve SBOM from the specified sources (oci,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
+      --username strings                 username. Comma-separated usernames allowed.
+      --vuln-type strings                comma-separated list of vulnerability types (os,library) (default [os,library])
+```
+
+### Options inherited from parent commands
+
+```
+      --cache-dir string          cache directory (default "/path/to/cache")
+  -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
+  -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
+

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

@@ -0,0 +1,109 @@
+## 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
+
+```
+  -A, --all-namespaces                    fetch resources from all cluster namespaces
+      --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
+      --exclude-nodes strings             indicate the node labels that the node-collector job should exclude from scanning (example: kubernetes.io/arch:arm64,team:dev)
+      --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
+      --ignorefile string                 specify .trivyignore file (default ".trivyignore")
+      --image-src strings                 image source(s) to use, in priority order (docker,containerd,podman,remote) (default [docker,containerd,podman,remote])
+      --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
+      --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
+      --node-collector-namespace string   specify the namespace in which the node-collector job should be deployed (default "trivy-temp")
+      --offline-scan                      do not issue API requests to identify dependencies
+  -o, --output string                     output file name
+      --parallel int                      number (between 1-20) of goroutines enabled for parallel scanning (default 5)
+      --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
+      --redis-tls                         enable redis TLS with public certificates, 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
+      --reset-policy-bundle               remove policy bundle
+      --sbom-sources strings              [EXPERIMENTAL] try to retrieve SBOM from the specified sources (oci,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
+      --tolerations strings               specify node-collector job tolerations (example: key1=value1:NoExecute,key2=value2:NoSchedule)
+      --trace                             enable more verbose trace output for custom queries
+      --vuln-type strings                 comma-separated list of vulnerability types (os,library) (default [os,library])
+```
+
+### Options inherited from parent commands
+
+```
+      --cache-dir string          cache directory (default "/path/to/cache")
+  -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
+  -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
+

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

@@ -0,0 +1,100 @@
+## 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-confidence-level float   specify license classifier's confidence level (default 0.9)
+      --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/.trivy/modules")
+      --no-progress                      suppress progress bar
+      --offline-scan                     do not issue API requests to identify dependencies
+  -o, --output string                    output file name
+      --password strings                 password. Comma-separated passwords allowed. TRIVY_PASSWORD should be used for security reasons.
+      --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
+      --redis-tls                        enable redis TLS with public certificates, if using redis as cache backend
+      --registry-token string            registry token
+      --rekor-url string                 [EXPERIMENTAL] address of rekor STL server (default "https://rekor.sigstore.dev")
+      --reset                            remove all caches and database
+      --reset-policy-bundle              remove policy bundle
+      --sbom-sources strings             [EXPERIMENTAL] try to retrieve SBOM from the specified sources (oci,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
+      --username strings                 username. Comma-separated usernames allowed.
+      --vuln-type strings                comma-separated list of vulnerability types (os,library) (default [os,library])
+```
+
+### Options inherited from parent commands
+
+```
+      --cache-dir string          cache directory (default "/path/to/cache")
+  -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
+  -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
+

docs/docs/references/configuration/cli/trivy_rootfs.md

@@ -0,0 +1,104 @@
+## 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-confidence-level float   specify license classifier's confidence level (default 0.9)
+      --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/.trivy/modules")
+      --no-progress                      suppress progress bar
+      --offline-scan                     do not issue API requests to identify dependencies
+  -o, --output string                    output file name
+      --password strings                 password. Comma-separated passwords allowed. TRIVY_PASSWORD should be used for security reasons.
+      --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
+      --redis-tls                        enable redis TLS with public certificates, if using redis as cache backend
+      --registry-token string            registry token
+      --rekor-url string                 [EXPERIMENTAL] address of rekor STL server (default "https://rekor.sigstore.dev")
+      --reset                            remove all caches and database
+      --reset-policy-bundle              remove policy bundle
+      --sbom-sources strings             [EXPERIMENTAL] try to retrieve SBOM from the specified sources (oci,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
+      --username strings                 username. Comma-separated usernames allowed.
+      --vuln-type strings                comma-separated list of vulnerability types (os,library) (default [os,library])
+```
+
+### Options inherited from parent commands
+
+```
+      --cache-dir string          cache directory (default "/path/to/cache")
+  -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
+  -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
+

docs/docs/references/configuration/cli/trivy_sbom.md

@@ -12,9 +12,6 @@ trivy sbom [flags] SBOM_PATH
   # 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
 
@@ -62,7 +59,8 @@ trivy sbom [flags] SBOM_PATH
   -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")
+      --vex string                  [EXPERIMENTAL] file path to VEX
+      --vuln-type strings           comma-separated list of vulnerability types (os,library) (default [os,library])
 ```
 
 ### Options inherited from parent commands

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

@@ -32,15 +32,18 @@ trivy server [flags]
       --listen string               listen address in server mode (default "localhost:4954")
       --module-dir string           specify directory to the wasm modules that will be loaded (default "$HOME/.trivy/modules")
       --no-progress                 suppress progress bar
+      --password strings            password. Comma-separated passwords allowed. TRIVY_PASSWORD should be used for security reasons.
       --redis-ca string             redis ca file location, if using redis as cache backend
       --redis-cert string           redis certificate file location, if using redis as cache backend
       --redis-key string            redis key file location, if using redis as cache backend
       --redis-tls                   enable redis TLS with public certificates, if using redis as cache backend
+      --registry-token string       registry token
       --reset                       remove all caches and database
       --skip-db-update              skip updating vulnerability database
       --skip-java-db-update         skip updating Java index database
       --token string                for authentication in client/server mode
       --token-header string         specify a header name for token in client/server mode (default "Trivy-Token")
+      --username strings            username. Comma-separated usernames allowed.
 ```
 
 ### Options inherited from parent commands

docs/docs/references/configuration/cli/trivy_vm.md

@@ -42,11 +42,9 @@ trivy vm [flags] VM_IMAGE
   -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/.trivy/modules")
       --no-progress                 suppress progress bar
@@ -58,6 +56,7 @@ trivy vm [flags] VM_IMAGE
       --redis-tls                   enable redis TLS with public certificates, 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
+      --reset-policy-bundle         remove policy bundle
       --sbom-sources strings        [EXPERIMENTAL] try to retrieve SBOM from the specified sources (oci,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")
@@ -72,7 +71,7 @@ trivy vm [flags] VM_IMAGE
       --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")
+      --vuln-type strings           comma-separated list of vulnerability types (os,library) (default [os,library])
 ```
 
 ### Options inherited from parent commands

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

@@ -1,6 +1,7 @@
 # Config file
 
-Trivy can be customized by tweaking a `trivy.yaml` file. The config path can be overridden by the `--config` flag.
+Trivy can be customized by tweaking a `trivy.yaml` file.
+The config path can be overridden by the `--config` flag.
 
 An example is [here][example].
 
@@ -192,6 +193,15 @@ image:
   # Same as '--removed-pkgs'
   # Default is false
   removed-pkgs: false
+  
+  # Same as '--platform'
+  # Default is empty
+  platform: 
+  
+  docker:
+    # Same as '--docker-host'
+    # Default is empty
+    host: 
 ```
 
 ## Vulnerability Options

docs/docs/references/customization/envs.md

@@ -1,17 +0,0 @@
-# Environment variables
-
-Trivy can be customized by environment variables.
-The environment variable key is the flag name converted by the following procedure.
-
-- Add `TRIVY_` prefix
-- Make it all uppercase
-- Replace `-` with `_`
-
-For example, 
-
-- `--debug` => `TRIVY_DEBUG`
-- `--cache-dir` => `TRIVY_CACHE_DIR`
-
-```
-$ TRIVY_DEBUG=true TRIVY_SEVERITY=CRITICAL trivy image alpine:3.15
-```

docs/docs/sbom/cyclonedx.md

@@ -1,249 +0,0 @@
-# CycloneDX generation
-Trivy can generate SBOM in the [CycloneDX][cyclonedx] format.
-Note that XML format is not supported at the moment.
-
-You can use the regular subcommands (like `image`, `fs` and `rootfs`) and specify `cyclonedx` with the `--format` option.
-
-CycloneDX can represent either or both SBOM or BOV.
-
-- [Software Bill of Materials (SBOM)][sbom]
-- [Bill of Vulnerabilities (BOV)][bov]
-
-By default, `--format cyclonedx` represents SBOM and doesn't include vulnerabilities in the CycloneDX output.
-
-```
-$ trivy image --format cyclonedx --output result.json alpine:3.15
-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>
-<summary>Result</summary>
-
-```
-$ cat result.json | jq .
-{
-  "bomFormat": "CycloneDX",
-  "specVersion": "1.4",
-  "serialNumber": "urn:uuid:2be5773d-7cd3-4b4b-90a5-e165474ddace",
-  "version": 1,
-  "metadata": {
-    "timestamp": "2022-02-22T15:11:40.270597Z",
-    "tools": [
-      {
-        "vendor": "aquasecurity",
-        "name": "trivy",
-        "version": "dev"
-      }
-    ],
-    "component": {
-      "bom-ref": "pkg:oci/alpine@sha256:21a3deaa0d32a8057914f36584b5288d2e5ecc984380bc0118285c70fa8c9300?repository_url=index.docker.io%2Flibrary%2Falpine&arch=amd64",
-      "type": "container",
-      "name": "alpine:3.15",
-      "version": "",
-      "purl": "pkg:oci/alpine@sha256:21a3deaa0d32a8057914f36584b5288d2e5ecc984380bc0118285c70fa8c9300?repository_url=index.docker.io%2Flibrary%2Falpine&arch=amd64",
-      "properties": [
-        {
-          "name": "aquasecurity:trivy:SchemaVersion",
-          "value": "2"
-        },
-        {
-          "name": "aquasecurity:trivy:ImageID",
-          "value": "sha256:c059bfaa849c4d8e4aecaeb3a10c2d9b3d85f5165c66ad3a4d937758128c4d18"
-        },
-        {
-          "name": "aquasecurity:trivy:RepoDigest",
-          "value": "alpine@sha256:21a3deaa0d32a8057914f36584b5288d2e5ecc984380bc0118285c70fa8c9300"
-        },
-        {
-          "name": "aquasecurity:trivy:DiffID",
-          "value": "sha256:8d3ac3489996423f53d6087c81180006263b79f206d3fdec9e66f0e27ceb8759"
-        },
-        {
-          "name": "aquasecurity:trivy:RepoTag",
-          "value": "alpine:3.15"
-        }
-      ]
-    }
-  },
-  "components": [
-    {
-      "bom-ref": "pkg:apk/alpine/alpine-baselayout@3.2.0-r18?distro=3.15.0",
-      "type": "library",
-      "name": "alpine-baselayout",
-      "version": "3.2.0-r18",
-      "licenses": [
-        {
-          "expression": "GPL-2.0-only"
-        }
-      ],
-      "purl": "pkg:apk/alpine/alpine-baselayout@3.2.0-r18?distro=3.15.0",
-      "properties": [
-        {
-          "name": "aquasecurity:trivy:SrcName",
-          "value": "alpine-baselayout"
-        },
-        {
-          "name": "aquasecurity:trivy:SrcVersion",
-          "value": "3.2.0-r18"
-        },
-        {
-          "name": "aquasecurity:trivy:LayerDigest",
-          "value": "sha256:59bf1c3509f33515622619af21ed55bbe26d24913cedbca106468a5fb37a50c3"
-        },
-        {
-          "name": "aquasecurity:trivy:LayerDiffID",
-          "value": "sha256:8d3ac3489996423f53d6087c81180006263b79f206d3fdec9e66f0e27ceb8759"
-        }
-      ]
-    },
-    ...(snip)...
-    {
-      "bom-ref": "pkg:apk/alpine/zlib@1.2.11-r3?distro=3.15.0",
-      "type": "library",
-      "name": "zlib",
-      "version": "1.2.11-r3",
-      "licenses": [
-        {
-          "expression": "Zlib"
-        }
-      ],
-      "purl": "pkg:apk/alpine/zlib@1.2.11-r3?distro=3.15.0",
-      "properties": [
-        {
-          "name": "aquasecurity:trivy:SrcName",
-          "value": "zlib"
-        },
-        {
-          "name": "aquasecurity:trivy:SrcVersion",
-          "value": "1.2.11-r3"
-        },
-        {
-          "name": "aquasecurity:trivy:LayerDigest",
-          "value": "sha256:59bf1c3509f33515622619af21ed55bbe26d24913cedbca106468a5fb37a50c3"
-        },
-        {
-          "name": "aquasecurity:trivy:LayerDiffID",
-          "value": "sha256:8d3ac3489996423f53d6087c81180006263b79f206d3fdec9e66f0e27ceb8759"
-        }
-      ]
-    },
-    {
-      "bom-ref": "3da6a469-964d-4b4e-b67d-e94ec7c88d37",
-      "type": "operating-system",
-      "name": "alpine",
-      "version": "3.15.0",
-      "properties": [
-        {
-          "name": "aquasecurity:trivy:Type",
-          "value": "alpine"
-        },
-        {
-          "name": "aquasecurity:trivy:Class",
-          "value": "os-pkgs"
-        }
-      ]
-    }
-  ],
-  "dependencies": [
-    {
-      "ref": "3da6a469-964d-4b4e-b67d-e94ec7c88d37",
-      "dependsOn": [
-        "pkg:apk/alpine/alpine-baselayout@3.2.0-r18?distro=3.15.0",
-        "pkg:apk/alpine/alpine-keys@2.4-r1?distro=3.15.0",
-        "pkg:apk/alpine/apk-tools@2.12.7-r3?distro=3.15.0",
-        "pkg:apk/alpine/busybox@1.34.1-r3?distro=3.15.0",
-        "pkg:apk/alpine/ca-certificates-bundle@20191127-r7?distro=3.15.0",
-        "pkg:apk/alpine/libc-utils@0.7.2-r3?distro=3.15.0",
-        "pkg:apk/alpine/libcrypto1.1@1.1.1l-r7?distro=3.15.0",
-        "pkg:apk/alpine/libretls@3.3.4-r2?distro=3.15.0",
-        "pkg:apk/alpine/libssl1.1@1.1.1l-r7?distro=3.15.0",
-        "pkg:apk/alpine/musl@1.2.2-r7?distro=3.15.0",
-        "pkg:apk/alpine/musl-utils@1.2.2-r7?distro=3.15.0",
-        "pkg:apk/alpine/scanelf@1.3.3-r0?distro=3.15.0",
-        "pkg:apk/alpine/ssl_client@1.34.1-r3?distro=3.15.0",
-        "pkg:apk/alpine/zlib@1.2.11-r3?distro=3.15.0"
-      ]
-    },
-    {
-      "ref": "pkg:oci/alpine@sha256:21a3deaa0d32a8057914f36584b5288d2e5ecc984380bc0118285c70fa8c9300?repository_url=index.docker.io%2Flibrary%2Falpine&arch=amd64",
-      "dependsOn": [
-        "3da6a469-964d-4b4e-b67d-e94ec7c88d37"
-      ]
-    }
-  ],
-  "vulnerabilities": [
-    {
-      "id": "CVE-2021-42386",
-      "source": {
-        "name": "alpine",
-        "url": "https://secdb.alpinelinux.org/"
-      },
-      "ratings": [
-        {
-          "source": {
-            "name": "nvd"
-          },
-          "score": 7.2,
-          "severity": "high",
-          "method": "CVSSv31",
-          "vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H"
-        },
-        {
-          "source": {
-            "name": "nvd"
-          },
-          "score": 6.5,
-          "severity": "medium",
-          "method": "CVSSv2",
-          "vector": "AV:N/AC:L/Au:S/C:P/I:P/A:P"
-        },
-        {
-          "source": {
-            "name": "redhat"
-          },
-          "score": 6.6,
-          "severity": "medium",
-          "method": "CVSSv31",
-          "vector": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H"
-        }
-      ],
-      "cwes": [
-        416
-      ],
-      "description": "A use-after-free in Busybox's awk applet leads to denial of service and possibly code execution when processing a crafted awk pattern in the nvalloc function",
-      "advisories": [
-        {
-          "url": "https://access.redhat.com/security/cve/CVE-2021-42386"
-        },
-        {
-          "url": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-42386"
-        }
-      ],
-      "published": "2021-11-15 21:15:00 +0000 UTC",
-      "updated": "2022-01-04 17:14:00 +0000 UTC",
-      "affects": [
-        {
-          "ref": "pkg:apk/alpine/busybox@1.33.1-r3?distro=3.14.2"
-        },
-        {
-          "ref": "pkg:apk/alpine/ssl_client@1.33.1-r3?distro=3.14.2"
-        }
-      ]
-    }
-  ]
-}
-
-```
-
-</details>
-
-If you want to include vulnerabilities, you can enable vulnerability scanning via `--scanners vuln`.
-
-```
-$ trivy image --scanners vuln --format cyclonedx --output result.json alpine:3.15
-```
-
-
-[cyclonedx]: https://cyclonedx.org/
-[sbom]: https://cyclonedx.org/capabilities/sbom/
-[bov]: https://cyclonedx.org/capabilities/bov/

docs/docs/sbom/index.md

@@ -1,203 +0,0 @@
-# SBOM generation
-
-Trivy can generate the following SBOM formats.
-
-- [CycloneDX][cyclonedx]
-- [SPDX][spdx]
-
-## 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
-```
-
-
-```
-$ trivy fs --format cyclonedx --output result.json /app/myproject
-```
-
-<details>
-<summary>Result</summary>
-
-```
-{
-  "bomFormat": "CycloneDX",
-  "specVersion": "1.3",
-  "serialNumber": "urn:uuid:2be5773d-7cd3-4b4b-90a5-e165474ddace",
-  "version": 1,
-  "metadata": {
-    "timestamp": "2022-02-22T15:11:40.270597Z",
-    "tools": [
-      {
-        "vendor": "aquasecurity",
-        "name": "trivy",
-        "version": "dev"
-      }
-    ],
-    "component": {
-      "bom-ref": "pkg:oci/alpine@sha256:21a3deaa0d32a8057914f36584b5288d2e5ecc984380bc0118285c70fa8c9300?repository_url=index.docker.io%2Flibrary%2Falpine&arch=amd64",
-      "type": "container",
-      "name": "alpine:3.15",
-      "version": "",
-      "purl": "pkg:oci/alpine@sha256:21a3deaa0d32a8057914f36584b5288d2e5ecc984380bc0118285c70fa8c9300?repository_url=index.docker.io%2Flibrary%2Falpine&arch=amd64",
-      "properties": [
-        {
-          "name": "aquasecurity:trivy:SchemaVersion",
-          "value": "2"
-        },
-        {
-          "name": "aquasecurity:trivy:ImageID",
-          "value": "sha256:c059bfaa849c4d8e4aecaeb3a10c2d9b3d85f5165c66ad3a4d937758128c4d18"
-        },
-        {
-          "name": "aquasecurity:trivy:RepoDigest",
-          "value": "alpine@sha256:21a3deaa0d32a8057914f36584b5288d2e5ecc984380bc0118285c70fa8c9300"
-        },
-        {
-          "name": "aquasecurity:trivy:DiffID",
-          "value": "sha256:8d3ac3489996423f53d6087c81180006263b79f206d3fdec9e66f0e27ceb8759"
-        },
-        {
-          "name": "aquasecurity:trivy:RepoTag",
-          "value": "alpine:3.15"
-        }
-      ]
-    }
-  },
-  "components": [
-    {
-      "bom-ref": "pkg:apk/alpine/alpine-baselayout@3.2.0-r18?distro=3.15.0",
-      "type": "library",
-      "name": "alpine-baselayout",
-      "version": "3.2.0-r18",
-      "licenses": [
-        {
-          "expression": "GPL-2.0-only"
-        }
-      ],
-      "purl": "pkg:apk/alpine/alpine-baselayout@3.2.0-r18?distro=3.15.0",
-      "properties": [
-        {
-          "name": "aquasecurity:trivy:SrcName",
-          "value": "alpine-baselayout"
-        },
-        {
-          "name": "aquasecurity:trivy:SrcVersion",
-          "value": "3.2.0-r18"
-        },
-        {
-          "name": "aquasecurity:trivy:LayerDigest",
-          "value": "sha256:59bf1c3509f33515622619af21ed55bbe26d24913cedbca106468a5fb37a50c3"
-        },
-        {
-          "name": "aquasecurity:trivy:LayerDiffID",
-          "value": "sha256:8d3ac3489996423f53d6087c81180006263b79f206d3fdec9e66f0e27ceb8759"
-        }
-      ]
-    },
-    ...(snip)...
-    {
-      "bom-ref": "pkg:apk/alpine/zlib@1.2.11-r3?distro=3.15.0",
-      "type": "library",
-      "name": "zlib",
-      "version": "1.2.11-r3",
-      "licenses": [
-        {
-          "expression": "Zlib"
-        }
-      ],
-      "purl": "pkg:apk/alpine/zlib@1.2.11-r3?distro=3.15.0",
-      "properties": [
-        {
-          "name": "aquasecurity:trivy:SrcName",
-          "value": "zlib"
-        },
-        {
-          "name": "aquasecurity:trivy:SrcVersion",
-          "value": "1.2.11-r3"
-        },
-        {
-          "name": "aquasecurity:trivy:LayerDigest",
-          "value": "sha256:59bf1c3509f33515622619af21ed55bbe26d24913cedbca106468a5fb37a50c3"
-        },
-        {
-          "name": "aquasecurity:trivy:LayerDiffID",
-          "value": "sha256:8d3ac3489996423f53d6087c81180006263b79f206d3fdec9e66f0e27ceb8759"
-        }
-      ]
-    },
-    {
-      "bom-ref": "3da6a469-964d-4b4e-b67d-e94ec7c88d37",
-      "type": "operating-system",
-      "name": "alpine",
-      "version": "3.15.0",
-      "properties": [
-        {
-          "name": "aquasecurity:trivy:Type",
-          "value": "alpine"
-        },
-        {
-          "name": "aquasecurity:trivy:Class",
-          "value": "os-pkgs"
-        }
-      ]
-    }
-  ],
-  "dependencies": [
-    {
-      "ref": "3da6a469-964d-4b4e-b67d-e94ec7c88d37",
-      "dependsOn": [
-        "pkg:apk/alpine/alpine-baselayout@3.2.0-r18?distro=3.15.0",
-        "pkg:apk/alpine/alpine-keys@2.4-r1?distro=3.15.0",
-        "pkg:apk/alpine/apk-tools@2.12.7-r3?distro=3.15.0",
-        "pkg:apk/alpine/busybox@1.34.1-r3?distro=3.15.0",
-        "pkg:apk/alpine/ca-certificates-bundle@20191127-r7?distro=3.15.0",
-        "pkg:apk/alpine/libc-utils@0.7.2-r3?distro=3.15.0",
-        "pkg:apk/alpine/libcrypto1.1@1.1.1l-r7?distro=3.15.0",
-        "pkg:apk/alpine/libretls@3.3.4-r2?distro=3.15.0",
-        "pkg:apk/alpine/libssl1.1@1.1.1l-r7?distro=3.15.0",
-        "pkg:apk/alpine/musl@1.2.2-r7?distro=3.15.0",
-        "pkg:apk/alpine/musl-utils@1.2.2-r7?distro=3.15.0",
-        "pkg:apk/alpine/scanelf@1.3.3-r0?distro=3.15.0",
-        "pkg:apk/alpine/ssl_client@1.34.1-r3?distro=3.15.0",
-        "pkg:apk/alpine/zlib@1.2.11-r3?distro=3.15.0"
-      ]
-    },
-    {
-      "ref": "pkg:oci/alpine@sha256:21a3deaa0d32a8057914f36584b5288d2e5ecc984380bc0118285c70fa8c9300?repository_url=index.docker.io%2Flibrary%2Falpine&arch=amd64",
-      "dependsOn": [
-        "3da6a469-964d-4b4e-b67d-e94ec7c88d37"
-      ]
-    }
-  ]
-}
-
-```
-
-</details>
-
-## Supported packages
-Trivy supports the following packages.
-
-- [OS packages][os_packages]
-- [Language-specific packages][language_packages]
-
-In addition to the above packages, Trivy also supports the following packages for generating SBOM.
-
-!!! note
-    These packages are not supported for vulnerability scanning.
-
-| Language | File              | Dependency location[^1] |
-|----------|-------------------|:-----------------------:|
-| Python   | conda package[^2] |            -            |
-| Swift    | Podfile.lock      |            -            |
-
-[^1]: Use `startline == 1 and endline == 1` for unsupported file types
-[^2]: `envs/*/conda-meta/*.json`
-
-[cyclonedx]: cyclonedx.md
-[spdx]: spdx.md
-
-[os_packages]: ../vulnerability/detection/os.md
-[language_packages]: ../vulnerability/detection/language.md

docs/docs/sbom/spdx.md

@@ -1,298 +0,0 @@
-# SPDX generation
-
-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.
-
-```
-$ trivy image --format spdx --output result.spdx alpine:3.15
-```
-
-<details>
-<summary>Result</summary>
-
-```
-$ cat result.spdx
-SPDXVersion: SPDX-2.2
-DataLicense: CC0-1.0
-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-0.38.1
-Created: 2022-04-28T07:32:57.142806Z
-
-##### Package: zlib
-
-PackageName: zlib
-SPDXID: SPDXRef-12bc938ac028a5e1
-PackageVersion: 1.2.12-r0
-FilesAnalyzed: false
-PackageLicenseConcluded: Zlib
-PackageLicenseDeclared: Zlib
-
-##### Package: apk-tools
-
-PackageName: apk-tools
-SPDXID: SPDXRef-26c274652190d87f
-PackageVersion: 2.12.7-r3
-FilesAnalyzed: false
-PackageLicenseConcluded: GPL-2.0-only
-PackageLicenseDeclared: GPL-2.0-only
-
-##### Package: libretls
-
-PackageName: libretls
-SPDXID: SPDXRef-2b021966d19a8211
-PackageVersion: 3.3.4-r3
-FilesAnalyzed: false
-PackageLicenseConcluded: ISC AND (BSD-3-Clause OR MIT)
-PackageLicenseDeclared: ISC AND (BSD-3-Clause OR MIT)
-
-##### Package: busybox
-
-PackageName: busybox
-SPDXID: SPDXRef-317ce3476703f20d
-PackageVersion: 1.34.1-r5
-FilesAnalyzed: false
-PackageLicenseConcluded: GPL-2.0-only
-PackageLicenseDeclared: GPL-2.0-only
-
-##### Package: libcrypto1.1
-
-PackageName: libcrypto1.1
-SPDXID: SPDXRef-34f407fb4dbd67f4
-PackageVersion: 1.1.1n-r0
-FilesAnalyzed: false
-PackageLicenseConcluded: OpenSSL
-PackageLicenseDeclared: OpenSSL
-
-##### Package: libc-utils
-
-PackageName: libc-utils
-SPDXID: SPDXRef-4bbc1cb449d54083
-PackageVersion: 0.7.2-r3
-FilesAnalyzed: false
-PackageLicenseConcluded: BSD-2-Clause AND BSD-3-Clause
-PackageLicenseDeclared: BSD-2-Clause AND BSD-3-Clause
-
-##### Package: alpine-keys
-
-PackageName: alpine-keys
-SPDXID: SPDXRef-a3bdd174be1456b6
-PackageVersion: 2.4-r1
-FilesAnalyzed: false
-PackageLicenseConcluded: MIT
-PackageLicenseDeclared: MIT
-
-##### Package: ca-certificates-bundle
-
-PackageName: ca-certificates-bundle
-SPDXID: SPDXRef-ac6472ba26fb991c
-PackageVersion: 20211220-r0
-FilesAnalyzed: false
-PackageLicenseConcluded: MPL-2.0 AND MIT
-PackageLicenseDeclared: MPL-2.0 AND MIT
-
-##### Package: libssl1.1
-
-PackageName: libssl1.1
-SPDXID: SPDXRef-b2d1b1d70fe90f7d
-PackageVersion: 1.1.1n-r0
-FilesAnalyzed: false
-PackageLicenseConcluded: OpenSSL
-PackageLicenseDeclared: OpenSSL
-
-##### Package: scanelf
-
-PackageName: scanelf
-SPDXID: SPDXRef-c617077ba6649520
-PackageVersion: 1.3.3-r0
-FilesAnalyzed: false
-PackageLicenseConcluded: GPL-2.0-only
-PackageLicenseDeclared: GPL-2.0-only
-
-##### Package: musl
-
-PackageName: musl
-SPDXID: SPDXRef-ca80b810029cde0e
-PackageVersion: 1.2.2-r7
-FilesAnalyzed: false
-PackageLicenseConcluded: MIT
-PackageLicenseDeclared: MIT
-
-##### Package: alpine-baselayout
-
-PackageName: alpine-baselayout
-SPDXID: SPDXRef-d782e64751ba9faa
-PackageVersion: 3.2.0-r18
-FilesAnalyzed: false
-PackageLicenseConcluded: GPL-2.0-only
-PackageLicenseDeclared: GPL-2.0-only
-
-##### Package: musl-utils
-
-PackageName: musl-utils
-SPDXID: SPDXRef-e5e8a237f6162e22
-PackageVersion: 1.2.2-r7
-FilesAnalyzed: false
-PackageLicenseConcluded: MIT BSD GPL2+
-PackageLicenseDeclared: MIT BSD GPL2+
-
-##### Package: ssl_client
-
-PackageName: ssl_client
-SPDXID: SPDXRef-fdf0ce84f6337be4
-PackageVersion: 1.34.1-r5
-FilesAnalyzed: false
-PackageLicenseConcluded: GPL-2.0-only
-PackageLicenseDeclared: GPL-2.0-only
-```
-
-</details>
-
-SPDX-JSON format is also supported by using `spdx-json` with the `--format` option.
-
-```
-$ trivy image --format spdx-json --output result.spdx.json alpine:3.15
-```
-
-<details>
-<summary>Result</summary>
-
-```
-$ cat result.spdx.json | jq .
-{
-	"SPDXID": "SPDXRef-DOCUMENT",
-	"creationInfo": {
-		"created": "2022-04-28T08:16:55.328255Z",
-		"creators": [
-			"Tool: trivy-0.38.1",
-			"Organization: aquasecurity"
-		]
-	},
-	"dataLicense": "CC0-1.0",
-	"documentNamespace": "http://aquasecurity.github.io/trivy/container_image/alpine:3.15-d9549e3a-a4c5-4ee3-8bde-8c78d451fbe7",
-	"name": "alpine:3.15",
-	"packages": [
-		{
-			"SPDXID": "SPDXRef-12bc938ac028a5e1",
-			"filesAnalyzed": false,
-			"licenseConcluded": "Zlib",
-			"licenseDeclared": "Zlib",
-			"name": "zlib",
-			"versionInfo": "1.2.12-r0"
-		},
-		{
-			"SPDXID": "SPDXRef-26c274652190d87f",
-			"filesAnalyzed": false,
-			"licenseConcluded": "GPL-2.0-only",
-			"licenseDeclared": "GPL-2.0-only",
-			"name": "apk-tools",
-			"versionInfo": "2.12.7-r3"
-		},
-		{
-			"SPDXID": "SPDXRef-2b021966d19a8211",
-			"filesAnalyzed": false,
-			"licenseConcluded": "ISC AND (BSD-3-Clause OR MIT)",
-			"licenseDeclared": "ISC AND (BSD-3-Clause OR MIT)",
-			"name": "libretls",
-			"versionInfo": "3.3.4-r3"
-		},
-		{
-			"SPDXID": "SPDXRef-317ce3476703f20d",
-			"filesAnalyzed": false,
-			"licenseConcluded": "GPL-2.0-only",
-			"licenseDeclared": "GPL-2.0-only",
-			"name": "busybox",
-			"versionInfo": "1.34.1-r5"
-		},
-		{
-			"SPDXID": "SPDXRef-34f407fb4dbd67f4",
-			"filesAnalyzed": false,
-			"licenseConcluded": "OpenSSL",
-			"licenseDeclared": "OpenSSL",
-			"name": "libcrypto1.1",
-			"versionInfo": "1.1.1n-r0"
-		},
-		{
-			"SPDXID": "SPDXRef-4bbc1cb449d54083",
-			"filesAnalyzed": false,
-			"licenseConcluded": "BSD-2-Clause AND BSD-3-Clause",
-			"licenseDeclared": "BSD-2-Clause AND BSD-3-Clause",
-			"name": "libc-utils",
-			"versionInfo": "0.7.2-r3"
-		},
-		{
-			"SPDXID": "SPDXRef-a3bdd174be1456b6",
-			"filesAnalyzed": false,
-			"licenseConcluded": "MIT",
-			"licenseDeclared": "MIT",
-			"name": "alpine-keys",
-			"versionInfo": "2.4-r1"
-		},
-		{
-			"SPDXID": "SPDXRef-ac6472ba26fb991c",
-			"filesAnalyzed": false,
-			"licenseConcluded": "MPL-2.0 AND MIT",
-			"licenseDeclared": "MPL-2.0 AND MIT",
-			"name": "ca-certificates-bundle",
-			"versionInfo": "20211220-r0"
-		},
-		{
-			"SPDXID": "SPDXRef-b2d1b1d70fe90f7d",
-			"filesAnalyzed": false,
-			"licenseConcluded": "OpenSSL",
-			"licenseDeclared": "OpenSSL",
-			"name": "libssl1.1",
-			"versionInfo": "1.1.1n-r0"
-		},
-		{
-			"SPDXID": "SPDXRef-c617077ba6649520",
-			"filesAnalyzed": false,
-			"licenseConcluded": "GPL-2.0-only",
-			"licenseDeclared": "GPL-2.0-only",
-			"name": "scanelf",
-			"versionInfo": "1.3.3-r0"
-		},
-		{
-			"SPDXID": "SPDXRef-ca80b810029cde0e",
-			"filesAnalyzed": false,
-			"licenseConcluded": "MIT",
-			"licenseDeclared": "MIT",
-			"name": "musl",
-			"versionInfo": "1.2.2-r7"
-		},
-		{
-			"SPDXID": "SPDXRef-d782e64751ba9faa",
-			"filesAnalyzed": false,
-			"licenseConcluded": "GPL-2.0-only",
-			"licenseDeclared": "GPL-2.0-only",
-			"name": "alpine-baselayout",
-			"versionInfo": "3.2.0-r18"
-		},
-		{
-			"SPDXID": "SPDXRef-e5e8a237f6162e22",
-			"filesAnalyzed": false,
-			"licenseConcluded": "MIT BSD GPL2+",
-			"licenseDeclared": "MIT BSD GPL2+",
-			"name": "musl-utils",
-			"versionInfo": "1.2.2-r7"
-		},
-		{
-			"SPDXID": "SPDXRef-fdf0ce84f6337be4",
-			"filesAnalyzed": false,
-			"licenseConcluded": "GPL-2.0-only",
-			"licenseDeclared": "GPL-2.0-only",
-			"name": "ssl_client",
-			"versionInfo": "1.34.1-r5"
-		}
-	],
-	"spdxVersion": "SPDX-2.2"
-}
-```
-
-</details>
-
-
-[spdx]: https://spdx.dev/wp-content/uploads/sites/41/2020/08/SPDX-specification-2-2.pdf

docs/docs/scanner/license.md

@@ -20,16 +20,18 @@ By default, Trivy scans licenses for packages installed by `apk`, `apt-get`, `dn
 To enable extended license scanning, you can use `--license-full`.
 In addition to package licenses, Trivy scans source code files, Markdown documents, text files and `LICENSE` documents to identify license usage within the image or filesystem.
 
+By default, Trivy only classifies licenses that are matched with a confidence level of 0.9 or more by the classifer.
+To configure the confidence level, you can use `--license-confidence-level`. This enables us to classify licenses that might be matched with a lower confidence level by the classifer. 
+
 !!! note
     The full license scanning is expensive. It takes a while.
 
 Currently, the standard license scanning doesn't support filesystem and repository scanning.
 
-|   License scanning    | Image | Rootfs    | Filesystem | Repository |
-|:---------------------:|:-----:|:---------:|:----------:|:----------:|
-|       Standard        |  ✅   |     ✅    |   -        |      -     |
-| Full (--license-full) |  ✅   |     ✅    |     ✅     |     ✅     |
-
+|   License scanning    | Image | Rootfs | Filesystem | Repository |
+|:---------------------:|:-----:|:------:|:----------:|:----------:|
+|       Standard        |   ✅   |   ✅    |     -      |     -      |
+| Full (--license-full) |   ✅   |   ✅    |     ✅      |     ✅      |
 
 License checking classifies the identified licenses and map the classification to severity.
 
@@ -158,6 +160,30 @@ Total: 2 (HIGH: 2, CRITICAL: 0)
 
 ```
 
+### Configuring Classifier Confidence Level
+You can use the `--license-confidence-level` flag to adjust the confidence level between 0.0 to 1.0 (default 0.9).
+For example, when you run the scanner with the default confidence level on [SPDX license list data](https://github.com/spdx/license-list-data/tree/main/text), it is able to detect only 258 licenses.
+
+```shell
+$ trivy fs --scanners license --license-full <path/to/spdx/list/data>
+2023-04-18T10:05:13.601-0700    INFO    Full license scanning is enabled
+
+Loose File License(s) (license)
+===============================
+Total: 258 (UNKNOWN: 70, LOW: 90, MEDIUM: 18, HIGH: 58, CRITICAL: 22)
+```
+
+However, by configuring the confidence level to 0.8, the scanner is now able to detect 282 licenses.
+
+```shell
+$ trivy fs --scanners license --license-full --license-confidence-level 0.8 <path/to/spdx/list/data>
+2023-04-18T10:21:39.637-0700    INFO    Full license scanning is enabled
+
+Loose File License(s) (license)
+===============================
+Total: 282 (UNKNOWN: 81, LOW: 97, MEDIUM: 24, HIGH: 58, CRITICAL: 22)
+```
+
 ### Custom Classification
 You can generate the default config by the `--generate-default-config` flag and customize the license classification.
 For example, if you want to forbid only AGPL-3.0, you can leave it under `forbidden` and move other licenses to another classification.

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

@@ -196,7 +196,7 @@ You can specify input format via the `custom.input` annotation.
     `type` accepts `kubernetes`, `dockerfile`, `cloudformation`, `terraform`, `terraformplan`, `json`, or `yaml`.
 
 ### Schemas
-See [here](./schema.md) for the detail.
+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/scanner/misconfiguration/index.md

@@ -2,8 +2,6 @@
 Trivy provides built-in policies to detect configuration issues in popular Infrastructure as Code files, such as: Docker, Kubernetes, Terraform, CloudFormation, and more. 
 In addition to built-in policies, you can write your own custom policies, as you can see [here][custom].
 
-![misconf](../../imgs/misconf.png)
-
 ## Quick start
 
 Simply specify a directory containing IaC files such as Terraform, CloudFormation, Azure ARM templates, Helm Charts and Dockerfile.
@@ -313,7 +311,87 @@ Tests: 20 (SUCCESSES: 18, FAILURES: 2, EXCEPTIONS: 0)
 Failures: 2 (MEDIUM: 2, HIGH: 0, CRITICAL: 0)
 ```
 
-## Examples
-See [here](https://github.com/aquasecurity/trivy/tree/{{ git.tag }}/examples/misconf/mixed)
+## Configuration
+This section describes misconfiguration-specific configuration.
+Other common options are documented [here](../../configuration/index.md).
 
-[custom]: ./custom/index.md
+### Pass custom policies
+You can pass directories including your custom policies through `--policy` option.
+This can be repeated for specifying multiple directories.
+
+```bash
+cd examplex/misconf/
+trivy conf --policy custom-policy/policy --policy combine/policy --namespaces user misconf/mixed
+```
+
+For more details, see [Custom Policies](./custom/index.md).
+
+!!! tip
+You also need to specify `--namespaces` option.
+
+### Pass custom data
+You can pass directories including your custom data through `--data` option.
+This can be repeated for specifying multiple directories.
+
+```bash
+cd examples/misconf/custom-data
+trivy conf --policy ./policy --data ./data --namespaces user ./configs
+```
+
+For more details, see [Custom Data](./custom/data.md).
+
+### Pass namespaces
+By default, Trivy evaluates policies defined in `builtin.*`.
+If you want to evaluate custom policies in other packages, you have to specify package prefixes through `--namespaces` option.
+This can be repeated for specifying multiple packages.
+
+``` bash
+trivy conf --policy ./policy --namespaces main --namespaces user ./configs
+```
+
+### Terraform value overrides
+You can pass `tf-vars` files to Trivy to override default values found in the Terraform HCL code.
+
+```bash
+trivy conf --tf-vars dev.terraform.tfvars ./infrastructure/tf
+```
+
+### Helm value overrides
+There are a number of options for overriding values in Helm charts. When override values are passed to the Helm scanner, the values will be used during the Manifest rendering process and will become part of the scanned artifact.
+
+#### Setting inline value overrides
+Overrides can be set inline on the command line
+
+```bash
+trivy conf --helm-set securityContext.runAsUser=0 ./charts/mySql
+```
+
+#### Setting value file overrides
+Overrides can be in a file that has the key=value set.
+
+```yaml
+# Example override file (overrides.yaml)
+
+securityContext:
+  runAsUser: 0
+```
+
+```bash
+trivy conf --helm-values overrides.yaml ./charts/mySql
+``` 
+
+#### Setting value as explicit string
+the `--helm-set-string` is the same as `--helm-set` but explicitly retains the value as a string
+
+```bash
+trivy config --helm-set-string name=false ./infrastructure/tf
+```
+
+#### Setting specific values from files
+Specific override values can come from specific files
+
+```bash
+trivy conf --helm-set-file environment=dev.values.yaml ./charts/mySql
+```
+
+[custom]: custom/index.md

docs/docs/scanner/secret.md

@@ -0,0 +1,315 @@
+# Secret Scanning
+
+Trivy scans any container image, filesystem and git repository to detect exposed secrets like passwords, api keys, and tokens.
+Secret scanning is enabled by default.
+
+Trivy will scan every plaintext file, according to builtin rules or configuration. There are plenty of builtin rules:
+
+- AWS access key
+- GCP service account
+- GitHub personal access token
+- GitLab personal access token
+- Slack access token
+- etc.
+
+You can see a full list of [built-in rules][builtin] and [built-in allow rules][builtin-allow].
+
+!!! tip
+    If your secret is not detected properly, please make sure that your file including the secret is not in [the allowed paths][builtin-allow].
+    You can disable allow rules via [disable-allow-rules](#disable-rules).
+
+## Quick start
+This section shows how to scan secrets in container image and filesystem. Other subcommands should be the same.
+
+### Container image
+Specify an image name.
+
+``` shell
+$ trivy image myimage:1.0.0
+2022-04-21T18:56:44.099+0300    INFO    Detected OS: alpine
+2022-04-21T18:56:44.099+0300    INFO    Detecting Alpine vulnerabilities...
+2022-04-21T18:56:44.101+0300    INFO    Number of language-specific files: 0
+
+myimage:1.0.0 (alpine 3.15.0)
+=============================
+Total: 6 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 0, CRITICAL: 2)
+
++--------------+------------------+----------+-------------------+---------------+---------------------------------------+
+|   LIBRARY    | VULNERABILITY ID | SEVERITY | INSTALLED VERSION | FIXED VERSION |                 TITLE                 |
++--------------+------------------+----------+-------------------+---------------+---------------------------------------+
+| busybox      | CVE-2022-28391   | CRITICAL | 1.34.1-r3         | 1.34.1-r5     | CVE-2022-28391 affecting              |
+|              |                  |          |                   |               | package busybox 1.35.0                |
+|              |                  |          |                   |               | -->avd.aquasec.com/nvd/cve-2022-28391 |
++--------------+------------------|          |-------------------+---------------+---------------------------------------+
+| ssl_client   | CVE-2022-28391   |          | 1.34.1-r3         | 1.34.1-r5     | CVE-2022-28391 affecting              |
+|              |                  |          |                   |               | package busybox 1.35.0                |
+|              |                  |          |                   |               | -->avd.aquasec.com/nvd/cve-2022-28391 |
++--------------+------------------+----------+-------------------+---------------+---------------------------------------+
+
+app/secret.sh (secrets)
+=======================
+Total: 1 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 0, CRITICAL: 1)
+
++----------+-------------------+----------+---------+--------------------------------+
+| CATEGORY |    DESCRIPTION    | SEVERITY | LINE NO |             MATCH              |
++----------+-------------------+----------+---------+--------------------------------+
+|   AWS    | AWS Access Key ID | CRITICAL |   10    | export AWS_ACCESS_KEY_ID=***** |
++----------+-------------------+----------+---------+--------------------------------+
+```
+
+
+!!! tip
+    Trivy tries to detect a base image and skip those layers for secret scanning.
+    A base image usually contains a lot of files and makes secret scanning much slower.
+    If a secret is not detected properly, you can see base layers with the `--debug` flag.
+
+### Filesystem
+
+``` shell
+$ trivy fs /path/to/your_project
+...(snip)...
+
+certs/key.pem (secrets)
+========================
+Total: 1 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 1, CRITICAL: 0)
+
++----------------------+------------------------+----------+---------+---------------------------------+
+|       CATEGORY       |      DESCRIPTION       | SEVERITY | LINE NO |              MATCH              |
++----------------------+------------------------+----------+---------+---------------------------------+
+| AsymmetricPrivateKey | Asymmetric Private Key |   HIGH   |    1    | -----BEGIN RSA PRIVATE KEY----- |
++----------------------+------------------------+----------+---------+---------------------------------+
+```
+
+
+!!! tip
+    Your project may have some secrets for testing. You can skip them with `--skip-dirs` or `--skip-files`.
+    We would recommend specifying these options so that the secret scanning can be faster if those files don't need to be scanned.
+    Also, you can specify paths to be allowed in a configuration file. See the detail [here](#configuration).
+
+## Configuration
+This section describes secret-specific configuration.
+Other common options are documented [here](../configuration/index.md).
+
+Trivy has a set of builtin rules for secret scanning, which can be extended or modified by a configuration file.
+Trivy tries to load `trivy-secret.yaml` in the current directory by default.
+If the file doesn't exist, only built-in rules are used.
+You can customize the config file path via the `--secret-config` flag.
+
+!!! warning
+    Trivy uses [Golang regexp package](https://pkg.go.dev/regexp/syntax#hdr-Syntax). To use `^` and `$` as simbols of begin and end of line use multi-line mode -`(?m)`.
+
+### Custom Rules
+Trivy allows defining custom rules.
+
+``` yaml
+rules:
+  - id: rule1
+    category: general
+    title: Generic Rule
+    severity: HIGH
+    path: .*\.sh
+    keywords:
+      - secret
+    regex: (?i)(?P<key>(secret))(=|:).{0,5}['"](?P<secret>[0-9a-zA-Z\-_=]{8,64})['"]
+    secret-group-name: secret
+    allow-rules:
+      - id: skip-text
+        description: skip text files
+        path: .*\.txt
+```
+
+`id` (required)
+:   - Unique identifier for this rule.
+
+`category` (required)
+:   - String used for metadata and reporting purposes.
+
+`title` (required)
+:   - Short human-readable title of the rule.
+
+`severity` (required)
+:   - How critical this rule is.
+- Allowed values:
+- CRITICAL
+- HIGH
+- MEDIUM
+- LOW
+
+`regex` (required)
+:   - Golang regular expression used to detect secrets.
+
+`path` (optional)
+:   - Golang regular expression used to match paths.
+
+`keywords` (optional, recommended)
+:   - Keywords are used for pre-regex check filtering.
+- Rules that contain keywords will perform a quick string compare check to make sure the keyword(s) are in the content being scanned.
+- Ideally these values should either be part of the identifier or unique strings specific to the rule's regex.
+- It is recommended to define for better performance.
+
+`allow-rules` (optional)
+:   - Allow rules for a single rule to reduce false positives with known secrets.
+- The details are below.
+
+### Allow Rules
+If the detected secret is matched with the specified `regex`, then that secret will be skipped and not detected.
+The same logic applies for `path`.
+
+`allow-rules` can be defined globally and per each rule. The fields are the same.
+
+``` yaml
+rules:
+  - id: rule1
+    category: general
+    title: Generic Rule
+    severity: HIGH
+    regex: (?i)(?P<key>(secret))(=|:).{0,5}['"](?P<secret>[0-9a-zA-Z\-_=]{8,64})['"]
+    allow-rules:
+      - id: skip-text
+        description: skip text files
+        path: .*\.txt
+allow-rules:
+  - id: social-security-number
+    description: skip social security number
+    regex: 219-09-9999
+```
+
+
+`id` (required)
+:   - Unique identifier for this allow rule.
+
+`description` (optional)
+:   - Short human-readable description of this allow rule.
+
+`regex` (optional)
+:   - Golang regular expression used to allow detected secrets.
+- `regex` or `path` must be specified.
+
+`path` (optional)
+:   - Golang regular expression used to allow matched paths.
+- `regex` or `path` must be specified.
+
+### Enable Rules
+Trivy provides plenty of out-of-box rules and allow rules, but you may not need all of them.
+In that case, `enable-builtin-rules` will be helpful.
+If you just need AWS secret detection, you can enable only relevant rules as shown below.
+It specifies AWS-related rule IDs in `enable-builtin-rules`.
+All other rules are disabled, so the scanning will be much faster.
+We would strongly recommend using this option if you don't need all rules.
+
+You can see a full list of [built-in rule IDs][builtin] and [built-in allow rule IDs][builtin-allow].
+
+``` yaml
+enable-builtin-rules:
+  - aws-access-key-id
+  - aws-account-id
+  - aws-secret-access-key
+```
+
+### Disable Rules
+Trivy offers built-in rules and allow rules, but you may want to disable some of them.
+For example, you don't use Slack, so Slack doesn't have to be scanned.
+You can specify the Slack rule IDs, `slack-access-token` and `slack-web-hook` in `disable-rules` so that those rules will be disabled for less false positives.
+
+You should specify either `enable-builtin-rules` or `disable-rules`.
+If they both are specified, `disable-rules` takes precedence.
+In case `github-pat` is specified in `enable-builtin-rules` and `disable-rules`, it will be disabled.
+
+In addition, there are some allow rules.
+Markdown files are ignored by default, but you may want to scan markdown files as well.
+You can disable the allow rule by adding `markdown` to `disable-allow-rules`.
+
+You can see a full list of [built-in rule IDs][builtin] and [built-in allow rule IDs][builtin-allow].
+
+``` yaml
+disable-rules:
+  - slack-access-token
+  - slack-web-hook
+disable-allow-rules:
+  - markdown
+```
+
+## Recommendation
+We would recommend specifying `--skip-dirs` for faster secret scanning.
+In container image scanning, Trivy walks the file tree rooted  `/` and scans all the files other than [built-in allowed paths][builtin-allow].
+It will take a while if your image contains a lot of files even though Trivy tries to avoid scanning layers from a base image.
+If you want to make scanning faster, `--skip-dirs` and `--skip-files` helps so that Trivy will skip scanning those files and directories.
+You can see more options [here](../configuration/others.md).
+
+`allow-rules` is also helpful. See the [allow-rules](#allow-rules) section.
+
+In addition, all the built-in rules are enabled by default, so it takes some time to scan all of them.
+If you don't need all those rules, you can use `enable-builtin-rules` or `disable-rules` in the configuration file.
+You should use `enable-builtin-rules` if you need only AWS secret detection, for example.
+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 `--scanners` flag.
+
+```shell
+$ trivy image --scanners vuln alpine:3.15
+```
+
+## Example
+`trivy-secret.yaml` in the working directory is loaded by default.
+
+``` yaml
+$ cat trivy-secret.yaml
+rules:
+  - id: rule1
+    category: general
+    title: Generic Rule
+    severity: HIGH
+    regex: (?i)(?P<key>(secret))(=|:).{0,5}['"](?P<secret>[0-9a-zA-Z\-_=]{8,64})['"]
+allow-rules:
+  - id: social-security-number
+    description: skip social security number
+    regex: 219-09-9999
+  - id: log-dir
+    description: skip log directory
+    path: ^\/var\/log\/
+disable-rules:
+  - slack-access-token
+  - slack-web-hook
+disable-allow-rules:
+  - markdown
+
+# The following command automatically loads the above configuration.
+$ trivy image YOUR_IMAGE
+```
+
+Also, you can customize the config file path via `--secret-config`.
+
+``` yaml
+$ cat ./secret-config/trivy.yaml
+rules:
+  - id: rule1
+    category: general
+    title: Generic Rule
+    severity: HIGH
+    regex: (?i)(?P<key>(secret))(=|:).{0,5}['"](?P<secret>[0-9a-zA-Z\-_=]{8,64})['"]
+    allow-rules:
+      - id: skip-text
+        description: skip text files
+        path: .*\.txt
+enable-builtin-rules:
+  - aws-access-key-id
+  - aws-account-id
+  - aws-secret-access-key
+disable-allow-rules:
+  - usr-dirs
+
+# Pass the above config with `--secret-config`.
+$ trivy fs --secret-config ./secret-config/trivy.yaml /path/to/your_project
+```
+
+## Credit
+This feature is inspired by [gitleaks][gitleaks].
+
+[builtin]: https://github.com/aquasecurity/trivy/blob/{{ git.tag }}/pkg/fanal/secret/builtin-rules.go
+[builtin-allow]: https://github.com/aquasecurity/trivy/blob/{{ git.tag }}/pkg/fanal/secret/builtin-allow-rules.go
+[gitleaks]: https://github.com/gitleaks/gitleaks
+
+[builtin]: https://github.com/aquasecurity/trivy/blob/main/pkg/fanal/secret/builtin-rules.go
+[builtin-allow]: https://github.com/aquasecurity/trivy/blob/main/pkg/fanal/secret/builtin-allow-rules.go

docs/docs/scanner/vulnerability/index.md

@@ -1,4 +1,17 @@
-# Database
+# Vulnerability Scanning
+
+## Overview
+This section describes the overview of vulnerability scanning.
+Trivy detects known vulnerabilities according to the versions of installed packages.
+
+The following packages are supported.
+
+- [OS packages](os.md)
+- [Language-specific packages](language/index.md)
+
+Trivy downloads [the vulnerabillity database](https://github.com/aquasecurity/trivy-db) every 6 hours.
+
+## Database
 Trivy uses two types of databases for vulnerability detection:
 
 - Vulnerability Database
@@ -6,15 +19,15 @@ Trivy uses two types of databases for vulnerability detection:
 
 This page provides detailed information about these databases.
 
-## Vulnerability Database
+### 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).
+For CLI flags related to the database, please refer to [this page](../../configuration/db.md).
 
-### Private Hosting
+#### 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`.
 
@@ -23,16 +36,16 @@ $ 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.
+Please refer to [the documentation](../../advanced/private-registries/index.md) for more details.
 
-## Java Index Database
+### 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
+#### 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.
+Currently, specifying a username and password is not supported.

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

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

docs/docs/scanner/vulnerability/language/java.md

@@ -11,14 +11,14 @@ The following table provides an outline of the features Trivy offers.
 | *gradle.lockfile |           -           | Exclude          |
 
 These may be enabled or disabled depending on the target.
-See [here](../detection/language.md) for the detail.
+See [here](./index.md) for the detail.
 
 ## JAR/WAR/PAR/EAR
 To find information about your JAR[^2] file, Trivy parses `pom.properties` and `MANIFEST.MF` files in your JAR[^2] file and takes required properties[^3].
 
 If those files don't exist or don't contain enough information - Trivy will try to find this JAR[^2] file in [trivy-java-db](https://github.com/aquasecurity/trivy-java-db).
 The Java DB will be automatically downloaded/updated when any JAR[^2] file is found.
-It is stored in [the cache directory](../examples/cache.md#cache-directory).
+It is stored in [the cache directory](../../../configuration/cache.md#cache-directory).
 
 !!! warning "EXPERIMENTAL"
     Finding JARs in `trivy-java-db` is an experimental function.
@@ -26,6 +26,8 @@ It is stored in [the cache directory](../examples/cache.md#cache-directory).
 Base JAR[^2] may contain inner JARs[^2] within itself.
 To find information about these JARs[^2], the same logic is used as for the base JAR[^2].
 
+`table` format only contains the name of root JAR[^2] . To get the full path to inner JARs[^2] use the `json` format.
+
 ## pom.xml
 Trivy parses your `pom.xml` file and tries to find files with dependencies from these local locations.
 
@@ -37,7 +39,7 @@ If your machine doesn't have the necessary files - Trivy tries to find the infor
 
 !!! Note
     Trivy only takes information about packages. We don't take a list of vulnerabilities for packages from the `maven repository`.
-    Information about data sources for Java you can see [here](../detection/data-source.md).
+    Information about data sources for Java you can see [here](./index.md#data-sources).
 
 You can disable connecting to the maven repository with the `--offline-scan` flag.
 The `--offline-scan` flag does not affect the Trivy database.

docs/docs/scanner/vulnerability/language/nodejs.md

@@ -16,7 +16,7 @@ In addition, Trivy scans installed packages with `package.json`.
 | package.json |        -         |    -     |    ✅    |
 
 These may be enabled or disabled depending on the target.
-See [here](../detection/language.md) for the detail.
+See [here](./index.md) for the detail.
 
 ## Package managers
 Trivy parses your files generated by package managers in filesystem/repository scanning.
@@ -44,4 +44,4 @@ Trivy searches for `package.json` files under `node_modules` and identifies inst
 It only extracts package names, versions and licenses for those packages.
 
 
-[tree]: ../examples/report.md#show-origins-of-vulnerable-dependencies 
+[tree]: ../../../configuration/reporting.md#show-origins-of-vulnerable-dependencies 

docs/docs/scanner/vulnerability/language/python.md

@@ -17,16 +17,36 @@ In addition, Trivy supports two formats of Python packages: `egg` and `wheel`.
 | Wheel     |    ✅    |
 
 These may be enabled or disabled depending on the target.
-See [here](../detection/language.md) for the detail.
+See [here](./index.md) for the detail.
 
 ## Package managers
 Trivy parses your files generated by package managers in filesystem/repository scanning.
 
 ### pip
-`requirements.txt` files contain only the direct dependencies and not contain the transitive dependencies.
+`requirements.txt` files usually contain only the direct dependencies and not contain the transitive dependencies.
 Therefore, Trivy scans only for the direct dependencies with `requirements.txt`.
 
-Also, `requirements.txt` files don't contain information about dependencies used for development.
+To detect transitive dependencies as well, you need to generate `requirements.txt` with `pip freeze`.
+
+```zsh
+$ cat requirements.txt # it will only find `requests@2.28.2`.
+requests==2.28.2 
+$ pip install -r requirements.txt
+...
+
+$ pip freeze > requirements.txt   
+$ cat requirements.txt # it will also find the transitive dependencies of `requests@2.28.2`.
+certifi==2022.12.7
+charset-normalizer==3.1.0
+idna==3.4
+PyJWT==2.1.0
+requests==2.28.2
+urllib3==1.26.15
+```
+
+`pip freeze` also helps to resolve [extras](https://packaging.python.org/en/latest/tutorials/installing-packages/#installing-extras)(optional) dependencies (like `package[extras]=0.0.0`).
+
+`requirements.txt` files don't contain information about dependencies used for development.
 Trivy could detect vulnerabilities on the development packages, which not affect your production environment.
 
 License detection is not supported for `pip`.

docs/docs/scanner/vulnerability/os.md

@@ -1,11 +1,19 @@
-# Supported OS
+# OS Packages
+Trivy is capable of automatically detecting installed OS packages when scanning container images, VM images and running hosts.
+This page provides an overview of OS packages in the context of Trivy scans.
 
-The unfixed/unfixable vulnerabilities mean that the patch has not yet been provided on their distribution. Trivy doesn't support self-compiled packages/binaries, but official packages provided by vendors such as Red Hat and Debian.
+## Supported OS
+
+The unfixed/unfixable vulnerabilities mean that the patch has not yet been provided on their distribution.
+To hide unfixed/unfixable vulnerabilities, you can use the `--ignore-unfixed` flag.
+
+Trivy doesn't support self-compiled packages/binaries, but official packages provided by vendors such as Red Hat and Debian.
 
 | OS                               | Supported Versions                        | Target Packages               | Detection of unfixed vulnerabilities |
 |----------------------------------|-------------------------------------------|-------------------------------|:------------------------------------:|
-| Alpine Linux                     | 2.2 - 2.7, 3.0 - 3.17, edge               | Installed by apk              |                  NO                  |
+| Alpine Linux                     | 2.2 - 2.7, 3.0 - 3.18, edge               | Installed by apk              |                  NO                  |
 | Wolfi Linux                      | (n/a)                                     | Installed by apk              |                  NO                  |
+| Chainguard                       | (n/a)                                     | Installed by apk              |                  NO                  |
 | Red Hat Universal Base Image[^1] | 7, 8, 9                                   | Installed by yum/rpm          |                 YES                  |
 | Red Hat Enterprise Linux         | 6, 7, 8                                   | Installed by yum/rpm          |                 YES                  |
 | CentOS                           | 6, 7, 8                                   | Installed by yum/rpm          |                 YES                  |
@@ -21,17 +29,50 @@ 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                  |
 
+## Data Sources
+
+| OS            | Source                                 |
+|---------------|----------------------------------------|
+| Arch Linux    | [Vulnerable Issues][arch]              |
+| Alpine Linux  | [secdb][alpine]                        |
+| Wolfi Linux   | [secdb][wolfi]                         |
+| Chainguard    | [secdb][chainguard]                    |
+| Amazon Linux  | [Amazon Linux Security Center][amazon] |
+| Debian        | [Security Bug Tracker][debian-tracker] |
+|               | [OVAL][debian-oval]                    |
+| Ubuntu        | [Ubuntu CVE Tracker][ubuntu]           |
+| RHEL/CentOS   | [OVAL][rhel-oval]                      |
+|               | [Security Data][rhel-api]              |
+| AlmaLinux     | [AlmaLinux Product Errata][alma]       |
+| Rocky Linux   | [Rocky Linux UpdateInfo][rocky]        |
+| Oracle Linux  | [OVAL][oracle]                         |
+| CBL-Mariner   | [OVAL][mariner]                        |
+| OpenSUSE/SLES | [CVRF][suse]                           |
+| Photon OS     | [Photon Security Advisory][photon]     |
+
+### Data source selection
+Trivy **only** consumes security advisories from the sources listed in the above table.
+
+As for packages installed from OS package managers (`dpkg`, `yum`, `apk`, etc.), Trivy uses the advisory database from the appropriate **OS vendor**.
+
+For example: for a python package installed from `yum` (Amazon linux), Trivy will only get advisories from [ALAS][amazon].
+But for a python package installed from another source (e.g. `pip`), Trivy will get advisories from the `GitLab` and `GitHub` databases.
+
+This advisory selection is essential to avoid getting false positives because OS vendors usually backport upstream fixes, and the fixed version can be different from the upstream fixed version.
+The severity is from the selected data source.
+If the data source does not provide severity, it falls back to [NVD][nvd], and if NVD does not have severity, it will be UNKNOWN.
+
 ## Distributions
 ### CBL-Mariner
-Trivy scans [CBL-Mariner][mariner].
+Trivy scans [CBL-Mariner][cbl-mariner].
 
 #### Support
 The following table provides an outline of the features Trivy offers.
 
 | Version | Container image | Virtual machine | Distroless |  Multi-arch  | Unfixed support |
 |---------|:---------------:|:---------------:|:----------:|:------------:|:---------------:|
-| 1.0     |        ✔        |        ✔        |      ✔     | amd64, arm64 |        ✔        |
-| 2.0     |        ✔        |        ✔        |      ✔     | amd64, arm64 |        ✔        |
+| 1.0     |        ✔        |        ✔        |     ✔      | amd64, arm64 |        ✔        |
+| 2.0     |        ✔        |        ✔        |     ✔      | amd64, arm64 |        ✔        |
 
 ### Examples
 
@@ -42,9 +83,9 @@ The following table provides an outline of the features Trivy offers.
     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)
+    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)
+    Total: 33 (UNKNOWN: 0, LOW: 0, MEDIUM: 15, HIGH: 13, CRITICAL: 5)
     ```
 
 === "rootfs"
@@ -73,8 +114,23 @@ The following table provides an outline of the features Trivy offers.
 [^1]: https://developers.redhat.com/products/rhel/ubi
 [^2]: https://github.com/GoogleContainerTools/distroless
 
-### Data source
-See [here][source].
+[arch]: https://security.archlinux.org/
+[alpine]: https://secdb.alpinelinux.org/
+[wolfi]: https://packages.wolfi.dev/os/security.json
+[chainguard]: https://packages.cgr.dev/chainguard/security.json
+[amazon]: https://alas.aws.amazon.com/
+[debian-tracker]: https://security-tracker.debian.org/tracker/
+[debian-oval]: https://www.debian.org/security/oval/
+[ubuntu]: https://ubuntu.com/security/cve
+[rhel-oval]: https://www.redhat.com/security/data/oval/v2/
+[rhel-api]: https://www.redhat.com/security/data/metrics/
+[alma]: https://errata.almalinux.org/
+[rocky]: https://download.rockylinux.org/pub/rocky/
+[oracle]: https://linux.oracle.com/security/oval/
+[suse]: http://ftp.suse.com/pub/projects/security/cvrf/
+[photon]: https://packages.vmware.com/photon/photon_cve_metadata/
+[mariner]: https://github.com/microsoft/CBL-MarinerVulnerabilityData/
 
-[mariner]: https://github.com/microsoft/CBL-Mariner
-[source]: data-source.md
+[cbl-mariner]: https://github.com/microsoft/CBL-Mariner
+
+[nvd]: https://nvd.nist.gov/

docs/docs/secret/configuration.md

@@ -1,142 +0,0 @@
-# Configuration
-Trivy tries to load `trivy-secret.yaml` in the current directory by default.
-If the file doesn't exist, only built-in rules are used.
-You can customize the config file path via the `--secret-config` flag.
-
-You can see the example [here][examples].
-
-## Custom Rules
-Trivy allows defining custom rules. You can see an example.
-
-``` yaml
-rules:
-  - id: rule1
-    category: general
-    title: Generic Rule
-    severity: HIGH
-    path: .*\.sh
-    keywords:
-      - secret
-    regex: (?i)(?P<key>(secret))(=|:).{0,5}['"](?P<secret>[0-9a-zA-Z\-_=]{8,64})['"]
-    secret-group-name: secret
-    allow-rules:
-      - id: skip-text
-        description: skip text files
-        path: .*\.txt
-```
-
-`id` (required)
-:   - Unique identifier for this rule.
-
-`category` (required)
-:   - String used for metadata and reporting purposes.
-
-`title` (required)
-:   - Short human-readable title of the rule.
-
-`severity` (required)
-:   - How critical this rule is.
-    - Allowed values:
-        - CRITICAL
-        - HIGH
-        - MEDIUM
-        - LOW
-
-`regex` (required)
-:   - Golang regular expression used to detect secrets.
-
-`path` (optional)
-:   - Golang regular expression used to match paths.
-
-`keywords` (optional, recommended)
-:   - Keywords are used for pre-regex check filtering.
-    - Rules that contain keywords will perform a quick string compare check to make sure the keyword(s) are in the content being scanned.
-    - Ideally these values should either be part of the identifier or unique strings specific to the rule's regex.
-    - It is recommended to define for better performance.
-
-`allow-rules` (optional)
-:   - Allow rules for a single rule to reduce false positives with known secrets.
-    - The details are below.
-
-## Allow Rules
-If the detected secret is matched with the specified `regex`, then that secret will be skipped and not detected.
-The same logic applies for `path`.
-
-`allow-rules` can be defined globally and per each rule. The fields are the same.
-
-``` yaml
-rules:
-  - id: rule1
-    category: general
-    title: Generic Rule
-    severity: HIGH
-    regex: (?i)(?P<key>(secret))(=|:).{0,5}['"](?P<secret>[0-9a-zA-Z\-_=]{8,64})['"]
-    allow-rules:
-      - id: skip-text
-        description: skip text files
-        path: .*\.txt
-allow-rules:
-  - id: social-security-number
-    description: skip social security number
-    regex: 219-09-9999
-```
-
-
-`id` (required)
-:   - Unique identifier for this allow rule.
-
-`description` (optional)
-:   - Short human-readable description of this allow rule.
-
-`regex` (optional)
-:   - Golang regular expression used to allow detected secrets.
-    - `regex` or `path` must be specified.
-
-`path` (optional)
-:   - Golang regular expression used to allow matched paths.
-    - `regex` or `path` must be specified.
-
-## Enable Rules
-Trivy provides plenty of out-of-box rules and allow rules, but you may not need all of them.
-In that case, `enable-builtin-rules` will be helpful.
-If you just need AWS secret detection, you can enable only relevant rules as shown below.
-It specifies AWS-related rule IDs in `enable-builtin-rules`.
-All other rules are disabled, so the scanning will be much faster.
-We would strongly recommend using this option if you don't need all rules.
-
-You can see a full list of [built-in rule IDs][builtin] and [built-in allow rule IDs][builtin-allow].
-
-``` yaml
-enable-builtin-rules:
-  - aws-access-key-id
-  - aws-account-id
-  - aws-secret-access-key
-```
-
-## Disable Rules
-Trivy offers built-in rules and allow rules, but you may want to disable some of them.
-For example, you don't use Slack, so Slack doesn't have to be scanned.
-You can specify the Slack rule IDs, `slack-access-token` and `slack-web-hook` in `disable-rules` so that those rules will be disabled for less false positives.
-
-You should specify either `enable-builtin-rules` or `disable-rules`.
-If they both are specified, `disable-rules` takes precedence.
-In case `github-pat` is specified in `enable-builtin-rules` and `disable-rules`, it will be disabled.
-
-In addition, there are some allow rules.
-Markdown files are ignored by default, but you may want to scan markdown files as well.
-You can disable the allow rule by adding `markdown` to `disable-allow-rules`.
-
-You can see a full list of [built-in rule IDs][builtin] and [built-in allow rule IDs][builtin-allow].
-
-``` yaml
-disable-rules:
-  - slack-access-token
-  - slack-web-hook
-disable-allow-rules:
-  - markdown
-```
-
-
-[builtin]: https://github.com/aquasecurity/trivy/blob/main/pkg/fanal/secret/builtin-rules.go
-[builtin-allow]: https://github.com/aquasecurity/trivy/blob/main/pkg/fanal/secret/builtin-allow-rules.go
-[examples]: ./examples.md

docs/docs/secret/examples.md

@@ -1,110 +0,0 @@
-# Examples
-Also see [quick start][quick-start].
-
-## Skip Directories
-Trivy traversals directories and scans all files except those matching the built-in allow rules by default.
-If your have a lot of files in your container image or project, the scanning takes time.
-To make it faster, you can skip traversal in the specific directory.
-Also, it would be helpful if your project contains secrets and certificates for testing.
-
-``` shell
-$ trivy image --skip-dirs /var/lib --skip-dirs /var/log YOUR_IMAGE
-```
-
-``` shell
-$ trivy fs --skip-dirs ./my-test-dir --skip-dirs ./my-testing-cert/ /path/to/your_project
-```
-
-`--skip-files` also works similarly.
-
-## Filter by severity
-
-Use `--severity` option.
-
-``` shell
-$ trivy fs --severity CRITICAL ./
-
-app/secret.sh (secrets)
-=======================
-Total: 1 (CRITICAL: 1)
-
-+----------+-------------------+----------+---------+--------------------------------+
-| CATEGORY |    DESCRIPTION    | SEVERITY | LINE NO |             MATCH              |
-+----------+-------------------+----------+---------+--------------------------------+
-|   AWS    | AWS Access Key ID | CRITICAL |   10    | export AWS_ACCESS_KEY_ID=***** |
-+----------+-------------------+----------+---------+--------------------------------+
-```
-
-## Filter by RuleID
-
-Use `.trivyignore`.
-
-```bash
-$ cat .trivyignore
-
-# Ignore these rules
-generic-unwanted-rule
-aws-account-id
-```
-
-## Disable secret scanning
-If you need vulnerability scanning only, you can disable secret scanning via the `--scanners` flag.
-
-``` shell
-$ trivy image --scanners vuln alpine:3.15
-```
-
-## With configuration file
-`trivy-secret.yaml` in the working directory is loaded by default.
-
-``` yaml
-$ cat trivy-secret.yaml
-rules:
-  - id: rule1
-    category: general
-    title: Generic Rule
-    severity: HIGH
-    regex: (?i)(?P<key>(secret))(=|:).{0,5}['"](?P<secret>[0-9a-zA-Z\-_=]{8,64})['"]
-allow-rules:
-  - id: social-security-number
-    description: skip social security number
-    regex: 219-09-9999
-  - id: log-dir
-    description: skip log directory
-    path: ^\/var\/log\/
-disable-rules:
-  - slack-access-token
-  - slack-web-hook
-disable-allow-rules:
-  - markdown
-
-# The following command automatically loads the above configuration.
-$ trivy image YOUR_IMAGE
-```
-
-Also, you can customize the config file path via `--secret-config`.
-
-``` yaml
-$ cat ./secret-config/trivy.yaml
-rules:
-  - id: rule1
-    category: general
-    title: Generic Rule
-    severity: HIGH
-    regex: (?i)(?P<key>(secret))(=|:).{0,5}['"](?P<secret>[0-9a-zA-Z\-_=]{8,64})['"]
-    allow-rules:
-      - id: skip-text
-        description: skip text files
-        path: .*\.txt
-enable-builtin-rules:
-  - aws-access-key-id
-  - aws-account-id
-  - aws-secret-access-key
-disable-allow-rules:
-  - usr-dirs
-
-# Pass the above config with `--secret-config`.
-$ trivy fs --secret-config ./secret-config/trivy.yaml /path/to/your_project
-```
-
-[quick-start]: ./scanning.md#quick-start

docs/docs/secret/scanning.md

@@ -1,126 +0,0 @@
-# Secret Scanning
-
-Trivy scans any container image, filesystem and git repository to detect exposed secrets like passwords, api keys, and tokens.
-Secret scanning is enabled by default.
-
-Trivy will scan every plaintext file, according to builtin rules or configuration. There are plenty of builtin rules:
-
-- AWS access key
-- GCP service account
-- GitHub personal access token
-- GitLab personal access token
-- Slack access token
-- etc.
-
-You can see a full list of [built-in rules][builtin] and [built-in allow rules][builtin-allow].
-
-!!! tip
-    If your secret is not detected properly, please make sure that your file including the secret is not in [the allowed paths][builtin-allow].
-    You can disable allow rules via [disable-allow-rules][disable-rules].
-
-## Quick start
-This section shows how to scan secrets in container image and filesystem. Other subcommands should be the same.
-
-### Container image
-Specify an image name.
-
-``` shell
-$ trivy image myimage:1.0.0
-2022-04-21T18:56:44.099+0300    INFO    Detected OS: alpine
-2022-04-21T18:56:44.099+0300    INFO    Detecting Alpine vulnerabilities...
-2022-04-21T18:56:44.101+0300    INFO    Number of language-specific files: 0
-
-myimage:1.0.0 (alpine 3.15.0)
-=============================
-Total: 6 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 0, CRITICAL: 2)
-
-+--------------+------------------+----------+-------------------+---------------+---------------------------------------+
-|   LIBRARY    | VULNERABILITY ID | SEVERITY | INSTALLED VERSION | FIXED VERSION |                 TITLE                 |
-+--------------+------------------+----------+-------------------+---------------+---------------------------------------+
-| busybox      | CVE-2022-28391   | CRITICAL | 1.34.1-r3         | 1.34.1-r5     | CVE-2022-28391 affecting              |
-|              |                  |          |                   |               | package busybox 1.35.0                |
-|              |                  |          |                   |               | -->avd.aquasec.com/nvd/cve-2022-28391 |
-+--------------+------------------|          |-------------------+---------------+---------------------------------------+
-| ssl_client   | CVE-2022-28391   |          | 1.34.1-r3         | 1.34.1-r5     | CVE-2022-28391 affecting              |
-|              |                  |          |                   |               | package busybox 1.35.0                |
-|              |                  |          |                   |               | -->avd.aquasec.com/nvd/cve-2022-28391 |
-+--------------+------------------+----------+-------------------+---------------+---------------------------------------+
-
-app/secret.sh (secrets)
-=======================
-Total: 1 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 0, CRITICAL: 1)
-
-+----------+-------------------+----------+---------+--------------------------------+
-| CATEGORY |    DESCRIPTION    | SEVERITY | LINE NO |             MATCH              |
-+----------+-------------------+----------+---------+--------------------------------+
-|   AWS    | AWS Access Key ID | CRITICAL |   10    | export AWS_ACCESS_KEY_ID=***** |
-+----------+-------------------+----------+---------+--------------------------------+
-```
-
-
-!!! tip
-    Trivy tries to detect a base image and skip those layers for secret scanning.
-    A base image usually contains a lot of files and makes secret scanning much slower.
-    If a secret is not detected properly, you can see base layers with the `--debug` flag.
-
-### Filesystem
-
-``` shell
-$ trivy fs /path/to/your_project
-...(snip)...
-
-certs/key.pem (secrets)
-========================
-Total: 1 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 1, CRITICAL: 0)
-
-+----------------------+------------------------+----------+---------+---------------------------------+
-|       CATEGORY       |      DESCRIPTION       | SEVERITY | LINE NO |              MATCH              |
-+----------------------+------------------------+----------+---------+---------------------------------+
-| AsymmetricPrivateKey | Asymmetric Private Key |   HIGH   |    1    | -----BEGIN RSA PRIVATE KEY----- |
-+----------------------+------------------------+----------+---------+---------------------------------+
-```
-
-
-!!! tip
-    Your project may have some secrets for testing. You can skip them with `--skip-dirs` or `--skip-files`.
-    We would recommend specifying these options so that the secret scanning can be faster if those files don't need to be scanned.
-    Also, you can specify paths to be allowed in a configuration file. See the detail [here][configuration].   
-
-## Configuration
-Trivy has a set of builtin rules for secret scanning, which can be extended or modified by a configuration file.
-
-
-## Recommendation
-We would recommend specifying `--skip-dirs` for faster secret scanning.
-In container image scanning, Trivy walks the file tree rooted  `/` and scans all the files other than [built-in allowed paths][builtin-allow].
-It will take a while if your image contains a lot of files even though Trivy tries to avoid scanning layers from a base image.
-If you want to make scanning faster, `--skip-dirs` and `--skip-files` helps so that Trivy will skip scanning those files and directories.
-The usage examples are [here][examples].
-
-`allow-rules` is also helpful. See the [allow-rules][allow-rules] section.
-
-In addition, all the built-in rules are enabled by default, so it takes some time to scan all of them.
-If you don't need all those rules, you can use `enable-builtin-rules` or `disable-rules` in the configuration file.
-You should use `enable-builtin-rules` if you need only AWS secret detection, for example.
-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 `--scanners` flag.
-
-```shell
-$ trivy image --scanners vuln alpine:3.15
-```
-
-
-## Credit
-This feature is inspired by [gitleaks][gitleaks]. 
-
-[builtin]: https://github.com/aquasecurity/trivy/blob/main/pkg/fanal/secret/builtin-rules.go
-[builtin-allow]: https://github.com/aquasecurity/trivy/blob/main/pkg/fanal/secret/builtin-allow-rules.go
-[configuration]: ./configuration.md
-[allow-rules]: ./configuration.md#allow-rules
-[enable-rules]: ./configuration.md#enable-rules
-[disable-rules]: ./configuration.md#disable-rules
-[examples]: ./examples.md
-[gitleaks]: https://github.com/zricethezav/gitleaks