Dependency Vulnerability Scanning

Example workflows

Starting points built from this record, not transcripts of a run. Each prompt is written the way it should be sent, as one paragraph, and each is worth editing before you send it.

1. 01

   Stand it up from scratch

   You have read the record and want Dependency Vulnerability Scanning working in a real project rather than a sandbox.

   Set up Dependency Vulnerability Scanning in this project — auto-detect npm dependency vulnerabilities by severity. Walk it end to end, tell me exactly what you changed, and flag anything I have to switch on myself before it works.

   Expected outcome

   A working setup, a plain list of what changed, and a short list of anything left for you to switch on. Check that list before assuming it is done.

2. 02

   Pre-launch dependency hygiene

   The record lists this as one of the jobs Dependency Vulnerability Scanning is meant for, so it is a fair first test of whether it fits your app.

   In this project, use Dependency Vulnerability Scanning for pre-launch dependency hygiene. Build the smallest version that a real user could complete end to end, keep the change scoped to that path, and tell me how to test it myself.

   Expected outcome

   One complete path a user can walk, the files and settings that changed, and the steps to test it. Walk it yourself before you ship it.

3. 03

   Review it before you publish

   Dependency Vulnerability Scanning is wired in and you are about to put it in front of people. This is the pass that catches the half-configured version.

   Review how this project uses Dependency Vulnerability Scanning before I publish. Check severity ranking and affected-package visibility, list anything that is missing, misconfigured, or only half wired, fix what is safe to fix, and tell me what you left alone and why.

   Expected outcome

   A findings list split into what was fixed and what was left, with a reason for each. Anything left alone is yours to decide on.

Frequently asked

• What is Dependency Vulnerability Scanning?

  Dependency Vulnerability Scanning is Lovable's Security feature: Auto-detect npm dependency vulnerabilities by severity. Automatic supply-chain scanning ranks dependency vulnerabilities by severity (critical, high, medium), shows which packages are affected, and surfaces available fixes.

• Is Dependency Vulnerability Scanning GA or in beta?

  Dependency Vulnerability Scanning is generally available (GA) on Lovable.

• What Lovable plan includes Dependency Vulnerability Scanning?

  Dependency Vulnerability Scanning is available on all Lovable plans.

• When did Dependency Vulnerability Scanning launch?

  Dependency Vulnerability Scanning launched on Jan 16, 2026.

• Security CenterSame category, also GA · Jan 2026
• Two-Factor Authentication (2FA)Same category, also GA · Jan 2026
• SCIM ProvisioningSame category, also GA · Feb 2026