GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
作者提供的说明(英文原文)
Checks TypeORM migrations for data loss, table locks, and deploy problems before they run.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"orm-preflight": {
"command": "npx",
"args": [
"-y",
"orm-preflight",
"mcp"
]
}
}
}在终端中运行这条命令
claude mcp add orm-preflight -- npx -y orm-preflight mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"orm-preflight": {
"command": "npx",
"args": [
"-y",
"orm-preflight",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"orm-preflight": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"orm-preflight",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 sikandar100 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(1.2.0)于22天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:GitHub, Desktop Commander, Cloudflare MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Preflight safety checks for TypeORM migrations: catch data loss and locking before you merge.
Documentation: https://sikandar100.github.io/orm-preflight/
Changing a column's length in TypeORM can delete all of its data. When a column's type or length changes, TypeORM's migration generator drops the column and adds it again (typeorm/typeorm#3357). The migration looks harmless in review and passes every test on an empty database. orm-preflight catches that, and other migrations that lose data, lock busy tables, or break a rolling deploy, before you merge.
src/migrations/1727100000000-WidenUserName.ts
7:30 error no-drop-and-recreate-column "users"."name" is dropped and re-added in the same migration. Every existing value in this column will be lost. Why: TypeORM drops and re-adds a column when its type or length changes, instead of changing it in place. The new column starts empty. Safe: Change the type in place: ALTER TABLE "users" ALTER COLUMN "name" TYPE varchar(255). Widening a varchar, or changing varchar to text, does not rewrite the table. ... Docs: https://github.com/sikandar100/orm-preflight/blob/main/docs/rules/no-drop-and-recreate-column.md
8:30 error no-add-not-null-without-default "users"."name" is added as NOT NULL without a default. The migration fails as soon as "users" has any rows. ...
2 errors, 0 warnings in 1 migration
npm install --save-dev orm-preflight
npx orm-preflight "src/migrations/*.ts"
Node.js 20 or newer. Without arguments, orm-preflight checks the migrations globs from its config, or every migrations folder in the project.
To start on an existing project without fixing its history, run npx orm-preflight init first (see Adopting on an existing project).
| Rule | Reports |
|---|---|
| Data loss | |
no-drop-and-recreate-column | A column dropped and added again in one migration |
possible-rename-data-loss | One column dropped and another added, with no data copied (warning) |
no-drop-column | A dropped column |
no-drop-table | A dropped table |
no-truncate | TRUNCATE or clearTable() |
no-truncating-type-change | A type change whose USING keeps only part of each value, such as left() (warning) |
no-delete-rows | A DELETE on an existing table (warning) |
no-null-out-column | An UPDATE that only clears columns, setting them to NULL (warning) |
rewrites-existing-rows | Every UPDATE, upsert, or INSERT ... SELECT on an existing table, for review (info) |
typeorm/no-changecolumn-recreate | changeColumn() that drops and re-adds the column |
| Deploy safety | |
no-rename-column | A renamed column |
no-rename-table | A renamed table |
| Locking (PostgreSQL) | |
require-concurrent-index | CREATE INDEX without CONCURRENTLY |
concurrent-index-transaction | CONCURRENTLY where it runs inside a transaction |
no-add-not-null-without-default | A NOT NULL column added without a default |
no-volatile-default | A column added with a volatile default, or as serial, identity, or generated |
no-unsafe-column-type-change | A column type change that rewrites the table |
require-not-valid-foreign-key | A foreign key added without NOT VALID |
no-set-not-null | SET NOT NULL on an existing column |
require-not-valid-check | A CHECK constraint added without NOT VALID |
validate-in-same-transaction | VALIDATE CONSTRAINT in the same transaction as its NOT VALID add, where it gains nothing (warning) |
require-concurrent-unique | A unique constraint or primary key added in place |
require-concurrent-index-drop | DROP INDEX without CONCURRENTLY (warning) |
no-blocking-maintenance | VACUUM FULL, CLUSTER, or REINDEX without CONCURRENTLY |
enum-value-used-in-same-transaction | A new enum value used before the transaction that adds it commits |
require-lock-timeout | A change to an existing table without lock_timeout (off, opt-in) |
typeorm/no-enum-recreate | TypeORM 0.3's enum change by recreating the type (warning) |
| Correctness | |
typeorm/transaction-override-forbidden | transaction set on a migration in transaction mode "all" |
typeorm/invalid-migration-name | A migration name without a 13-digit timestamp |
unanalyzable-statement | A statement orm-preflight could not read (warning) |
| [invalid-suppression](https://github.com/sikandar100/orm-preflight/blob/main/docs/rules
只显示了开头部分;其余内容请在仓库中阅读