Independent Audit and Evidence

Who audited

This is a self-audit prepared with an AI coding assistant during the 0.2.0 release. It is not a third-party certification. Treat it as a reproducible checklist: every row names a command you can run yourself.

Scope

Version 0.2.1: packages/core, packages/cli, packages/server, fixtures, tests, CI and packaging. Skills and agent prompts were checked for structure, not for model behavior.

Reproduce everything

git clone https://github.com/shahvatsalofficial/MigraSutra-AI.git && cd MigraSutra-AI
npm test
npm run demo
npm run test:report
npm run check:docs
node packages/cli/index.mjs audit --root fixtures/risky-app --target node:22 --out artifacts/audit

Results

#CheckMethodResult
1Unit and CLI testsnpm testSee test results. Fail count must be 0
2Skipped testsSame run3 symlink tests skip only when the host forbids symlinks; they run on Linux and macOS CI
3SQL rule accuracy16 labelled cases in tests/sql-corpus.test.mjs15 correct, 1 known false negative (dollar-quoted dynamic SQL)
4Source immutabilityByte comparison before and after plan, rehearse, auditUnchanged (tests: plan does not modify source, scan never mutates source tree)
5Verdict ceilingaudit on a clean fixtureREVIEW_REQUIRED, never a pass
6Report escapingInject <img src=x onerror=1> as a filenameEscaped in HTML
7Dependenciespackage.jsonZero runtime dependencies
8Network useCode review of packages/coreNo network import; rehearsal records network: false
9Package contentsnpm pack --dry-runOnly intended files ship
10Docs freshnessnpm run check:docsHTML equals regenerated output

What the 16-case corpus does and does not show

It shows the rules behave as designed on comments, strings, casing, line breaks and safe variants. It is small and written by the maintainer. It is not a precision or recall benchmark on real-world code. No such benchmark has been run.

Findings from the audit (fixed in 0.2.0)

FindingSeverityFix
Three tests failed on Windows hosts without symlink privilege (EPERM)MediumTests skip with a stated reason when symlinks cannot be created
Reports were a single preformatted block, hard to scanLowStructured Markdown and responsive HTML with severity badges
No single command produced all report formatsLowAdded audit
Few SQL rules for expand-contract risksLowAdded NOT NULL without DEFAULT, RENAME, non-concurrent index rules
Package was marked private and not publishableMediumMetadata, files list and release workflow added

Open limitations (not fixed)

How to verify claims independently

  1. Read packages/core/index.mjs. It is a single file under 400 lines.
  2. Run the commands above on a machine you control.
  3. Compare test-results.json with the Actions run for the same commit.
  4. Break a rule on purpose and confirm a test fails.