Download the PHP package sufyandev/laravel-migration-linter without Composer
On this page you can find all versions of the php package sufyandev/laravel-migration-linter. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download sufyandev/laravel-migration-linter
More information about sufyandev/laravel-migration-linter
Files in sufyandev/laravel-migration-linter
Package laravel-migration-linter
Short Description A lightweight Laravel package that analyzes and warns about risky database migration changes before they reach production.
License MIT
Homepage https://muhammad-sufyan5.github.io/sufyan-laravel-migration-lint-package/
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package laravel-migration-linter
🧩 Laravel Migration Linter
A lightweight Laravel package that analyzes your database migrations and warns you about risky schema changes — before they reach production.
🚀 Features
- 🔍 Detects dangerous migration patterns:
- Non-nullable columns without defaults
- Missing indexes on foreign keys
- Unsafe column drops
- Risky unique constraints
- Floating-point money fields
- Unsafe column renaming (table locks)
- Column type changes on large tables (table locks)
- Soft deletes on large tables
- ⚙️ Configurable rule severities (
info,warning,error) - 💡 Actionable suggestions — Each warning includes fix recommendations with grouped display
- 🔗 Documentation links — Every suggestion has a link to detailed docs
- 🧠 Baseline support to ignore legacy issues
- 🧾 JSON or table output for CI/CD (with suggestions included)
- 📊 HTML Reports — Generate beautiful, interactive HTML reports with charts and filtering
- 🎨 Clean output — Suggestions grouped by rule type to avoid repetition
- 🧩 Fully documented & tested (84 tests, 200 assertions)
📘 Read full rule docs:
👉 https://muhammad-sufyan5.github.io/sufyan-laravel-migration-lint-package/
📦 Installation
Install via Composer:
The package will auto-register via Laravel’s package discovery.
🧩 Usage
Run the built-in Artisan command to lint all migration files:
Common Options
| Option | Description |
|---|---|
--json |
Output structured JSON (great for CI) |
--html= |
Generate interactive HTML report (default: storage/app/...) |
--path= |
Lint a specific migration file/folder |
--baseline |
Use a custom baseline file |
--generate-baseline |
Create a baseline to ignore current issues |
--rules |
View all rules and their enabled status |
--summary |
Display summary footer in output |
--no-suggestions |
Hide suggestions (show only warnings table) |
Example Usage
Lint all migrations and export JSON:
Generate a new baseline file (ignore current issues):
Sample warning output:
📋 Scope & Limitations
What We Analyze
✅ Laravel Schema Builder Operations — All $table-> method calls
✅ Schema::create() and Schema::table() methods
✅ Column modifications via ->change()
✅ Foreign keys, indexes, constraints, timestamps
What We Don't Analyze (By Design)
⚠️ Raw SQL queries (DB::statement(), DB::raw(), etc.)
⚠️ Direct Eloquent operations (User::update(), model factories)
⚠️ Model traits and properties
⚠️ Data seeding operations
Reason: The linter focuses on statically analyzing schema builder patterns, which represent 99% of migration files. Raw SQL analysis requires different tooling.
⚙️ Configuration
You can publish the configuration file to customize rule settings:
The config file (config/migration-linter.php) allows you to:
- Set severity threshold (
info,warning,error) - Enable/disable specific rules
- Customize rule severity levels
Example configuration:
🧾 CI/CD Integration (GitHub Actions)
✨ What's New in v2.0.0
Complete SOLID Principles Refactoring
- 🏗️ 8 Core Interfaces — Dependency injection contracts for all components
- 🔧 3 Service Classes — Reusable business logic layer (LaravelConfigProvider, SeverityResolver, LintService)
- 🎨 5 Formatter Classes — Modular output system (Table, JSON, Compact, Summary, Base)
- 🔌 Dependency Injection — Automatic container bindings via service provider
- 📊 Enhanced Architecture — SOLID principles throughout (SRP, OCP, LSP, ISP, DIP)
- ✅ 144 tests passing — Comprehensive test coverage with 259 assertions
- 🔄 100% backward compatible — No breaking changes, all v1.4.0 commands work identically
- 🎯 Better table formatting — Fixed Symfony Table component for proper alignment
Migration from v1.4.0: All commands work exactly the same. No changes needed:
✨ What Was New in v1.4.0
- Suggestions System — Each warning includes actionable fix recommendations
- Documentation Links — Every issue links to detailed docs for the rule
- SoftDeletesOnProduction — New rule for detecting unsafe soft deletes on large tables
- Enhanced Reporter — JSON and table output include suggestions
- 100% test coverage with 43 passing tests
🧑💻 Contributing
Contributions are welcome! If you have an idea for a useful rule or enhancement, feel free to open a PR or issue.
🧾 License
Released under the MIT License. © 2025 Sufyan. All rights reserved.
🧠 Author
Muhammad Sufyan 📧 [email protected] 🐙 GitHub: @muhammad-sufyan5
“Smart developers don’t debug production — they lint migrations.”
📘 Full Documentation:
👉 https://muhammad-sufyan5.github.io/sufyan-laravel-migration-lint-package/
