Free, open-source VS Code extension · MIT

Know the moment a dependency turns against you.

DepSentinel watches every package in your workspace — including the sub-dependencies you never chose — and flags malicious releases, typosquats, hijacked packages and the CVEs attackers are exploiting right now. In your editor, before you commit.

Install for VS Code → See how attacks work
✓Zero sign-upInstall and it's already watching
✓KeylessFree public data, no API key
✓Fully privateNothing about you phoned home
package.jsoncheckout-service {{ scanLabel }}
{{ l.n }} {{ l.t }}
{{ l.flagKind }}{{ l.flagText }}
⎇ main✕ {{ errCount }}! {{ warnCount }}DepSentinel
Malicious package found
flatmap-stream@0.1.1, pulled in by event-stream@3.3.6. Remove it and rotate credentials on this machine.
Show findingsOpen report
{{ ecoCount }}
ecosystems, one extension — every lockfile you use
{{ sigCount }}
behavior signals for attacks with no CVE
Hourly
re-checks, plus every manifest change
0 bytes
of your source code sent anywhere
{{ e.n }} {{ e.f }}
01 — The problem

You chose a dozen packages. You installed hundreds.

Most of the code in your app was written by strangers, and most of it arrived as sub-dependencies you never picked. Attackers don't break into your app — they poison something it depends on, and your own npm install does the rest.

One bad package is enough. It runs with your permissions, on your laptop and your build servers, with your tokens, keys and customer data in reach.

$ npm install {{ gStatus }}
{{ g1n }}
you chose
{{ g2n }}
came along for the ride
{{ g3n }}
is malicious
☠ flatmap-stream@0.1.1 — you never installed this
your-app› event-stream@3.3.6› flatmap-stream@0.1.1
02 — How attacks work

Five ways a dependency gets you.

Real attacks on real companies. Pick one to watch it unfold.

{{ cur.pkg }}{{ progressLabel }}

{{ cur.title }}

{{ s.text }}

✓ DepSentinel flags it
{{ cur.caught }}
03 — What to fix first

Not every critical CVE is an emergency. Some are on fire.

A list sorted by severity hides what matters. DepSentinel ranks by real-world risk, so the first item is the one to fix today.

{{ c.pos }} {{ c.pkg }} {{ c.kev }} {{ c.sev }} · {{ c.ctx }} EPSS {{ c.epss }}
#PackageCVESeverityKEVEPSSContext
{{ c.pos }} {{ c.pkg }} {{ c.cve }} {{ c.sev }} {{ c.kev }} {{ c.epss }} {{ c.ctx }}

Exploited in the wild. Listed in CISA's Known Exploited Vulnerabilities catalog — attackers are using it now.

EPSS. The estimated chance of exploitation in the next 30 days, updated daily by FIRST.org.

Context. Runtime or dev-only? Direct or deep? Is there an easy, same-major fix?

Real packages and CVEs. EPSS values as seen in a scan in November 2026; they change daily.

04 — Why developers use it

A security teammate that never sleeps and never slows you down.

{{ f.tag }}

{{ f.title }}

{{ f.body }}

What gets caughtCVE-only check DepSentinel
{{ r.what }}{{ r.cve }} ✓Caught
6 of 6 · free, MIT
05 — Guard the pipeline

Fail the build before it ships.

The same engine runs as a CLI. Add it to CI and a malicious or actively exploited dependency can't sneak into a release.

→Exit code 1 at or above the level you choose
→SARIF for GitHub code scanning, Markdown for PR comments
→--no-exploit-data for offline or air-gapped runners
ci · build #482{{ ciStatus }}
# .github/workflows/deps.yml
- name: Scan dependencies
  run: node /tmp/ds/dist/cli.js . --fail-on high --sarif ds.sarif
{{ o.t }}
06 — Private by design

Security tooling you don't have to worry about.

Names and versions only

That's all that leaves your machine, plus public CVE ids for EPSS. Never source code, file paths or credentials.

Never runs your code

Manifests are read as text, with size limits and workspace-only file access. Works in Restricted Mode.

HTTPS only

Including every redirect. Plain HTTP is allowed only for a localhost mirror.

Open source, MIT

Read every line. Free data sources: OSV.dev, deps.dev, CISA KEV, FIRST EPSS.

07 — Where it runs

Two ways to use it today. More on the way.

Available now

VS Code extension

Inline warnings, one-click fixes, the findings view and the interactive report. Starts watching the moment you open a project.

Install from Marketplace →
Available now

Command-line tool

The same engine for CI and terminals. Fail builds on risky dependencies and export SARIF, Markdown or JSON.

Read the CLI docs →
Coming soon

More editors & features

New editor extensions and features are in the works. Star the repo to follow along and hear first when they ship.

★ Watch on GitHub →

Your next npm install deserves a guard.

Install in seconds. No setup — open a project and DepSentinel starts watching.