z-song/laravel-admin

Build a full-featured administrative interface in ten minutes

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 30 minutes ago
Added to GitGenius on September 5th, 2026
Created on December 30th, 2015
Open Issues & Pull Requests: 262 (+0)
GitHub issues: Enabled
Number of forks: 2,807
Total Stargazers: 11,136 (+0)
Total Subscribers: 358 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.7 days
Mean response time: 255.6 days
90th percentile: 1008.4 days
Tracked items: 30

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 18
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 814 days
Stale 30+ days: 18
Stale 90+ days: 18

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • wontfix (6)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Laravel Admin is a Laravel package that generates administrative interfaces for managing application data.

The tool addresses the repetitive work of building admin panels by providing a rapid scaffolding system. It works by generating grid views for listing and filtering data, form interfaces for creating and editing records, and show pages for displaying individual entries. The package includes a tree component for hierarchical data and integrates directly with Laravel's Eloquent models, allowing developers to define admin interfaces through configuration rather than writing custom controllers and views.

Laravel Admin suits projects where you need a functional admin panel quickly without extensive customization. It works well for standard CRUD operations on database models and is particularly useful for content management, user administration, and data management tasks. The tool is best suited for developers comfortable with Laravel who want to avoid building admin interfaces from scratch. It may be less appropriate for projects requiring highly specialized or branded admin experiences that diverge significantly from the package's default interface patterns.

The project maintains active engagement with its codebase, regularly addressing issues and incorporating user feedback. Development shows consistent attention to bug fixes and feature requests from the community. The maintainers demonstrate responsiveness to pull requests and actively guide users through implementation questions. The project sustains ongoing refinement of its core components and continues to evolve its feature set based on practical usage patterns reported by its user base.