dsql

Fail

Audited by Runlayer on Mar 4, 2026

Risk Level: HIGH
Scan Summary
Max Score
91%
Files
19
Flagged
15
Chunks
33
Flagged Files (15)
dsql/references/dsql-examples.mdHIGH
91.3%

Malicious tool definition detected

dsql/scripts/loader.shHIGH
90.6%

Malicious tool definition detected

echo "$download_url" | grep -qE "$ALLOWED_DOWNLOAD_DOMAINS"; then echo "Error: Download URL points to an unexpected domain." >&2 echo "URL: $download_url" >&2 echo "Expected: github.com/aws-samples/aurora-dsql-loader or objects.githubusercontent.com" >&2 exit 1 fi echo "Downloading from: $download_url" >&2 # Download with HTTPS enforcement and HTTP error detection local temp_file temp_file=$(mktemp) trap "rm -f '$temp_file'" EXIT if !

Aborting installation." >&2 exit 1 fi mv "$extracted_bin" "$LOADER_BIN" rm -rf "$temp_extract_dir" else chmod +x "$temp_file" # Validate the binary before moving it into place if !

dsql/mcp/mcp-setup.mdHIGH
90.4%

Tool passed security scan

Malicious tool definition detected

dsql/references/onboarding.mdMEDIUM
85.8%

Tool passed security scan

Malicious tool definition detected

This is recommended over using `admin` directly." - If yes, follow [access-control.md](./access-control.md) for detailed guidance - At minimum, guide creating one application role: ```sql -- As admin CREATE ROLE app_user WITH LOGIN; AWS IAM GRANT app_user TO 'arn:aws:iam::<account-id>:role/<AppIAMRole>'; GRANT USAGE ON SCHEMA public TO app_user; GRANT SELECT, INSERT, UPDATE, DELETE ON ALL TABLES IN SCHEMA public TO app_user; ``` - If the application handles sensitive user data, recommend a separ

dsql/SKILL.mdMEDIUM
83.2%

Tool passed security scan

Malicious tool definition detected

dsql/scripts/psql-connect.shMEDIUM
75.3%

Malicious tool definition detected

"$AI_MODEL" =~ ^[a-zA-Z0-9._-]+$ ]]; then echo "Error: --ai-model must contain only alphanumeric characters, hyphens, underscores, and dots." >&2 exit 1 fi PGAPPNAME="dsql-skill/${AI_MODEL}" fi export PGAPPNAME # Connect with psql if [[ -n "$COMMAND" ]]; then # Execute command and exit PGPASSWORD="$TOKEN" psql \ -h "$ENDPOINT" \ -U "$USER" \ -d postgres \ -c "$COMMAND" else # Interactive session PGPASSWORD="$TOKEN" psql \ -h "$ENDPOINT" \ -U "$USER" \ -d postgres fi

dsql/references/development-guide.mdMEDIUM
75.2%

Tool passed security scan

Malicious tool definition detected

Tool: dsql/references/development-guide.md [3/3] Description: from local files or S3 URIs of type csv, tsv, or parquet * automated schema detection and progress tracking ALWAYS use the loader's schema inference, PREFERRED to separate schema creation for data migration.

dsql/scripts/cluster-info.shLOW
68.2%

Tool passed security scan

dsql/mcp/mcp-tools.mdLOW
67.5%

Tool passed security scan

dsql/references/troubleshooting.mdLOW
65.2%

Tool passed security scan

dsql/references/ddl-migrations.mdLOW
63.2%

Tool passed security scan

dsql/references/mysql-to-dsql-migrations.mdLOW
59.0%

Tool passed security scan

dsql/references/access-control.mdLOW
56.1%

Tool passed security scan

dsql/scripts/delete-cluster.shLOW
52.7%

Tool passed security scan

dsql/scripts/README.mdLOW
51.6%

Tool passed security scan

Passed Files (4)Click to expand
dsql/scripts/create-cluster.shOK
45.2%

Tool passed security scan

dsql/scripts/list-clusters.shOK
38.3%

Tool passed security scan

dsql/mcp/.mcp.jsonOK
22.7%

Tool passed security scan

dsql/references/language.mdOK
8.3%

Tool passed security scan

Audit Metadata
Max File Score
91%
Classification
KNOWN_SERVER_PARTIAL_KNOWN
Files Scanned
19
Files Flagged
15
Chunks Analyzed
33
Analyzed
Mar 4, 2026, 05:16 PM
Security Audit — runlayer — dsql