Documentation Index
Fetch the complete documentation index at: https://docs.lovable.dev/llms.txt
Use this file to discover all available pages before exploring further.
What is Wiz security scanning
Wiz brings automated security scanning to Lovable. When connected, Wiz scans your project for vulnerable dependencies and risky code patterns and surfaces findings directly in your project’s Security view. Wiz scanning combines two analyses:- Software composition analysis (SCA)
Examines your project’s dependency tree (package lockfiles, installed libraries, and transitive dependencies) to identify packages with known CVEs - Static application security testing (SAST)
Analyzes your source code for security issues like unsafe patterns, hardcoded secrets, and risky API usage
- RLS analysis and Database security check examine your Cloud/Supabase configuration for missing row-level security policies and database misconfigurations.
- Code security review uses AI to analyze your code for vulnerabilities like exposed secrets, open endpoints, and input validation issues.
- Dependency audit checks npm dependencies for known vulnerabilities.
- Wiz scanning adds enterprise-grade vulnerability and code-security detection backed by Wiz’s continuously updated security database.
When to use Wiz scanning
- Before launching or deploying
Run a scan to check for vulnerable dependencies and risky code patterns before going live. - After adding or updating dependencies
Re-scan after installing new packages or updating existing ones to check for newly introduced vulnerabilities. - As an ongoing practice
Wiz scans run automatically as part of the security scan suite, so connected projects are continuously checked as new vulnerabilities are disclosed. - For compliance and security posture
Use Wiz scanning alongside other security scanners to maintain a comprehensive view of your project’s security status.
How Wiz scans your project
When a security scan runs, Lovable mounts your project code into a secure sandbox environment and runs the Wiz CLI scanner against it. The scanner examines your project’s software bill of materials (SBOM) and source files, and checks both dependencies and code against Wiz’s security database. Findings are classified by severity:| Wiz severity | Security view level |
|---|---|
| Critical | Error |
| High | Warning |
| Medium and lower | Info |
- The affected package or file
- The location (file path, and line numbers for SAST findings)
- A description and remediation guidance from Wiz
- A direct link to the full details in Wiz
Prerequisites
- A Wiz account with permission to add deployments
- Your Wiz Token URL: The OAuth authentication endpoint for your tenant (either Cognito or Auth0). If you’re unsure which to use, try Cognito first. Your Wiz administrator can confirm the correct endpoint.
- Lovable workspace owner or admin role to connect Wiz
All scans use your Wiz deployment’s permissions and quotas. Usage is handled directly by Wiz, not Lovable.
How to connect Wiz
A workspace admin or owner connects the Lovable workspace to Wiz using a Wiz deployment. Only one Wiz connection can be added per workspace.Step 1: Create a Lovable integration deployment in Wiz
A Lovable integration deployment lets Lovable authenticate with Wiz to run scans.Log in to the Wiz portal
Go to the Wiz portal.
Create and configure a new Lovable integration deployment
- Go to Create a new Lovable integration deployment
- Give the deployment a descriptive name (for example,
Lovable) and choose its scope. - Click Add integration.
Step 2: Connect Wiz to Lovable
Enter connection details
- Display name: Name the connection, for example
Wiz. - Client ID: From your Lovable integration deployment in Wiz.
- Client Secret: From your Lovable integration deployment in Wiz.
- Advanced settings → Token URL: Lovable defaults to Cognito (
https://auth.app.wiz.io/oauth/token), which is correct for most tenants. If your Wiz tenant uses Auth0, switch the Token URL tohttps://auth.wiz.io/oauth/token. Your Wiz administrator can confirm which to use. - Who can access this connection: keep access limited to specific people or invite the entire workspace. See Connection-level access for more information.
To enable security scanning for the entire workspace, make sure to invite the entire workspace.
How to view and fix findings
Wiz findings appear in the Security view of each project, alongside findings from other scanners.Open the Security view
Open your project and go to the Security tab. Wiz findings are listed in their own section. Each Wiz finding shows a Wiz badge so you can identify its source.
Review finding details
Click a finding to expand it and see the full details: affected package or file, location, description, remediation, and a link to the report in Wiz.
Manage the Wiz connection
Workspace admins and owners can manage the Wiz connection from Connectors → App connectors → Wiz.- Update credentials
Open the connection to edit the Client ID, Client Secret, or Token URL. Useful when rotating deployment credentials. - Delete
This permanently removes the workspace connection and its credentials. This cannot be undone. Wiz scanning will stop across all projects in the workspace, and existing Wiz findings will no longer appear in the Security view.