orm-preflight
NPM · ORM-PREFLIGHT
Checks TypeORM migrations for data loss, table locks, and deploy problems before they run.
Available components
Last scanned (20 hours ago)
Scores higher than 92% of npm servers
Category Databases
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 11 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to sikandar100/orm-preflight). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 390 tokens (~130/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (67% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 15 Oct 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: 0.47 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 1.1.0 → 1.2.0 functional
- 13 Oct 26 +7
- Stability: unverified → 0.43 ▲ functional
- Security disclosure: unverified → pass ▲ functional
- 11 Oct 26 −1
- Security disclosure: pass → unverified ▼ functional
- 1 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Sept 26 68
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Analysed npm/orm-preflight@1.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | sikandar100/orm-preflight |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/sikandar100/orm-preflight/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 3259416364 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:da5e0945e60ad6882530b7ea26eb5d6d49485ecd2376d4ceeb74442d7f1aa12318e475a1ff4efb40be82e4c012eebb161e9306414ce5385d68479dfd8 |
Background: How many MCP packages publish verified provenance →
Dependencies 11 packages
| Packages resolved | 11 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_migrations Check migrations ~191
Checks database migrations for data loss, table locks, and deploy problems. Returns every finding with what happens, why, and a safe alternative. Run it after writing or changing a migration. Without files, it checks the migrations configured for the project, or every migrations folder.
| Name | Type | Req | Description |
|---|---|---|---|
| changedSince | string | – | A git ref, such as origin/main. Checks only migrations added or changed since the branch left it. |
| dialect | – | – | The database. Default: the config, or postgres. |
| files | array | – | Migration files or globs, relative to projectDir, such as ["src/migrations/1727200000000-AddEmail.ts"]. |
| postgresVersion | integer | – | The PostgreSQL major version. Default: the config, or 16. |
| projectDir | string | – | Absolute path of the project root, where package.json is. Default: the directory the server started in. |
| Name | Type | Req | Description |
|---|---|---|---|
| findings | array | yes | – |
| summary | object | yes | – |
| version | string | yes | – |
No examples provided.
explain_rule Explain a rule ~59
Returns a rule's documentation: what happens, bad and safe examples, when a suppression is fine, and the PostgreSQL, MySQL, or TypeORM sources behind it.
| Name | Type | Req | Description |
|---|---|---|---|
| rule | string | yes | The rule ID, such as no-drop-column. |
No output schema declared.
No examples provided.
list_rules List rules ~21
Lists every rule with its category, default severity, and databases.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| rules | array | yes | – |
No examples provided.
How do I install the orm-preflight MCP server?
orm-preflight runs locally as an npm package, launched with npx -y orm-preflight. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · orm-preflight
claude mcp add sikandar100-orm-preflight -- npx -y orm-preflight
What is the orm-preflight MCP server?
orm-preflight is an MCP server listed in the public MCP registry as io.github.sikandar100/orm-preflight. Checks TypeORM migrations for data loss, table locks, and deploy problems before they run. This page covers its npm package (orm-preflight).
Is the orm-preflight MCP server safe to use?
orm-preflight scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the orm-preflight MCP server expose?
orm-preflight exposes 3 tools: check_migrations, explain_rule, list_rules. Their descriptions and schemas cost roughly 271 tokens of context every time the server is loaded.
Is the orm-preflight MCP server still maintained?
orm-preflight is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the orm-preflight MCP server under?
orm-preflight declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.