For indie developers, freelancers and agencies

Every project you've shipped, checked for vulnerable packages.

Sign in with GitHub, pick your repos, and NPMscan shows which ones depend on vulnerable or outdated npm, Composer, Python, Ruby, Go, Java or .NET packages, with the worst first. Built for people with more projects than time.

No access tokens to create, no credit card. Or scan a public repo without signing up.

Works withnpmYarnpnpmComposerPythonRubyGoJava.NETDocker
JavaScript and PHP

One report for every lockfile in the repo

NPMscan reads the lockfile each project already commits, so it checks the versions you actually install. A Laravel API and the Vite front end beside it show up in the same report, with the right install command for each.

npmpackage-lock.jsonLockfile versions 1 to 3, workspaces included.
Yarnyarn.lockYarn 1 and Yarn Berry lockfiles.
pnpmpnpm-lock.yamlpnpm 7, 8 and 9 lockfiles, monorepos included.
Composercomposer.lockLaravel, Symfony and any project with a composer.json.
Pythonrequirements.txt · poetry.lock · uv.lockpip, Poetry, uv and Pipenv projects, from pyproject.toml, Pipfile or requirements files.
RubyGemfile.lockRails and any Bundler project, with exact versions from Gemfile.lock.
Gogo.modGo modules: go.mod pins every module the build uses, indirect ones included.
Javapom.xml · build.gradle · gradle.lockfileMaven and Gradle projects. Versions set by a parent POM or BOM are not read yet.
.NETpackages.lock.json · .csprojNuGet packages from project files, Directory.Packages.props and packages.config, with exact versions from packages.lock.json.
DockerDockerfile · compose.ymlFlags node, php, python, postgres, mysql and other official base images on a release that no longer gets security fixes.
PHP and Node versionscomposer.json · .nvmrc · enginesFlags a declared version that no longer gets security fixes.
How the PHP and Composer checks work

Dependabot tells you about one repo at a time. You have twenty.

Side projects, client sites, things you shipped last year and forgot about. NPMscan puts all of them on one page.

Every repo in one view

Personal projects, client work and organisation repos side by side, worst first.

Known vulnerabilities

The exact versions in your lockfile, including packages your dependencies pull in, checked against the OSV.dev database with the version that fixes each one.

Outdated packages

See which packages are behind and by how much, so you can update before it becomes urgent.

Old runtimes and images

A warning when a project declares a PHP or Node version, or uses a Docker base image, that has stopped getting security fixes, or soon will.

A score to sort by

A 0 to 100 health score per project tells you where to spend your next hour.

One email a week tells you which project needs you

Every week NPMscan rescans your projects and sends a short summary. New advisories come first, with the package, the project it's in and a link to the details. When nothing changed, the email says so in one line.

No dashboard to remember to open, and it's included on every plan, Free too.

NPMscanMon 09:00

2 new vulnerabilities in your projects this week

This week's scan found 2 new vulnerabilities that weren't there last week.

  • CRITICAL next@14.1.0 in client-shop
  • HIGH axios@1.6.0 in client-shop
  • client-shop4 vulnerable packages
  • marketing-siteNo known vulnerable packages
  • booking-appNo known vulnerable packages

Set up in a minute

  1. 1

    Sign in with GitHub

    Allow access to your repos once. NPMscan only reads dependency files, and personal and organisation repos both work.

  2. 2

    Pick your projects

    Your most recently updated repos are selected for you. Change them if you like.

  3. 3

    Watch the first scan

    Results appear while you wait. After that we rescan every week and email you what changed.

Priced per project, not per developer

Start free. Upgrade when you have more to watch.

Free$0
  • Up to 3 projects
  • Weekly rescan and email summary
Indie$5 /month
  • Up to 15 projects
  • Automatic weekly scans
Agency · Recommended$29 /month
  • Up to 75 projects
  • Automatic weekly scans
Studio$79 /month
  • Unlimited projects
  • Automatic weekly scans

Check one package by hand

Every known advisory for an npm, Composer, PyPI, RubyGems, Go, Maven or NuGet package, which versions it affects and the release that fixes it.

Questions

What access does NPMscan need?

Access to your repositories, granted when you connect GitHub. GitHub labels this "full control of private repositories", because apps that connect this way have no read-only option for private repos. NPMscan only scans the projects you pick and only reads dependency files such as package.json, lockfiles, composer.json, Python, Ruby, Go, Java and .NET package files and Dockerfiles. It never writes to your repos, never stores your source code, and you can revoke access from GitHub at any time.

Which projects can it scan?

npm, Yarn and pnpm projects today, including monorepos. NPMscan reads your lockfile for exact versions; without one it checks the lowest version each range allows. Composer projects too: NPMscan reads composer.lock and checks each package for known vulnerabilities. Python projects as well: requirements.txt, pyproject.toml and Pipfile, with exact versions from poetry.lock, uv.lock or Pipfile.lock. Ruby projects from Gemfile.lock, Go modules from go.mod, Java projects from pom.xml, build.gradle and gradle.lockfile, and .NET projects from .csproj files and packages.lock.json. It also warns when a project declares a PHP or Node version, or a Docker base image such as php:8.1 or postgres:12, that no longer gets security fixes.

Do I still need Dependabot?

Keep it for update pull requests. NPMscan gives you the overview across all your repos that Dependabot does not.

How often are projects scanned?

Whenever you click Scan, and automatically once a week on every plan, with an email summary of anything new.

Can I cancel anytime?

Yes. Cancel from Settings and keep your plan until the end of the billing period.