sql-security

Scan TypeScript, Rust, and Go code for risky inline SQL construction.

320|3|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/mizchi/skills --skill sql-security-mizchi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sql-security
Source: https://github.com/mizchi/skills/tree/main/sql/security
Command: npx skills add https://github.com/mizchi/skills --skill sql-security-mizchi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

SQL-inspired vulnerabilities emerge when host-language code builds SQL strings without proper binding or safe placeholders. This skill provides a focused line-based scanner to detect risky patterns that commonly lead to SQL injection and secret leakage, enabling teams to triage and fix issues before they reach production.

Core Features & Use Cases

  • Detects SQL injection risks by scanning template literals and string concatenations that embed SQL fragments in languages like TypeScript, Rust, and Go.
  • Honors an opt-out marker (sql-security: ok) to silence known-safe lines or blocks without suppressing real findings.
  • Provides guidance for companion secretlint integration to catch hardcoded credentials or connection strings during pre-push or PR workflows.
  • Ignores generated code and build artifacts by design to keep focus on hand-written source.
  • Suitable for early-stage code reviews, CI checks, or automated scans to surface potential vulnerabilities for manual review.

Quick Start

Run the scanner against your project source to surface SQL-injection candidates for manual review.

Frequently Asked Questions about sql-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan TypeScript code for SQL injection risks in template literals?

Scanning TypeScript code for SQL injection risks involves analyzing template literals and string concatenations that embed SQL fragments. This skill performs line-based scanning across TypeScript, Rust, and Go projects to surface risky inline SQL construction for manual review.

What's the best way to detect unsafe SQL string concatenation in Node projects?

Detecting unsafe SQL string concatenation requires a focused scanner that identifies inline SQL without proper binding. This skill scans host-code for risky string patterns and provides opt-out markers to silence known-safe lines without suppressing real findings.

Can I use this SQL injection scanner with Rust and Go source code?

Yes, this SQL injection scanner supports Rust and Go source code alongside TypeScript. It applies line-based analysis to detect risky SQL construction patterns across these languages, targeting hand-written source while ignoring generated code and build artifacts.

Do I need external dependencies to run a SQL security scan on my codebase?

No external dependencies are required to run this SQL security scan. The scanner operates using only built-in modules and requires a Node 20+ runtime, keeping the toolchain lightweight and avoiding additional package installations.

How do I suppress false positives when scanning for SQL injection vulnerabilities?

Suppressing false positives during SQL injection scanning is handled through an opt-out marker. Adding the marker "sql-security: ok" to specific lines or blocks silences known-safe code without suppressing actual vulnerability findings elsewhere in the file.

What are the limitations of line-based scanning for SQL injection detection?

Line-based scanning for SQL injection detection focuses strictly on hand-written source code and ignores generated code or build artifacts by design. It surfaces potential vulnerabilities for manual review rather than providing automated fixing or runtime query analysis.