In team settings, turn vulnerability scanning on or off. Turning it on includes eligible existing and future CycloneDX and SPDX documents. A document’s switch can exclude it or follow the team setting.
Only team owners and admins can change this preference. You need document editing permission to change this preference.
Eligible SBOMs may be checked after upload, author edits and refreshes. Checks use Google’s OSV service and can send package names, ecosystems and versions. These details can reveal the software you use. Unmarked private names may be included; sent requests cannot be recalled.
Package identity data sent to OSV is limited to ecosystem, package name and version. Package identities with explicit private purl/location markers, and unsupported ecosystems, are excluded. Private packages without these markers may be sent.
Scanner results can create attributed document versions visible to readers. Author entries and VEX are preserved. A finding that disappears means it was no longer detected. A disappeared finding means no longer detected; it does not prove that the vulnerability was fixed.
Scanning depends on your plan’s document allowance and service availability. Protected documents, signed sources, URL-managed sources and unsupported formats are excluded. See Scan history for attempts, failures and coverage; an enabled switch does not confirm a completed scan.