Language targets need method and model comparison.
Provider migration
Migrate from liblab to Sourced
liblab focuses on SDK generation. Sourced is for teams that want SDKs, docs, previews, and publishing readiness in the same dashboard. On this page: what to scan in your liblab setup, the migration checks Sourced runs, and a preview of the generated SDK and docs you would get.
Unlimited previews. No credit card required.
01Checks
What to check
Package metadata and README examples need review.
Publishing credentials need dry-run checks.
Docs hosting usually lives outside the liblab workflow.
02Checks
Migration checklist
Inventory every liblab SDK language and package name.
Run Sourced compatibility reports against the SDKs customers already install.
Compare auth, pagination, errors, file uploads, and streaming behavior before publishing.
Move docs and examples into an OpenAPI-driven Sourced preview.
Use dry-run publishing before touching npm or PyPI packages.
03Details
Why Sourced fits
Sourced combines SDK generation with docs previews and release checks.
Compatibility reports make migration risk visible before a package goes live.
Unlimited preview generations let teams iterate before paying to launch.
Honest trade-off: liblab has broader mature language coverage today; Sourced is strongest for TypeScript and Python first.