- Home
- Skills
- Data & Databases
- Drizzle ORM Safety Check
More screenshots
Works with the AI Agents you already use
Drizzle ORM Safety Check
This skill finds those and the other Drizzle mistakes below before you deploy, and tells you how to fix each one.
$5
Drizzle ORM Safety Check
Example session with this skill installed
Check this project with drizzle-orm-safety-check.
- Read your context and instructions
- Compiled the drizzle orm safety
$ python3 scripts/check_drizzle.py examples/risky
BLOCK drizzle.config.ts:12 D02 DB_CREDENTIALS_IN_FILE
password: '<redacted>',
Why: A database password or token is written in the file: in a connection URL, in dbCredentials, in the connection object given to drizzle() or a driver (Pool, postgres(), createPool(), createClient()), as a ?? or || fallback, or in a package.json script (a URL, --password, --auth-token, PGPASSWORD=). Everyone who can read the repository, its history, CI logs or a published package can use the database.
Safer: Read credentials from the environment (url: process.env.DATABASE_URL!) or a secret manager, keep .env files out of git, and change (rotate) the password or token that was committed. Local hosts, example hosts and a Docker service name with a default password (postgres, root) are not reported.
BLOCK package.json:8 D03 PUSH_FORCE_ON_DEPLOY
BLOCK src/server/routes.ts:11 D01 RAW_SQL_FROM_REQUEST
REVIEW drizzle.config.ts:14 D19 DB_TLS_VERIFY_OFF
REVIEW package.json:7 D13 PUSH_ON_DEPLOY
REVIEW package.json:10 D18 STUDIO_ON_ALL_INTERFACES
REVIEW package.json:11 D19 DB_TLS_VERIFY_OFF
REVIEW src/db/schema.ts:6 D15 PASSWORD_COLUMN_NOT_HASH
REVIEW src/db/schema.ts:12 D16 FOREIGN_KEY_WITHOUT_INDEX
REVIEW src/db/schema.ts:13 D14 MONEY_IN_FLOAT_COLUMN
REVIEW src/server/routes.ts:17 D12 SQL_IDENTIFIER_FROM_INPUT
REVIEW src/server/routes.ts:22 D11 RAW_SQL_WITH_UNCHECKED_VALUE
REVIEW src/server/routes.ts:26 D17 DELETE_OR_UPDATE_WITHOUT_WHERE
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 5 files, 5 with Drizzle content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
db.execute(sql.raw(SELECT * FROM orders ORDER BY ${req.query.sort})) sends the request's own text to the database as SQL, and a start script that runs drizzle-kit push --force accepts every data-loss statement on the production database without asking. This skill finds those and the other Drizzle mistakes below before you deploy, and tells you how to fix each one.
Your agent runs a scanner on your drizzle.config files, schema files (pgTable, sqliteTable, mysqlTable, also through pgTableCreator, pgSchema or an alias), TypeScript and JavaScript query code, and package.json scripts. It skips comments and test files, follows request data from Express, Fastify, Koa, Hono, Next.js (route handlers, cookies, server actions), tRPC, Nuxt and SvelteKit through local variables and function parameters, treats the sql tagged template and the query builder as parameterized, accepts values picked from fixed choices or kept to them by a check that rejects anything else, and leaves local development credentials, example hosts and the placeholders of Drizzle's own docs alone. It never runs your code or connects to a database. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.
What it checks
BLOCK
- D01: request data (including tRPC input, server action arguments and cookies) in sql.raw(), also inside a sql template or through JSON.stringify(), or in a plain SQL string given to db.execute(), db.run(), db.all(), db.get() or db.values()
- D02: database passwords and tokens written in a connection URL, dbCredentials, the connection object of drizzle() or a driver, a ?? or || fallback, or a package.json script (a URL, --password, --auth-token, PGPASSWORD=)
- D03: drizzle-kit push --force run by a start, build, deploy, release or install script, directly or through another npm script
REVIEW
- D11: sql.raw() or a plain SQL string built from a parameter, stored data or another function's result
- D12: sql.identifier() with a table or column name from input
- D13: drizzle-kit push (without --force or --explain) run by a start, build, deploy, release or install script
- D14: money columns (price, amount, balance, total...) stored as real, double or float
- D15: password columns whose names do not say they hold a hash (Better Auth account tables are left alone)
- D16: foreign keys without an index on the referencing column in PostgreSQL, SQLite and SQL Server tables
- D17: db.delete(table) or db.update(table).set() with no where(), outside seed and reset scripts
- D18: drizzle-kit studio started with --host 0.0.0.0
- D19: database certificate checks turned off (rejectUnauthorized: false, trustServerCertificate: true, sslmode=no-verify, NODE_TLS_REJECT_UNAUTHORIZED=0, postgres.js ssl: 'require')
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason, safer approach and official source for each rule
- A risky and a safe example project (drizzle.config.ts, schema, Express routes, package.json), and the real report the scanner produces on the risky one
Limits It reads each file on its own and follows request data only through variables in that file: values passed in from helpers in other files are reported as D11, not D01, and scopes are read from brackets and declarations rather than a full parser. SQL migration files, .env files, Dockerfiles, CI workflows and .svelte, .vue or .astro files are not read, and it does not check your Drizzle version, database grants or row-level security policies. NOT FLAGGED is not a guarantee.
Static check of Drizzle config, schema, query code and package.json scripts. Request data is followed only within one file, and drizzle-kit commands started from Dockerfiles or CI workflows are not seen. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 days ago
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example project includes a clearly fake, inert database password (NOTREAL-...) for the scanner to find. Nothing in it is run.