Database Connections

CodescanBot can do more than explain vulnerabilities — it can fix them end-to-end. When a security fix requires a database change (a stored procedure, a constraint, an index, a schema alteration), the bot generates the exact SQL or command, shows it to you for review, and executes it directly against your database with one click.

What you need before you start

Supported databases

CodescanBot supports two modes for each database:

How to connect and run a migration

Step 1 — Open CodescanBot

1. Go to codesscan.com/scan and scan your code
2. Click ◈ CodescanBot in the scanner header (or press Ctrl+K)
3. Select a vulnerability from the findings list

Step 2 — Configure your database connection

1. In the CodescanBot panel header, click the 🗄 DB button
2. A database panel slides open — click the tab for your database type
3. Fill in the connection credentials (see the per-database guides below)
4. The button shows 🗄 DB ● when credentials are entered

Step 3 — Ask the bot to fix the vulnerability

1. Type “fix this” or click the ⚡ Apply fix chip
2. The bot fixes the code file AND, if a DB change is needed, generates the migration automatically
3. A DATABASE MIGRATION READY panel appears showing the exact SQL
4. Review the SQL — then click ▶ Execute Migration (live databases) or 📋 Copy Migration Script (script-only)
5. The result is shown immediately: ✅ success or ❌ error with the database message

PostgreSQL — connection guide

Covers Supabase, Neon, CockroachDB, AWS RDS PostgreSQL, Railway, Render, and any self-hosted PostgreSQL instance.

Option A — Connection string (recommended)

# Standard PostgreSQL URL format
postgresql://username:password@host:5432/database_name

# With SSL (required for most cloud providers)
postgresql://username:password@host:5432/database_name?sslmode=require

# Examples
postgresql://postgres:mypass@db.mycompany.com:5432/production
postgresql://user:pass@ep-xyz.us-east-2.aws.neon.tech/neondb?sslmode=require

Option B — Individual fields

Supabase — connection guide

Use the Supabase tab for the simplest setup — just your project URL and Service Role Key. CodeScan derives the correct PostgreSQL connection string automatically.

1. Log in to supabase.com → open your project
2. Go to Project Settings → API
3. Copy the Project URL (format: https://xyz.supabase.co)
4. Copy the service_role key (under Project API keys — not the anon key)
5. Paste both into the Supabase tab in the DB panel

MySQL / MariaDB — connection guide

Covers MySQL 5.7+, MySQL 8.x, MariaDB 10.x, PlanetScale, AWS RDS MySQL, and Amazon Aurora MySQL.

# Connection string format
mysql://username:password@host:3306/database_name

# With SSL
mysql://username:password@host:3306/database_name?ssl=true

# PlanetScale (requires SSL)
mysql://user:pscale_pw_xxx@host.us-east.psdb.cloud/database?ssl={"rejectUnauthorized":true}

# AWS RDS MySQL
mysql://admin:password@mydb.abc123.us-east-1.rds.amazonaws.com:3306/mydb

Where to find credentials:

• PlanetScale: Dashboard → Database → Connect → Create password → choose Node.js driver → copy connection string
• AWS RDS: RDS Console → Databases → your instance → Connectivity tab → Endpoint + Port
• Self-hosted: Use the host where MySQL is running, port 3306, and a user with ALTER and CREATE ROUTINE privileges

MongoDB — connection guide

Covers MongoDB Atlas, AWS DocumentDB, and Azure Cosmos DB for MongoDB. For MongoDB, migrations are sent as JSON commands (not SQL) that the bot formats automatically.

# MongoDB Atlas (SRV format — recommended)
mongodb+srv://username:password@cluster0.abc123.mongodb.net/myDatabase

# Standard format
mongodb://username:password@host:27017/database

# With auth source
mongodb://username:password@host:27017/database?authSource=admin

# Atlas example
mongodb+srv://codescan:MyPass123@cluster0.xyz.mongodb.net/production

Where to find your Atlas connection string:

1. Atlas → your cluster → Connect
2. Choose Drivers → Node.js
3. Copy the connection string and replace <password> with your actual password

Microsoft SQL Server — connection guide

Covers Azure SQL Database, AWS RDS for SQL Server, and on-premise SQL Server 2016+.

For Azure SQL, find the server name in Azure Portal → SQL databases → your database → Overview → Server name.

Redis — connection guide

Covers Redis Cloud, Upstash, AWS ElastiCache, and Heroku Redis. Redis migrations run as commands (SET, HSET, CONFIG SET, etc.) rather than SQL.

# Connection string formats
redis://password@host:6379
redis://username:password@host:6379
rediss://password@host:6380        # rediss:// = TLS

# Upstash (always TLS)
rediss://default:AXXXpasy...@us1-abc.upstash.io:6380

# Redis Cloud
redis://:mypassword@redis-12345.c1.us-east-1-1.ec2.cloud.redislabs.com:12345

# AWS ElastiCache (no password by default, TLS optional)
redis://my-cluster.abc123.ng.0001.use1.cache.amazonaws.com:6379

Cassandra — connection guide

Covers Apache Cassandra, DataStax Astra DB, and AWS Keyspaces. Migrations run as CQL (Cassandra Query Language).

Script-only databases

For Oracle, DynamoDB, Snowflake, BigQuery, Firestore, and SQLite — CodescanBot generates the correct migration syntax for the selected database but cannot execute it directly (these databases require native drivers or cloud SDKs that cannot run in a serverless environment). Instead:

1. Select the database type in the DB panel
2. Ask the bot to fix the vulnerability — it generates the correct migration syntax for your database
3. A 📋 Copy Migration Script button appears instead of Execute
4. Click it to copy the migration to your clipboard
5. Paste and run it in your database console or CLI

Where to run script-only migrations

Safety and security

Troubleshooting

Quick reference

# ── Open CodescanBot ──────────────────────────────────────────────
# Click ◈ CodescanBot in scanner header  OR  Ctrl+K

# ── Connect your database ─────────────────────────────────────────
# Click 🗄 DB  →  pick database tab  →  fill credentials
# Green dot (🗄 DB ●) = credentials entered

# ── Trigger a migration ───────────────────────────────────────────
# Select a vulnerability  →  ask bot to "fix this"
# Bot patches code + proposes DB migration
# Click ▶ Execute Migration  (live databases)
# Click 📋 Copy Migration Script  (script-only databases)

# ── Connection string formats ─────────────────────────────────────
# PostgreSQL   postgresql://user:pass@host:5432/db?sslmode=require
# Supabase     Project URL + service_role key  (use Supabase tab)
# MySQL        mysql://user:pass@host:3306/db
# MongoDB      mongodb+srv://user:pass@cluster.mongodb.net/db
# SQL Server   host + port + db + user + pass  (use SQL Server tab)
# Redis        redis://:password@host:6379
# Cassandra    host + keyspace + datacenter + credentials