v0.54.0 #7268
aqua-bot
announced in
Announcements
v0.54.0
#7268
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
📑 Table of Contents
--vuln-type
flag renamed into--pkg-types
✅pnpm-lock.yaml
files 📜🛫 Deprecation notice 🌆
🐹
--vuln-type
flag renamed to--pkg-types
✅--vuln-type
flag was added in one of the first versions of Trivy when Trivy was only a vulnerability scanner.Over time, the main use cases became centered around SBOM and Packages, and so the purpose of this flag became more about package filtering. To reflect that, we are renaming
--vuln-type
flag to--pkg-types
flag.--vuln-type
flag is now marked as deprecated and will be removed over time.🚀 What's new? 🚀
🕸️ VEX Hub Support 📡
This update introduces VEX Hub integration into Trivy using the
--vex repo
flag. Trivy can now automatically discover and apply VEX data during vulnerability scans, leveraging community-maintained VEX information to filter out non-exploitable vulnerabilities. This greatly helps to reduce noise in vulnerability scan results.--vex repo
creates the default configuration file in the first run. While the default config refers to VEX Hub, you can also use other VEX Repositories complying with VEX Repository Specification.See here for more details.
For OSS maintainers: please consider publishing VEX.
📄 VEX Attestations from OCI Registries 🌐
Trivy can now automatically retrieve and apply VEX (Vulnerability Exploitability eXchange) attestations from OCI registries during container image vulnerability scans using the
--vex oci
flag. This feature leverages VEX data to filter out non-exploitable vulnerabilities more effectively.See here for more details.
📦 Package Relationships Filter 🔄
This update introduces the
--pkg-relationships
flag, allowing users to filter vulnerabilities by package relationships. This flag provides more refined vulnerability reporting by focusing on direct or indirect dependencies.Note: The
--pkg-relationships
flag cannot be used with--dependency-tree
,--vex
, or SBOM formats (spdx, spdx-json, cyclonedx, github).Read more here.
🦎 Support for Tumbleweed OpenSUSE ✨
Trivy now supports package and vulnerability detection for
Tumbleweed OpenSUSE
юThanks to @msmeissn
🖥️ Support for Azure Linux 3.0 🦋
Now Trivy supports
Azure Linux 3.0
(previouslyCBL-Mariner
).Thanks to @tofay
📋 License Detection for
pnpm-lock.yaml
files 📜Trivy now parses
package.json
files from thenode_modules
directory to determine the licenses of installed packages.Thanks to @oscarbc96
🔓 Vulnerability support for SPDX formats 📕
Trivy can now include detected vulnerabilities in SPDX reports. Vulnerabilities are added as
externalRefs
, as described in SPDX Spec Appendix K.Note that vulnerability scanning is disabled by default for SBOM generation (when --format=SPDX/CycloneDX), but you can manually enable the vulnerability scanner using the
--scanners vuln
flag.Thanks to @goneall
🔖 Image labels in CycloneDX and SPDX formats 🏷️
Trivy now adds information about the scanned container image in CycloneDX and SPDX reports. This includes the Tag, DiffID, ImageID, and Labels of the scanned image.
🪭 Private image scanning in the Azure China ☁️
You can now authenticate against Azure Container Registry in Azure China cloud, for scanning private images.
Thanks to @admanb
👷♂️ Notable Fixes 🛠️
.deps.json
files asDev
#70790-9a-zA-Z
before secret #7176latest
is used as a package version #6747--tf-vars
#7084bytes.Index
inemptyLineSplit
to cut allocation #7065Beta Was this translation helpful? Give feedback.
All reactions