Vulnerability scanning (CVE)
The CVE in a package you did not know you had
LaraBug reads your composer.lock and tells you which of your dependencies have known vulnerabilities, how bad each one is, and the version that fixes it. Included in every paid plan.
✔︎ 14-day free trial ✔︎ No credit card required
Vulnerability scanning (CVE)
From the lockfile to the fix
- Composer composer.lock, read where it already is.
- npm package-lock.json, yarn.lock and pnpm-lock.yaml.
- Nightly rescans Checked against the Packagist and OSV advisories every night.
- New advisories A new advisory rescans every application that has the package.
- One issue per application Every vulnerable package, its severity and the version that fixes it.
- The fix as a pull request Open the version bump as a draft pull request.
In the same list as everything else
Findings arrive as issues, next to your exceptions, with the severity, the affected range and the first safe version. They are rescanned when the advisory database moves, not only when you deploy, and they snooze, assign and notify through the same channels your exceptions use.
Keep reading
- Alerts and integrations The right alert, in the right channel Slack, Discord, Teams, webhooks and email. Explore
- AI and MCP Your agent can read your errors Let Claude or Cursor read your issues. Explore
- Issue tracking Every error, with the context to fix it Every exception, grouped and traced. Explore
Catch the next bug before your users do
Nathan marked it fixedTwo minutes to install, a free plan that stays free, and your data kept in the EU. Teams have trusted LaraBug with their Laravel errors since 2016.