Learn › What Bugstack does

Automated vulnerability remediation: from an advisory to a patch

Automated vulnerability remediation means a tool does more than tell you a package is vulnerable: it opens the change that fixes it. Bugstack checks your packages against published advisories every four hours. When one of yours is affected, it opens a pull request that moves the package to the smallest version that closes the advisory, with the lockfile rebuilt.

The gap between a scanner and a fix

Most teams already have something that reports vulnerable packages. The report is not the problem. The problem is the list: forty findings, each needing someone to work out which version is safe, whether it breaks anything, and how to get the lockfile to agree.

So the list grows. Remediation is the part that takes a person’s afternoon, and it is the part worth automating.

What Bugstack does

Bugstack does autonomous software maintenance. For vulnerabilities:

  1. It scans every four hours. It reads your package files and compares them with OSV, the public database of open-source vulnerabilities. It reads package.json, requirements.txt, Gemfile and go.mod.
  2. It finds the smallest safe version. The target is the lowest version that fixes every advisory affecting the one you have installed.
  3. It opens a pull request for npm packages, with the lockfile rebuilt.
  4. It says what the upgrade crosses. If the fix needs a new major version, the pull request says so and tells you to read the release notes.
  5. It checks afterwards. After the pull request merges, the next scan confirms the advisory is gone.

A real one from our own repository upgraded a package by six major versions to close five advisories. Bugstack opened it, flagged that it crossed a major version, and left the merge to a person.

What you see in the pull request

  • Each advisory, with its identifier, severity and the versions it affects
  • Why this version was chosen
  • Whether the package runs in production or only in development
  • Which files change
  • What the scan could not read, so you know what is not covered

Where it stops

SituationWhat happens
Vulnerable npm packageA pull request with the upgrade
Vulnerable Python, Ruby or Go packageA finding on your Security page. No pull request yet
Fix needs a major versionThe pull request opens and waits for you
The lockfile cannot be rebuiltNo pull request, because it would fail your install
A flaw in your own codeFound by a security audit, not by this scan

Who merges

You do, by default. Security upgrades follow the same autonomy level and proof setting as every other change, and a major version always waits unless you change that.

How to start

  1. Sign in with GitHub and start the 14-day trial. It includes $50 of credit.
  2. Install the Bugstack GitHub App on your repository.

The first scan runs when the repository is connected. No SDK is needed. For flaws in your own code, run a security audit; your first one is on us.

Questions

How is this different from a vulnerability scanner?

A scanner gives you a list. Bugstack gives you the list and, for npm packages, the pull request that closes each item, with the right version already worked out and the lockfile rebuilt.

How quickly does it react to a new advisory?

It scans every four hours, so a newly published advisory that affects you is picked up within that window.

Does it patch vulnerabilities in my own code?

Package advisories are handled by this scan. Problems in code you wrote are the job of the security audit, which tries to prove each problem and starts a fix for what it finds.

See it work on your own code.

$100 a month

Includes $100 of usage credit every month. Start with a 14-day trial: $50 of credit and a first security audit on us. A card is required.