Dependency health Check a project Pro coming soon

One manifest. The whole picture.

Check your dependencies together and see what needs attention.

Check a whole project

Paste a package.json, requirements.txt, pyproject.toml, Cargo.toml, go.mod, pom.xml, .csproj, packages.config, Gemfile, Gemfile.lock, composer.json, composer.lock, pubspec.yaml, pubspec.lock, mix.lock or .terraform.lock.hcl — or just names, one per line, saying which registry: pypi:django, npm:django, crates:serde, go:github.com/gorilla/mux. No account, nothing stored but the dependency list, and you get a link you can share.

Terraform checks cover locked providers, not modules or cloud configuration. CDK projects use their package manifests. Keep infrastructure inventories private with Pro private imports →.

i
Paste the whole file: package.json, requirements.txt, pyproject.toml, Cargo.toml, go.mod, pom.xml, .csproj, packages.config, Gemfile, Gemfile.lock, composer.json, composer.lock, pubspec.yaml, pubspec.lock, mix.lock or .terraform.lock.hcl. Terraform covers locked public providers; modules and cloud configuration are not covered. CDK libraries use their language manifests, including npm package.json. Or one package per line with its registry in front — pypi:django, npm:django, crates:serde, go:github.com/gorilla/mux, maven:org.slf4j:slf4j-api, nuget:Newtonsoft.Json, rubygems:rails, terraform:hashicorp/aws — and a version after a space if you like. Bare names are read as PyPI packages. Up to 512 KB; nothing is kept but the names.

Looking for one dependency? Explore packages →