Prepare for v0.68.0 #9713
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.68.0
📑 Table of Contents
🚀 What's new? 🚀
🧩 Report Metadata Enhancements 📊
This release introduces new fields to the Trivy report format, improving traceability, consistency, and clarity across scan outputs.
Summary of Changes
ReportID— Introduces a UUID (v4) that uniquely identifies each individual scan report, enabling correlation acrossArtifactID— Provides a consistent, unique identifier for the scanned artifact (e.g., image, repository, or filesystem).systems.
Metadata.Reference— Captures the exact image reference used during the scan (e.g.,alpine:3.20), offering clearer context without ambiguity.Together, these additions make it easier to track scan origins, correlate results in external systems, and ensure reports remain uniquely identifiable — even when multiple scans target the same artifact.
Example Output
{ "SchemaVersion": 2, "ReportID": "278d4718-2366-46d0-8525-fc288c4eb5f9", "ArtifactID": "sha256:055936d39205...", "ArtifactName": "debian:11", "ArtifactType": "container_image", "Metadata": { "ImageID": "sha256:e7b300aee9f9b...", "Reference": "debian:11", "RepoTags": ["debian:latest", "debian:11"] } }Usage
These fields are automatically included in JSON and table outputs.
No user action is required to enable them.
🐳 Docker Archive RepoTags Support 🏷️
Trivy now preserves image repository tags when scanning Docker archives (
.tarfiles).This enhancement applies automatically when scanning Docker archives created via:
docker saveskopeo copy docker://... docker-archive:...Before
After
🧩 Change Artifact Type for Git Repositories 📁
When scanning a directory using
trivy fs, Trivy now automatically sets the artifact type torepositoryif the target is a Git repository. This behavior is automatic — no configuration needed.Summary of Changes
ArtifactTypefromfilesystem→repositorywhen Git information is found.filesystem.Example
Before
{ "ArtifactType": "filesystem", "Metadata": { "RepoURL": "https://github.com/aquasecurity/trivy-test-repo/", "Branch": "main", "Tags": ["v0.0.1"], "Commit": "8a19b492a589955c3e70c6ad8efd1e4ec6ae0d35", "CommitMsg": "Update README.md", "Author": "Teppei Fukuda <[email protected]>", "Committer": "GitHub <[email protected]>" } }After
{ "ArtifactType": "repository", "Metadata": { "RepoURL": "https://github.com/aquasecurity/trivy-test-repo/", "Branch": "main", "Tags": ["v0.0.1"], "Commit": "8a19b492a589955c3e70c6ad8efd1e4ec6ae0d35", "CommitMsg": "Update README.md", "Author": "Teppei Fukuda <[email protected]>", "Committer": "GitHub <[email protected]>" } }🌳 Dependency tree for *.deps.json files 📦
Trivy can now build a dependency tree for .NET *.deps.json files.
It also detects the project’s package (RootRelationship), as well as direct and indirect dependencies.
Thanks to @alexinslc
⚙️ Remote repositories from settings.xml files 🫙
Trivy now uses remote repositories from
settings.xmlfiles when scanningpom.xmlfiles.Thanks to @ricardo-kh
📜 Separate SPDX IDs can be use in ignore SPDX expression 🪪
It’s no longer necessary to specify each SPDX expression individually to ignore them.
You can specify all included SPDX IDs, and if Trivy finds all of them in an expression, it’ll ignore that license.
For example you can use
--ignored-licenses LGPLv2+,MITto ignoreMIT AND GPL-2.0-or-laterexpression.Thanks to @yutatokoi
Trivy can now limit the number of Rego compile errors during policy compilation. You can control this using the
--rego-error-limitflag. If the number of errors exceeds the specified limit, Trivy will stop the scan. Setting--rego-error-limit 0enforces strict checking and disallows any compile errors.The default value is defined internally via CompileErrorLimit.
🧩 More accurate YAML snippets in diagnostics ✅
Trivy now captures the correct start line for map nodes in YAML manifests. Previously, snippets began at the first value and did not include the key, which could make diagnostics less clear.
Before:
After:
🏎️ Performance 🏎️
👷♂️ Notable Fixes 🛠️
--detection-priority comprehensiveflag. #9609 Thanks to @raghur-orcaBeta Was this translation helpful? Give feedback.
All reactions