05 / Security signals
See the risk.
Understand the context.
An available update and a reported vulnerability are different signals. Dep Beacon keeps that distinction close to the dependency.
- Advisory source
- OSV.dev
- Queries
- Enabled by default
Read severity, not just color
Dep Beacon queries OSV for the package and version selected by the declared range, then summarizes advisory details in your editor. Inspect the dependency hover for context.
- Low / medium
- Orange warning signals identify lower-severity advisories that still need review.
- High / critical
- Red error signals give higher-severity findings greater prominence.
- Unknown severity
- Advisory details remain visible as known risk, even when a severity is unavailable.
Control what goes to OSV
OSV checks send package names and selected versions to OSV.dev. Set checkVulnerabilities tofalse when your workspace should not send that information to this external service.
{
"depBeacon.checkVulnerabilities": false
}{
"lsp": {
"dep-beacon": {
"settings": {
"checkVulnerabilities": false
}
}
}
}This disables OSV queries. Dependency metadata requests still go to your configured npm registry; it does not make Dep Beacon an offline tool.