Check any public GitHub repo for vulnerable dependencies
Paste the address of a public GitHub repository. We find every lockfile on its default branch, check each package version against OSV.dev and email you the report: what is affected, in which lockfile, and how to fix it. Free, and no account needed.
How it works
- We look at the default branch. We ask GitHub for the latest commit of the repository's default branch and the list of its files.
- We find the lockfiles. Every supported lockfile in the repository, also in sub-folders of a
monorepo, nearest to the root first. Folders like
node_modulesandvendorare skipped. - We check every exact version against OSV.dev, including indirect (transitive) dependencies, and group what we find per package, with the one upgrade that fixes it.
- The report arrives in your inbox in a minute or two: per lockfile, what is affected, the commands to fix it, and a prompt you can paste into your coding agent.
Which files we read
Only files that record exact versions can be checked. These are the ones we look for, wherever they are in the repository:
- JavaScript and TypeScript:
package-lock.json,npm-shrinkwrap.json,yarn.lock,pnpm-lock.yaml. - Python:
poetry.lock,uv.lock,Pipfile.lock, andrequirements*.txtfiles with==pins. - Go:
go.mod. Rust:Cargo.lock. Ruby:Gemfile.lock. PHP:composer.lock.
A package.json, pyproject.toml, Gemfile, Cargo.toml or
composer.json without a lockfile next to it is listed in the report as "not checked": it only says which
versions you accept, not which ones you install.
Private repositories, and checking every day
This page reads public repositories only. With a free AIssue account you connect GitHub through the AIssue GitHub App and choose which repositories it may read, private ones included. AIssue then checks them every day and emails you when a newly published vulnerability affects one of them.
Prefer not to connect GitHub? The dependency check takes a single lockfile, uploaded or pasted.
Questions
Does it work with private repositories?
Not without an account: we only read public repositories here. With a free AIssue account you connect GitHub through the AIssue GitHub App, choose the repositories (private ones too) and they are checked every day.
Do you clone or keep my code?
No. We list the files of the default branch, download only the lockfiles, and read the package names and versions from them. The repository name, the lockfile paths and the package list are kept for 90 days with your email address, then deleted.
Which branch is checked?
The default branch (usually main or master), at its latest commit when the check runs. The email says which commit was checked.
My repository has several projects. Are they all checked?
Yes: every supported lockfile in the repository is checked (up to 25, nearest to the root first), and the report says which lockfile each vulnerable package comes from. Folders like node_modules and vendor are skipped.
Why is a package.json or pyproject.toml listed as not checked?
Those files list version ranges, not the versions you install. Commit the lockfile next to them (package-lock.json, yarn.lock, poetry.lock, uv.lock...) and run the check again.
Can I check a repository that is not mine?
Yes, any public repository: a library you depend on, or a project you are about to use. To be alerted about new vulnerabilities in your own repositories every day, create a free account.
Related free tools
Dependency vulnerability check
Check requirements.txt, package-lock.json, poetry.lock and more against OSV.dev. Free report by email with fix commands. No account needed.
Package vulnerability database
Look up known vulnerabilities in npm, PyPI, Go, Cargo, RubyGems and Packagist packages, version by version, with the fix. Free, no account.
Last updated .