How it works
A local-first migration flow you can verify step by step.
There is no hidden service in the loop. The CLI writes files, the report explains what changed, and you keep control of the extension tree. The public claims are limited to the paths we have already run end-to-end.
- 01
Point it at a repo
Run the CLI against a local extension folder or a fixture tree. It finds manifest.json and the files that matter.
- 02
Rewrite the obvious parts
Convert the manifest, swap the common MV2 APIs, and keep ambiguous code paths visible as warnings.
- 03
Review the report
Inspect the HTML output locally, validate it in Chrome, and decide what still needs manual work.
Verified end-to-end
- Free runs on simple-popup and content-script-injector
- Pro runs on webrequest-blocker, redirector, and header fixtures
- Signed token issuance and token-based unlock
- Batch output, patch export, and premium JSON generation
- Customer flow: email purchase, token delivery, local CLI execution
- Chrome unpacked smoke script for local validation
Buying flow
- 1. Buyer emails the pricing contact.
- 2. Vendor sends a signed token by email.
- 3. Buyer runs mv3migrate locally with `--license`.
- 4. Buyer validates output in Chrome and keeps the patch/report.