- What is laravel-shift/cli used for?
- laravel-shift/cli is a command-line interface for Laravel Shift that lets you authenticate and run automated Shifts, which are scripted upgrade and code modernization tasks, from your terminal instead of the web UI. It is developer tooling for maintaining Laravel projects, such as upgrading framework versions or applying repetitive code transformations. It is not a runtime library and should never be loaded by a production application.
- How do I install laravel-shift/cli?
- It is intended to be installed as a global Composer tool, or as a dev-only dependency in a project you are maintaining, so it stays out of your production dependency graph. Pin the exact version you validate, because the repository is archived and no forward compatibility fixes will be published. After installing, you authenticate with your Laravel Shift account and then invoke the available Shift commands against a project.
- Does laravel-shift/cli support Laravel 11 and Laravel 12?
- That is unproven. The package was last released in September 2023 and the repository is archived, so there have been no compatibility updates for Laravel 11 or Laravel 12 and no testing against PHP 8.3 or newer. Treat support for current framework versions as unknown until you run a proof of value on a disposable branch. Check Composer resolution and PHP extension requirements against your target matrix before relying on it.
- Is laravel-shift/cli safe to use as a production dependency?
- No. It is a maintenance utility, not a runtime dependency, and it should be installed globally or as a dev-only Composer requirement in isolated tooling or CI images. Adding it to production dependencies gains you nothing and exposes you to abandoned-package and dependency conflict risk. Keep it in a disposable container with pinned dependencies and controlled repository access.
- Do I need a Laravel Shift account or API token to use the CLI?
- Yes, the CLI is a front end for the Laravel Shift service, so you authenticate with your Laravel Shift account before running Shifts. That means usage depends on the remote service remaining available, and your Shift credits or plan terms apply. Confirm what code or metadata leaves your machine, how credentials are stored, and what happens to your workflow if the service or your account lapses.
- Does laravel-shift/cli modify my source files, and can I roll back?
- Automated Shifts apply code transformations to your project, so you should always run them on a clean git branch with a committed baseline. Rollback is then a git reset or branch discard rather than anything the tool provides itself. Review the generated diff carefully, since an archived tool with no upstream fixes can produce drift or silent breakage in your upgrade pipeline.
- Is laravel-shift/cli still maintained?
- No. The repository is archived and the last release was in September 2023, which means no bug fixes, no security patches, no vendor support, and no framework compatibility updates. Ownership effectively transfers to your team if you adopt it, including dependency pinning, compatibility testing, and an eventual fork or replacement plan. Project visibility is also low, so community troubleshooting will be limited.
- Can I use laravel-shift/cli in a CI pipeline?
- You technically can, by wrapping the invocation in a shared CI template inside an isolated tooling image with pinned Composer dependencies. However, CI usage multiplies the risk of drift, remote API limits, credential handling concerns, and repeated execution costs across many repositories. Do not make it a mandatory step in release-critical upgrade pipelines without a documented exit plan.
- What are the alternatives to laravel-shift/cli?
- The Laravel Shift web service covers the same automated upgrade intent without the archived CLI, while maintained tools like Rector, Laravel Pint, and PHPStan handle code transformations, style, and static analysis respectively. Custom Artisan commands are a reasonable fit for repeatable project-specific maintenance tasks. Compare output quality, runtime, and rollback effort against these before adopting an unmaintained package.
- What license does laravel-shift/cli use, and can I fork it?
- It is MIT licensed, so you can fork it, vendor it internally, and modify it for your own maintenance workflows without meaningful legal friction. The catch is that forking creates permanent ownership cost, including security review, compatibility testing, and documentation. Only fork with a named owner, a pinned version, and a defined scope of tasks it is allowed to perform.