Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Laravel Console List Columns

Laravel Console List Columns Laravel Package

romanzipp/laravel-console-list-columns

A small Laravel package that lets you list a database table's columns directly from the console, showing names, types, and attributes in a clean table. Handy for quickly inspecting schemas while debugging migrations or models.

View on GitHub
Deep Wiki
Context7

List database tables columns & information.

Frequently asked questions about Laravel Console List Columns
What is romanzipp/laravel-console-list-columns used for?
It is a Laravel developer tool that adds a single Artisan command to list a database table's columns directly in the console. The output shows column names, types, and attributes in a clean table, which is handy for quickly inspecting schemas while debugging migrations or Eloquent models. It is not intended for application runtime.
How do I install romanzipp/laravel-console-list-columns?
Install it as a dev dependency with composer require --dev romanzipp/laravel-console-list-columns. Laravel's package auto-discovery registers the service provider and command automatically, so no config publishing or migrations are needed. After installation, the command appears in php artisan list.
Which Laravel versions does romanzipp/laravel-console-list-columns support?
The package does not publish an explicit compatibility matrix. Version 1.2.2 switched to symfony/console, which Laravel already ships, but you should verify the composer.json constraint against your Laravel 9, 10, or 11 installation. The maintainer has not documented a formal support range, so test before adopting it in a shared project.
Does it work with MySQL, PostgreSQL, SQLite, and SQL Server?
It introspects driver-specific metadata—for example, information_schema for MySQL, pg_catalog for PostgreSQL, PRAGMA for SQLite, and SQL Server system views. The package does not document driver coverage, and the technical assessment flags driver-coverage risk as medium. Test on your target database before relying on the output.
Can I use this package in production?
No, it is developer tooling and should be installed with --dev only. It performs read-only schema introspection but can print connection and schema details into logs, which is a minor leak vector in CI or production. Keep it out of your production autoload path.
How is it different from Laravel's native db:table or db:show commands?
Laravel 10.30+ and 11 include native db:table and db:show Artisan commands that provide similar schema inspection. This package is a convenience wrapper with no unique capability, so its substitutability is high. You can often achieve the same result with native commands or raw information_schema queries.
Is romanzipp/laravel-console-list-columns actively maintained?
Maintenance is low-activity with a single maintainer; the 1.2.2 release shows recent dependency hygiene but not a long-term support commitment. The package has 5 stars, 0 dependents, no published compatibility matrix, and no evident security policy. Treat it as a convenience tool rather than a critical dependency.
Did the output format change in version 1.2.2?
Yes. Version 1.2.2 replaced the phplucidframe/console-table renderer with symfony/console, so the table borders, padding, and text wrapping may look different. This is a cosmetic but observable change; any script or snapshot that parsed the old output will need to be re-baselined. The release was tagged as a patch, so review before upgrading in automated pipelines.
What command does it provide and how do I list a table's columns?
The package registers one Artisan command that lists a database table's columns with names, types, and attributes in a table format. After installation, run php artisan list to locate the command, then pass the table name as an argument. It is designed for quick interactive inspection, not for scripting.
Is it safe to run? What are the security concerns?
The security surface is negligible: it performs read-only introspection, runs only in the console, and makes no network calls. The only leak vector is printing connection or schema details into CI logs. Install it with --dev and avoid running it in shared production environments.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
dbravoan/dbcms-admin-theme-dbcms
dbravoan/dbcms-theme-db-cyber
dbravoan/dbcms-blocks-basic
dbravoan/dbcms-module-content-audit
dbravoan/dbcms-module-ai-assistant
paygate-to/paygate-php
padosoft/askmydocs-connector-base
defstudio/supercharged-carbon
bernskioldmedia/laravel-matomo
bernskioldmedia/laravel-harvest
bernskiold/laravel-data-scrubber
bernskiold/laravel-currency-converter
bernskiold/laravel-campaign-monitor
bernskioldmedia/laravel-autotranslate
siberfx/telegram-bot
roy-sandip/laravel-view-extended
gregsphotography/site-builder-core
roy-sandip/laravel-view
anodyne/blade-fluentui-icons
webx-ui/module-catalog-collections