Automatic vulnerability scanning for your dependencies

Published on 2 min read

Every deploy on MyBotCloud now runs through a dependency scan via OSV.dev, naming the exact library and the version to upgrade to — without blocking your deploy or touching your code.

Every application on MyBotCloud — Discord bot or AI agent — is now scanned automatically for dependencies with known, public vulnerabilities, with nothing to configure.

What happens

After every successful deploy (from the dashboard, the CLI, the VS Code extension or MCP), the platform reads your project's package.json/package-lock.json (Node.js) or requirements.txt (Python) and checks it against OSV.dev, the public vulnerability database maintained by Google and package maintainers — the same source behind tools like Dependabot.

If a dependency has a known vulnerability, the warning shows up in three places:

  1. Right on the deploy screen, as soon as the scan finishes (a few seconds after "Succeeded");
  2. On the Manage → Details tab, with its severity (low, medium, high or critical);
  3. On the app's Discord webhook, configured in the Alerts tab, if you have one set.

In all three, the warning is specific — the library's name, the version found, and which version to upgrade to:

lodash 4.17.15: update to version 4.18.0 or later

Apps already live are also re-checked once a day, because a CVE can be published after your deploy — without you having to redeploy anything.

What it doesn't do

  • It doesn't block your deploy. The app goes live normally; the warning is informational, the same way GitHub's Dependabot warns without blocking a merge.
  • It doesn't change your code. Upgrading the dependency is your call — edit the version in your project and redeploy (the Update tab) for the warning to clear on the next scan.
  • It never runs any of your code. The scan only reads manifest files, never installs or executes anything — it's a text lookup against a public database.

Why it's worth a look

An outdated dependency is the most common entry point for security incidents in small projects — not because anyone wrote bad code, but because nobody looked at package.json again after the first deploy. Now you find out without having to remember to run npm audit yourself.

Still stuck? Open a ticket in Support in the dashboard.

  • security
  • vulnerabilities
  • npm
  • dependencies
  • deploy

← Back to the blog