Skip to main content
Menu

Check pull requests with cve.now

Install the cve.now GitHub App and each pull request on the repositories you pick gets a check named cve.now. It fails when the pull request adds a dependency with a known high or critical vulnerability, or one on CISA's KEV list. It is free and needs no workflow file or token.

1Setup

Sign in with your Sazabi account

Sign in at cve.now/sign-in. With no Sazabi account yet, the next screen creates one, free. Your projects are Sazabi projects, so the repositories you add here show up in Sazabi too.

Sign in

2Setup

Connect GitHub

Open Account, then Projects, choose a project and select Connect GitHub. GitHub asks which repositories the cve.now App may use; pick the ones to check. An owner or admin of the organization does this step. If the App was installed before the check existed, the project page offers Approve pull request checks, which grants the new permissions.

3Setup

Add the repository to the project

Under Add a repository, choose the repository. cve.now reads its lockfiles, lists the CVEs that affect them on the project page, and from then on checks the repository's pull requests.

4Setup

Open a pull request that changes a lockfile

The cve.now check appears on the pull request within about a minute. Its summary lists every new finding, and each one is an annotation on the lockfile. GitHub's Re-run button runs the check again.

What fails

Only what the pull request adds

The check fails when the pull request adds a finding at high or critical severity, or one on the KEV list, in a package your code ships. Findings that are already on the target branch are counted but never fail it. A finding in a development-only package is a warning. An upgrade that leaves a package with fewer findings is a net improvement and passes, unless a remaining finding is on KEV or is malware.

Ignore

Ignore a finding

Put a .cve-now-ignore file at the repository root, or in the directory of a lockfile to cover only that one. List one vulnerability id per line (a CVE or GHSA id, as shown on the check), with a reason after a # if you want one. An ignored finding is listed as ignored and no longer fails the check.

Merging

Make the check required

It blocks nothing by default. To block merges on it, add cve.now as a required status check in a branch protection rule or ruleset on GitHub. GitHub lists a check there once it has run on the repository.

Access

What the App can see

Read-only access to repository contents, metadata and pull requests, and write access to checks. It reads only lockfiles and the manifests that label development-only packages, never your code. For a pull request, cve.now sends nothing outside its own systems and keeps no lockfile contents. For a repository you add to a project it keeps the parsed list of package names and versions, to show the project's CVEs, never the file. Remove the App at any time in your GitHub settings under Applications.

Limits

When a lockfile isn't checked

A lockfile with more than 10,000 packages, or one cve.now can't read, is not checked. The check names it in the summary and adds the count to its title; when nothing else in the pull request was checked, it finishes neutral instead of green. cve.now reads npm, bun, pnpm and yarn lockfiles, plus the Python, Rust, Go, Ruby, Elixir, Nix, PHP, .NET and Gradle ones. Pull requests from GitHub only for now.