Skip to main content
Migrations

MigraSutra AI

Audit upgrade and SQL-migration risk without running the migration.

Offline, read-only migration audit CLI. npm [email protected] published 2026-11-10. The README says it does not run tests, installs, scripts, or migrations, and it never says safe to deploy.

  • Offline
  • 20 skills
  • Node 22+
GitHub version
0.2.1
Licence
Apache-2.0
Language
HTML
Weekly downloads
519
Overall downloads
519
GitHub stars
4

Live npm weekly downloads, npm overall downloads, and the latest npm version, plus GitHub stars and the package.json version, fetched 2026-11-17 19:07 UTC. Cached 10 minutes. Weekly downloads cover 2026-11-10 to 2026-11-16. Overall downloads cover 2026-10-01 to 2026-11-17. npm does not publish an earlier total. Stars and downloads show public use. They are not a quality score.

Use it when

  • 1

    You want a read-only look at SQL, npm, Python, and Docker upgrade risk.

  • 2

    You want a rehearsal of one package.json change in a temp directory.

  • 3

    You want a gate that never says safe to deploy.

What it does, and what it does not

Read this before the guide. A limit here is a limit of the tool.

Does

  • SQL heuristics: drop table or column, truncate, unscoped delete, NOT NULL without default, rename, and non-concurrent index.
  • npm: star, latest, git, or URL dependencies, a missing lockfile, and an invalid manifest. Python requirements not pinned with ==. Docker base images that are untagged, latest, or not digest-pinned.
  • Inventory covers npm, Python, Go, PHP, JVM, .tool-versions, and Dockerfile.
  • plan and rehearse support an npm dependency change or an engines.node change in package.json, in a temp directory.
  • 20 skills. The README says live discovery in each IDE has not been verified.
  • The README says 16 labelled SQL cases, 15 correct, and 1 documented false negative. It calls that a small corpus, not a benchmark. Needs Node.js 22 or newer.

Does not

  • It does not run tests, installs, scripts, or migrations. Test status is always NOT_RUN.
  • The best verdict is REVIEW_REQUIRED. The README says it never says safe to deploy.
  • SQL checks miss dynamic SQL inside $$ bodies.
  • Runnable sandboxes, codemods, database restore labs, and a hosted dashboard are roadmap, not shipped.
  • The audit is a self-audit, not a third-party certificate. 0 runtime dependencies.

Claims above are from the project pages and are attributed as stated there. They are not independently verified here.

How a run moves

From the MigraSutra AI README, npm 0.2.0, published 2026-11-10. Needs Node.js 22 or newer. It reads files. It does not run the migration.

  1. 1. Input

    Manifests and SQL files

    npm, Python, Docker, Go, PHP, JVM, and .tool-versions. No install and no migration run.

  2. 2. Rules

    Heuristics

    Destructive SQL patterns, unpinned dependencies, and unpinned images. Dynamic SQL inside $$ bodies is missed.

  3. 3. Rehearsal

    One package.json change

    plan and rehearse cover an npm dependency or engines.node, in a temp directory. Other change types are not rehearsed.

  4. 4. Gate

    A person decides

    The best verdict is REVIEW_REQUIRED. The README says the tool never says safe to deploy.

How to read the result

Result It means It does not mean
NO_GO The risky-app demo in the README ends NO_GO with high 4 and medium 4. The tool still did not run the migration or the tests.
REVIEW_REQUIRED The strongest positive verdict the README allows. Not safe to deploy.
NOT_RUN Test status. The CLI does not run the suite. Not a green test result.

Wording is from the project page or README and is attributed as stated there. It is not independently verified here.

Commands and notes

  • npx [email protected] audit --root . --out migrasutra-report --fail high the README CI line.
  • migrasutra scan --root . --out scan.json
  • migrasutra plan --root . --scan scan.json --target npm:[email protected] --out plan.json
  • migrasutra rehearse --root . --plan plan.json --out rehearsal.json
  • migrasutra gate --plan plan.json --rehearsal rehearsal.json --out gate.json

Guide

How to use the result. GitHub is the source repository. npm is the install.

What the audit looks at

From the MigraSutra AI README, npm 0.2.0, published 2026-11-10. Needs Node.js 22 or newer.

  • SQL heuristics: drop table or column, truncate, unscoped delete, NOT NULL without default, rename, and non-concurrent index. Dynamic SQL inside $$ bodies is missed.
  • npm: star, latest, git, or URL dependencies, a missing lockfile, and an invalid manifest. Python requirements not pinned with ==. Docker images that are untagged, latest, or not digest-pinned.
  • Inventory covers npm, Python, Go, PHP, JVM, .tool-versions, and Dockerfile.
  • plan and rehearse support an npm dependency change or an engines.node change in package.json, in a temp directory.

What it will not say

  • It does not run tests, installs, scripts, or migrations. Test status is always NOT_RUN.
  • The best verdict is REVIEW_REQUIRED. The README says it never says safe to deploy. The risky-app demo ends NO_GO with high 4 and medium 4.
  • 20 skills. Live discovery in each IDE has not been verified. The README says 16 labelled SQL cases, 15 correct, and 1 documented false negative, and calls that a small corpus.
  • Runnable sandboxes, codemods, database restore labs, and a hosted dashboard are roadmap, not shipped. 0 runtime dependencies.

Questions

Does MigraSutra run the migration?

No. The README says it does not run tests, installs, scripts, or migrations. Test status is always NOT_RUN.

Can the verdict be safe to deploy?

No. The README says the best verdict is REVIEW_REQUIRED and a human decides.

WhatsApp