Prepare for v0.63.0 #8915
Closed
DmitriyLewen
started this conversation in
Development
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Draft to collaborate on v0.63.0
📑 Table of Contents
🚀 What's new? 🚀
🏷️ Check for updates and telemetry 🆔
Trivy now checks for updates which includes newer versions, breaking changes, deprecation notices, and other important information. Messages are displayed along with scan results.
Trivy also now collects telemetry in order to improve the product experience.
Both new features can be disabled using the flags:
--disable-telemetry
,--skip-version-check
.More background and context in the following discussions: #8675 #8645
🏝️ Detect licenses in Go vendored modules 🏴☠️
Trivy now scans the
vendor
directory in Go projects to detect licenses for modules vendored viago mod vendor
, ensuring license detection even when modules are not in the default cache directory.Thanks to @oneum20
🍶 Bottlerocket OS support 🚀
Trivy now supports Bottlerocket operating system. Currently, only SBOM generation is supported without vulnerability scanning. See here for more details.
Thanks to @0intro
🎚️ Echo OS support 🧩
Trivy now supports Echo operating system. See here for more details.
Thanks to @orizerah
💽 MinimOS OS support ⛏️
Trivy now supports MinimOS operating system. See here for more details.
Thanks to @Daniel-Wachter
🍔 Bun support↕️
Trivy now supports scanning Javascript projects managed with Bun package manger. See here for more details.
Thanks to @sneaky-potato
📜 Composite licenses classification 📝
Trivy now correctly identifies license category and severity for compound licenses (e.g dual-licence).
Licenses composited with
OR
operator will be classified following the least severe license, while licenses composited withAND
operator will be classified following the most severe license.Thanks to @JonatanLindstrom
🗃️ Free-text license classification 📃
You can now classify licenses by matching a free-text expression or regular expression, using the new
text://
prefix in the license classification configuration file.For example:
See here for more details.
🛰️ Checks can declare compatible Trivy version 🧑🏽🎤
Trivy misconfiguration check authors can now declare the minimum required Trivy version for the check. Since checks are updated and distributed seperately from Trivy, it's possible that a newer check is evaluated by an older Trivy scanner, and this check might depend on newer input schema (i.e lookup an field which isn't there) which the older scanner doesn't support. Previously Trivy silentrly failed those checks, with this recent addition, Trivy will know to skip those checks which it cannot evaluate.
For example, the following check will be enabled only for Trivy versions 1.2.3 and above:
📦 Terraform raw scanning 🔍
Terraform misconfiguration checks now have access to the raw Terraform code, enabling more flexible and powerful checks.
This feature is disabled by default, and can be enabled with the new
--raw-config-scanners=terraform
flag, and specifying theterraform-raw
input selector in the check metadata. When enabled, the raw terraform code is available under the input document which follows the schema: https://github.com/aquasecurity/trivy/blob/main/pkg/iac/rego/schemas/terraform-raw.jsonExample check:
Example config:
Output:
🛠️ Misconfiguration details in JUnit format 🧪
The JUnit format now includes enhanced details for each misconfiguration: the file path and location of the issue, a list of all occurrences, and a relevant code snippet.
Example:

🗂️ Consolidated trusted registry checks into a single check 🧹
Checks
KSV032
,KSV033
,KSV034
, andKSV035
, which previously validated image sources against trusted registries, have been merged into a single check:KSV0125
. The old checks are now marked as deprecated.You can customize the list of trusted registries by custom data to Trivy.
Example data file:
See the documentation to learn more about custom data.
This consolidation simplifies maintenance and makes customization of trusted registries more consistent.
👷♂️ Notable Fixes 🛠️
--compliance
flag #8876fs
/vm
modes #8819relationship
field is missing #8871julia
packages don't supportRelationship
field #8938Beta Was this translation helpful? Give feedback.
All reactions