Documentation / Field guide
A clearer view of your dependencies.
Read the signal. Choose your next update. Keep the decision beside the manifest you are already editing.
- Editors
- VS Code + Zed
- Packages
- npm ecosystem
- Security data
- OSV.dev
Find your next step
From first install to workspace policy.
Install Dep Beacon
Choose your editor and open your first manifest.
Work in VS Code
Read inline signals, inspect hovers, and choose an update.
Work in Zed
Use native diagnostics, code actions, and optional inlay hints.
Connect your workspace
Understand default catalogs, named catalogs, and shared policy.
Read security signals
Separate available updates from reported vulnerability risk.
Make it yours
Adjust registry, privacy, display, and installation settings.
Read the signal
Dep Beacon combines npm metadata, semver-aware update targets, pnpm catalog resolution, and OSV advisories. Version status and security risk stay distinct, so you can decide what needs attention.
- Up to date
- Your declared range already accepts the latest stable version.
- Update available
- A newer target is available. Choose patch, minor, major, or latest.
- Needs attention
- Review missing packages, invalid ranges, or reported security risk.
At home in your manifests
package.json- Dependency sections, npm overrides, Yarn resolutions, and pnpm-specific blocks.
pnpm-workspace.yaml- Default and named catalogs, overrides, and package extensions. The
.ymlextension works too. - Your editor
- Inspect a dependency, choose an update, or use VS Code commands to refresh signals, sort manifests, and run installs.