PHPackages                             levizoesch/laravel-check-migrations - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [CLI & Console](/categories/cli)
4. /
5. levizoesch/laravel-check-migrations

ActiveProject[CLI & Console](/categories/cli)

levizoesch/laravel-check-migrations
===================================

A Laravel command scans your application for pending migrations, providing a clear overview of what needs to be migrated.You can then choose to run individual migrations or skip them as needed, short-cutting and optimizing your development workflow.

1.0.2(2y ago)1486↓100%MITPHPPHP ^7.0|^8.0

Since Mar 27Pushed 2y ago1 watchersCompare

[ Source](https://github.com/levizoesch/laravel-check-migrations)[ Packagist](https://packagist.org/packages/levizoesch/laravel-check-migrations)[ RSS](/packages/levizoesch-laravel-check-migrations/feed)WikiDiscussions main Synced 1mo ago

READMEChangelog (3)DependenciesVersions (4)Used By (0)

Check Migrations
================

[](#check-migrations)

A Laravel command scans your application for pending migrations, providing a clear overview of what needs to be migrated. You can then choose to run individual migrations or skip them as needed, short-cutting and optimizing your development workflow.

Support for Structured Migrations
---------------------------------

[](#support-for-structured-migrations)

This package seamlessly handles migrations organized within subdirectories, ensuring that no pending migrations are overlooked regardless of the project's migration structure.

```
database
└── migrations
├── 2023_01_01
│ ├── 20230101000001_create_table_one.php
│ └── 20230101000002_create_table_two.php
└── 2023_02_01
├── 20230201000001_create_table_three.php
└── 20230201000002_create_table_four.php
```

Installation
------------

[](#installation)

```
composer require levizoesch/laravel-check-migrations
```

Usage
-----

[](#usage)

Run the following command in your terminal:

#### This will display pending migrations and prompt for confirmation before running each one.

[](#this-will-display-pending-migrations-and-prompt-for-confirmation-before-running-each-one)

```
php artisan check-migrations
```

#### This will skip confirmation and run pending migrations directly.

[](#this-will-skip-confirmation-and-run-pending-migrations-directly)

```
php artisan check-migrations --skip
```

#### This will ignore the migration named 20230101000000\_create\_example\_table from running and prompting for confirmation.

[](#this-will-ignore-the-migration-named-20230101000000_create_example_table-from-running-and-prompting-for-confirmation)

```
php artisan check-migrations --ignore=20230101000000_create_example_table
```

### Notes

[](#notes)

Ensure that your Laravel project is properly configured and migrations are set up correctly for this command to work effectively.

Always review pending migrations before running them in production environments to prevent unintended consequences.

Known Issues
------------

[](#known-issues)

### Double Confirmation Prompts in Production

[](#double-confirmation-prompts-in-production)

When running the `check-migrations` command in a production environment, users may encounter double confirmation prompts. This occurs due to Laravel's native `migrate` command prompting for confirmation before migrating when in production mode. Since the `check-migrations` command internally calls the `migrate` command for each pending migration, users may be prompted twice for confirmation for each migration.

###  Health Score

25

—

LowBetter than 37% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity15

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity48

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~0 days

Total

3

Last Release

776d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/a7345e75059e49fd6d8b2ba9ac99d10f313e829a80ad55f92901816a79d261e2?d=identicon)[levizoesch](/maintainers/levizoesch)

---

Top Contributors

[![levizoesch](https://avatars.githubusercontent.com/u/18410490?v=4)](https://github.com/levizoesch "levizoesch (2 commits)")

---

Tags

laravellaravel-helperslaravel commandsLevi ZoeschLaravel Check Migrations

### Embed Badge

![Health badge](/badges/levizoesch-laravel-check-migrations/health.svg)

```
[![Health](https://phpackages.com/badges/levizoesch-laravel-check-migrations/health.svg)](https://phpackages.com/packages/levizoesch-laravel-check-migrations)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)