What it checks
Reads composer.lock and package-lock.json in themes and registered directories and looks up known vulnerabilities on OSV.dev. Only package names and versions are sent.
Check ID: deps.osv
composer.lock and package-lock.json files in the scan targets are read, and their packages are looked up on OSV.dev. Only package names and versions are sent.
Development packages are checked only when they are actually installed on the server (in vendor/ or node_modules/ next to the lock file). This check runs only while OSV.dev is allowed under Settings → External services.
What a finding means
The titles, severities and explanations below are the ones shown on the Findings screen.
| Finding | Severity | Meaning |
|---|---|---|
Vulnerable package: … …osv.vulnerable | Critical High Medium Low | … known vulnerabilities: … The highest severity of the package's vulnerabilities on OSV.dev (at least Medium). One level lower for development dependencies. |
Lock file could not be readosv.unreadable | Info | The file is unreadable, too large or not valid JSON, so its packages were not checked. |
Dependencies could not be checkedosv.unavailable | Info | OSV.dev could not be reached: …. Previous results are kept. |
How to fix
The recommended action shown with each finding:
- Vulnerable package: … …
Update … to … or later (e.g. …), deploy the result and run the scan again.
Update … to a version without these vulnerabilities (e.g. …), or replace it if no fix exists. - Lock file could not be read, Dependencies could not be checked
Run the scan again later. You can disable this check in the settings.
Related settings
- Settings → Targets: Themes to scan, Plugins to scan and Directories outside WordPress decide which files are checked. Each registered directory has its own Checks and exclusions.
- Settings → Checks → Enabled checks: switch “Vulnerable dependencies” on or off.
- Settings → External services: OSV.dev. See External services.