Start here

Buy this when the scan is promising but the purchase decision is still fuzzy.

Run the SQLAlchemy or Pydantic scanner first, then use the fit report add-on locally to turn the report into a manager-readable recommendation.

Local workflow with no repo upload.
Recommendation output from scanner data you generated locally.
Manual-review risk stays visible before a larger purchase.

Price: $99 per team.

Buy automated fit report - $99

Explore the details

Secure checkout is handled by Stripe.

Trust boundary

Scope and validation

Run on a branch and review the documented scope before applying changes.
The public repo is scanner-first and does not expose the full paid apply engine.
Examples establish only the cases shown. Run your own application tests before merging.

What this fixes

Ambiguous scan output where supported and manual-review findings are mixed.
Manager uncertainty about whether a cleanup pack is worth buying.
The gap between a raw JSON scan report and a clear next-step recommendation.

After purchase, you receive

Commercial ZIP with the local fit-report add-on.
Buy/do-not-buy summary for SQLAlchemy or Pydantic scanner output.
Supported finding counts, manual-review risk notes, and next-step recommendation.
No human review, no report submission, and no source-code upload.

Example before/after

See the migration deliverable before checkout.

Illustrative output format: sample counts and validation results below are not a run on your repository. Use the linked proof artifacts for recorded evidence. You can also make changes manually using the free report and migration guides.

Local command

python -m pip install "https://github.com/zippertools/sqlalchemy-14-to-20-codemod/archive/refs/tags/v0.1.2.zip"
python -m sa20_pack.cli . --report migration-report.json
# Then run the purchased fit-report add-on against that scanner output.

Use SQLAlchemy or Pydantic scanner output. Do not send private source code through support.

Sample report

Fit report complete
supported_findings: 38
manual_review_findings: 6
recommendation: good_fit (heuristic; review supported scope)
next_step: preview deterministic rewrites

Before/after diff preview

Manager summary
Repo fit: yes, for the documented SQLAlchemy subset
Why: repeated Query.get and select([..]) findings
Risk: engine.execute remains manual review
Manual alternative: use the free report and linked migration guidance

The value is the controlled workflow: scan, preview, apply supported rewrites, review manual findings, and validate on your branch.

Pattern	Behavior
SQLAlchemy scanner report	supported input
Pydantic scanner report	supported input
ESLint proof-only report	out of scope
Private source upload	not required

Apply output

fit-report add-on complete
input_report: migration-report.json
supported_ratio: strong enough for paid cleanup consideration
manual_review_risk: medium
recommendation_written: manager-fit-summary.md

Validation summary

validation summary
scanner_report_loaded: passed
unsupported_product_family_check: passed
source_upload_required: false
overall: recommendation ready for review

Final manager summary

final manager summary
Decision: buy the cleanup pack if validation time is available.
Why: repeated supported findings dominate the migration noise.
Risk: manual-review findings remain visible and should be assigned.

Use this if

Teams with SQLAlchemy or Pydantic scanner output but no clear buy/no-buy decision yet.
Buyers who need a manager-readable fit summary without uploading source code.
Repos where supported and manual-review findings are mixed enough to justify a second local check.

Fit signals and docs

Reads scanner output locally instead of requiring private repo upload.
Separates supported findings from manual-review risk before a larger purchase.
Produces a software-generated recommendation without human service delivery.

Do not use this if

Repos that have not run the SQLAlchemy or Pydantic scanner yet.
Teams that already know they need the full cleanup pack.
ESLint proof-only scans; this add-on is scoped to SQLAlchemy and Pydantic output.

How delivery works

Stripe Checkout handles secure payment and receipts.
Download your purchased ZIP after payment.
Runs locally; no hosted API, repo upload, or production credentials needed.
Run the add-on against scanner output you generated locally; keep the recommendation with your branch or manager notes.

Refund/support note

14-day refund review for published-scope or delivery mismatches. This add-on is not automatically credited toward a cleanup pack yet; treat it as a separate diagnostic purchase.

Support: support@zippertools.org

Next step

Buy the fit report

Use checkout after you have scanner output and want a local recommendation before buying a larger pack.