From: Ross Burton <ross.burton@arm.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 3/3] classes/sbom-cve-check: add variable to control the scope of the CVE scan
Date: Thu, 9 Apr 2026 17:26:22 +0100 [thread overview]
Message-ID: <20260409162622.3307731-3-ross.burton@arm.com> (raw)
In-Reply-To: <20260409162622.3307731-1-ross.burton@arm.com>
Unless told otherwise, sbom-cve-check will only report on issues found
in target recipes. Whilst this is the behaviour we want for image-based
scanning, it's not the designed bevhaviour for recipe-based scanning.
Add a new variable SBOM_CVE_CHECK_SCAN_SCOPE that is used as the value
passed with --export-process-native. Default this to "target" so the
normal behaviour is unchanged, but set it to "both" in the
sbom-cve-check-recipe class.
[1] https://sbom-cve-check.readthedocs.io/en/latest/export.html#export-options
Signed-off-by: Ross Burton <ross.burton@arm.com>
---
meta/classes/sbom-cve-check-common.bbclass | 9 ++++++++-
meta/classes/sbom-cve-check-recipe.bbclass | 3 +++
2 files changed, 11 insertions(+), 1 deletion(-)
diff --git a/meta/classes/sbom-cve-check-common.bbclass b/meta/classes/sbom-cve-check-common.bbclass
index 3db189d60de..6963ad71c61 100644
--- a/meta/classes/sbom-cve-check-common.bbclass
+++ b/meta/classes/sbom-cve-check-common.bbclass
@@ -6,6 +6,10 @@ require conf/sbom-cve-check-config.inc
SBOM_CVE_CHECK_DEPLOYDIR = "${WORKDIR}/sbom-cve-check/image-deploy"
+SBOM_CVE_CHECK_SCAN_SCOPE ?= "target"
+SBOM_CVE_CHECK_SCAN_SCOPE[doc] = "Whether to scan target and native, just target, or just native. \
+ Valid values are both, target, native."
+
SBOM_CVE_CHECK_EXTRA_ARGS[doc] = "Allow to specify extra arguments to sbom-cve-check. \
For example to add export flags for filtering (e.g., only export vulnerable CVEs). \
"
@@ -54,6 +58,7 @@ def run_sbom_cve_check(d, sbom_path, export_base_name, export_link_name=None):
dl_db_dir = d.getVar("SBOM_CVE_CHECK_DEPLOY_DB_DIR")
out_deploy_dir = d.getVar("SBOM_CVE_CHECK_DEPLOYDIR")
+ scan_scope = d.getVar("SBOM_CVE_CHECK_SCAN_SCOPE")
export_files = []
for export_var in d.getVar("SBOM_CVE_CHECK_EXPORT_VARS").split():
@@ -70,7 +75,9 @@ def run_sbom_cve_check(d, sbom_path, export_base_name, export_link_name=None):
d.expand("${STAGING_BINDIR_NATIVE}/sbom-cve-check"),
"--sbom-path",
sbom_path,
- "--disable-auto-updates"
+ "--disable-auto-updates",
+ "--export-process-native",
+ scan_scope,
]
for export_type, export_file, export_link in export_files:
diff --git a/meta/classes/sbom-cve-check-recipe.bbclass b/meta/classes/sbom-cve-check-recipe.bbclass
index 904ce57f5cc..c80b8ac83ff 100644
--- a/meta/classes/sbom-cve-check-recipe.bbclass
+++ b/meta/classes/sbom-cve-check-recipe.bbclass
@@ -9,6 +9,9 @@
inherit sbom-cve-check-common
+# Recipe-based scanning should cover both target and native components.
+SBOM_CVE_CHECK_SCAN_SCOPE = "both"
+
python do_sbom_cve_check_recipe() {
"""
Task: Run sbom-cve-check analysis on a recipe SBOM.
--
2.43.0
prev parent reply other threads:[~2026-04-09 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 16:26 [PATCH 1/3] python3-sbom-cve-check: move from devtools/python to devtools/sbom-cve-check Ross Burton
2026-04-09 16:26 ` [PATCH 2/3] python3-sbom-cve-check: fix the version attribute in the Yocto-style JSON Ross Burton
2026-04-09 16:26 ` Ross Burton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260409162622.3307731-3-ross.burton@arm.com \
--to=ross.burton@arm.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox