- What is tomasvotruba/lavarle used for?
- Lavarle is a small Laravel utility package that provides Rector rules for automating framework upgrades and common code modernization tasks. It is intended to help teams apply API changes and best practices through Rector-powered automated refactoring rather than manual edits. However, the repository now lives under the deprecated-packages GitHub organization, so it should be treated as retired rather than actively developed.
- Is tomasvotruba/lavarle still maintained?
- No. The repository is hosted under the deprecated-packages GitHub organization, which is an explicit signal from the authors that the package has been retired. It also shows zero stars and zero dependents, meaning there is effectively no community backstop or production validation. Do not expect security patches or compatibility updates for new PHP or Laravel releases.
- How do I install lavarle with Composer?
- Mechanically it is a standard Composer install plus Laravel package auto-discovery, typically requiring nothing more than a composer require tomasvotruba/lavarle command. There are no complicated build steps or manual service provider registrations described. The real question is not whether you can install it but whether adoption is justified given the package's deprecated status.
- Which Laravel versions does lavarle support?
- The package dates from the Laravel 5.x through 9.x era and predates Laravel 10 and 11, so it is not being updated for current framework majors. Expect breakage on the next Laravel major or PHP minor bump because there is no maintainer tracking compatibility. Modern applications on Laravel 10+, PHP 8.2+, or strict static analysis setups are a poor fit.
- Can lavarle automate a Laravel upgrade with Rector?
- That is its stated purpose: it supplies Rector rules that codify common Laravel API changes so upgrades and refactors can be applied automatically and consistently. In practice, because the package is abandoned, you should not rely on it as the backbone of a multi-year upgrade path. Audit the individual rules you need and consider writing or maintaining equivalent Rector rules in-house.
- Does lavarle work with Laravel 10 or Laravel 11?
- There is no evidence of support for Laravel 10 or 11; the package predates both and is not receiving updates. Utility packages of this vintage frequently fail strict typing and generics checks under PHPStan or Larastan at higher levels. Treat Laravel 10+ compatibility as unverified at best and plan an alternative.
- Is lavarle safe to use in production?
- The integration cost is near zero but the integration risk is high for anything with a multi-year lifecycle. Abandonment and bus-factor risks are critical: a single maintainer has retired the package, so there is no support path and no security patching. For a throwaway internal tool it may be tolerable, but for long-lived production code it is effectively a no.
- What are alternatives to lavarle for Laravel code modernization?
- First check the first-party equivalents: Illuminate Support Str, Arr, Collection, Number, and Laravel Prompts cover most helper-style needs, and Rector itself plus maintained Laravel rule sets can handle refactoring. Commercial options such as Laravel Shift cover framework upgrades. For anything genuinely unique, copy the small implementation into an internal app Support namespace you own.
- Does lavarle register global macros, facades, or service providers?
- Utility packages of this type commonly ship an auto-discovered service provider and may register global macros, config, or facades, which increases the blast radius of bugs and the cost of removal. You should read the source and enumerate exactly which classes, macros, and side effects you actually need before adopting it. Utility packages are typically 80 percent unused surface area.
- How do I remove lavarle from an existing codebase?
- Start by enumerating every helper, macro, or behavior the application uses, then map each one to a first-party Laravel equivalent or an in-house replacement. Utility helpers are the dependency class most likely to be sprinkled everywhere, so removal gets more expensive the longer it stays. If some part is load-bearing and unique, vendor or fork it with a named owner who tracks Laravel majors.