Live security checks for npm and PyPI packages. Your AI confirms a package is real and safe before installing it, and audits a whole project in one call.
AI coding tools learn about packages from training data that is months or years old. They recommend versions with known holes, and sometimes invent package names that do not exist. Attackers register those invented names and wait.
Dependency Check gives your AI current answers. Before installing anything it can confirm the package is real, see when it was first published and how widely it is used, and check it against known vulnerabilities and malware reports. For a whole project, it reads the lockfile and returns a short list ordered by real risk, not hundreds of unranked warnings.
It reads package-lock.json, package.json, yarn.lock, pnpm-lock.yaml and requirements.txt.
Data comes live from OSV.dev, CISA's Known Exploited Vulnerabilities list, FIRST's EPSS scores and the npm and PyPI registries. There is no login. Package names and versions are looked up and then discarded; nothing you send is stored or logged.
Need checks like this wired into your own build pipeline or internal registry? We build private MCPs for that.
Every answer comes from these sources. We read from them and pass on what they say; we do not add data of our own.