# Litstack: a Laravel admin panel scaffold that stopped growing

> Litstack is an MIT licensed Laravel package that generates content administration panels for users, models and free form page content, with a Vue front end built through Laravel Mix. The project is in maintenance only mode, so the interesting question is what the scaffold still gives you and what it no longer will.

**litstack/litstack** — Build content-administration-panels in Laravel

- Repository: https://github.com/litstack/litstack
- Website: https://litstack.io
- Stars: 860 · Forks: 80
- Language: PHP
- License: MIT
- Published: 2026-10-20 · Updated: 2026-10-20 · Language: en
- Canonical page: https://hysenlabs.com/projects/litstack-litstack

## Admin panels for Laravel applications that have grown content

Litstack describes itself as a package for building admin interfaces that help maintain the data of your applications. The target is not a generic dashboard but the tedious back office that appears once a Laravel application has real users, real models and pages whose text and images need editing by people who do not write code.

The feature surface is described in one sentence: an intuitive interface plus the tools to manage a project's Users, Models and free Forms for Pages, Settings and similar content. The package.json description makes the same point from the other side, calling Litstack a multilanguage admin panel and cms scaffolding package that helps you create CRUD in seconds via Artisan commands, and that lets you manage the static content of each website page, with headlines, text and images, alongside the repetitive mixed content you define.

Two properties of that description matter for an evaluation. Multilanguage support is built in rather than bolted on, which matters for any application with more than one locale. And the content model is free form, so the same panel can hold pages, site settings and custom collections instead of forcing everything into one rigid blog schema. The stated audience is Laravel developers, and the documentation assumes familiarity with Laravel standards.

## The repository layout separates PHP package, front end and publishable assets

The top level entries show a package with three distinct parts. `composer.json` holds the PHP side, `src/` holds the Laravel package code, and `package.json` with `webpack.mix.js`, `mix-manifest.json` and `.babelrc` holds the front end build. `resources/` contains the JavaScript, Vue and Sass sources, `public/` the compiled output, and `publish/` the assets a host application publishes into its own directory.

`stubs/` sits beside them, which is the marker of a scaffolding package rather than a plain library. Stubs are the template files the Artisan commands copy into an application, so the generated panel is code the team then owns and edits. `tests/` holds both PHP tests, driven by `phpunit.xml`, and JavaScript tests, and `fixer/` holds a code style helper. `CHANGELOG-3.x.md` confirms that the 3.x line is the tracked release line, matching the `3.x` default branch.

For a team deciding whether to adopt this, the layout is the honest description of the design. Nothing in it is hidden behind a service: the panel runs inside your Laravel application, your database and your authentication, and the files that render it are published into your repository. The cost of that choice is that upgrades are manual merges, which becomes the central problem once the project is no longer actively developed.

## The front end is Vue components compiled by Laravel Mix

The JavaScript toolchain is the part of the project that explains its second topic tag. The npm scripts in `package.json` drive Laravel Mix: `dev` maps to `npm run development`, which runs `mix`, `watch` maps to `mix watch`, `hot` maps to `mix watch --hot`, and `prod` maps to `npm run production`, which runs `mix --production`. There is also a polling variant, `mix watch -- --watch-options-poll=1000`, for filesystems where native watch events are unreliable.

The Jest configuration inside the same file handles `.js`, `.jsx` and `.vue` files, transforming Vue single file components through `vue-jest` and JavaScript through `babel-jest`. Path aliases are defined for the project itself, with `@lit-js` and `@lit-sass` mapping into `resources/js` and `resources/sass`, plus a `lit-test` alias pointing at the JavaScript test bootstrap. `mix-manifest.json` at the root records the compiled asset names that the PHP side looks up.

So the runtime asset pipeline is conventional for its era: Vue components compiled by Mix, Sass compiled by Mix, and a manifest that tells Laravel which hashed file to load. That design is dated in one respect, since Mix itself has been superseded by Vite in newer Laravel starter kits, which is relevant for anyone pairing this package with a current application skeleton.

## Getting Litstack and running the documented npm workflow

The README does not print a Composer install command, so there is nothing to copy here for the PHP side. The package is distributed through Packagist, where the README links the download badge to `packagist.org/packages/litstack/litstack`, and the official documentation lives at `litstack.io/docs`, with the introduction telling you to learn how to build your custom admin panel using your knowledge of Laravel standards. The version badge points at the latest stable release on the same Packagist page.

What the repository does document is the front end workflow, through the npm scripts in `package.json`. The individual commands behind those scripts are:

```bash
npm run test:js && npm run test:php
npm run development
mix watch
npm run production
```

The first line is what the `test` script runs, chaining the JavaScript test suite to the PHP suite. The second compiles assets for development, the third recompiles on change while you work, and the last produces a production build with `mix --production`. Working on a panel therefore means running the watcher while you edit `resources/js` and `resources/sass`, and running both test suites before you ship.

The documentation also points to a contribution guide on `litstack.io/docs/prologue/contribution`, and the project runs a Discord channel that the README invites people to join. Keep in mind the build tooling is the documented part of the workflow, while the Artisan commands that generate the panel itself are described only in prose in the package description, so read the docs site for the exact command names before scripting them.

## Discontinued, but maintained only for severe problems

The first thing the README says is that development has been discontinued and the project is in maintenance only mode, with fixes limited to severe problems the maintainers hit in their own production projects that use Litstack. Bug fixes and pull requests from outside contributors are still welcomed. The repository is not archived, so the code and the branches remain accessible.

The dates tell the rest of the story. The last push was on 2026-06-02, which coincided with the v3.8.6 release. Before that came v3.8.5 on 2025-07-28 and v3.8.4 on 2025-04-14, a gap of roughly ten months between the two most recent releases before the final push. That is the profile of a project where maintenance follows the maintainers' own needs rather than a published schedule.

For an adopter this changes the nature of the risk. In a package with active development, an upgrade brings fixes and a changelog entry. Here, an upgrade brings whatever the maintainers happened to need, and the security questions are yours. The MIT licence means you can fork the package and carry it yourself, which is the mitigation that actually exists, but it also means you take on the merge work that the discontinued upstream would otherwise have handled.

## Where Litstack stops being the right answer

Several situations rule this package out. If you are starting a new Laravel application with a new admin panel, adopting a discontinued scaffold means accepting a code base whose front end pipeline is built around Laravel Mix while your application skeleton is likely on Vite, and you will own that mismatch from day one. If your admin panel needs a workflow that does not fit CRUD plus free form content, the free form pages and settings model will need custom code on top of the package rather than configuration inside it.

There is also a documentation limit worth naming. The README is short. It states the purpose, links to `litstack.io/docs` for the real instructions, and lists the licence, the Discord channel and the contribution guide. It does not document version compatibility for specific Laravel releases, does not enumerate the Artisan commands it provides, and does not say what happens to generated admin code when the package is upgraded. You will be reading the docs site, not the repository, to answer most operational questions.

None of this makes the package defective. It makes it a snapshot: a complete, coherent admin layer that was good enough to be used in production by the maintainers, and that now carries its own upgrade debt.

## The real alternative is owning the panel outright

The obvious alternative is not another package but a different allocation of work: assemble the admin panel yourself from Laravel's own models, controllers, policies and forms, with a Vue or Livewire front end written by your team, and publish it as an internal package if several applications need it.

The difference in approach is ownership of the cost curve. Litstack front loads the work. The Artisan driven scaffolding creates CRUD for your models, the users area and the free form page content, and the published assets mean you start from a working panel rather than from a blank route file. Writing it yourself starts slower and then never needs to reconcile a published admin panel with a dependency that no longer ships upgrades.

That trade is worth taking when the panel is small and stable, when the team already knows the framework deeply, or when the application has admin requirements that no generic CRUD scaffold will fit. Litstack earns its place when the admin area is broad, when several team members need a working interface immediately, and when the cost of building a multilingual content backend from zero is the dominant cost in the project.

## Conclusion

Litstack still fits teams that want a prebuilt CRUD and content layer for a Laravel application they already maintain, and the MIT licence leaves the source free to fork. It does not fit teams starting a new admin panel today, because the project is in maintenance only mode and the last push was on 2026-06-02. Verify first whether the release you install, on the 3.x branch, still matches your Laravel version, and whether you are willing to own the fork before a breaking change appears.

## FAQ

### Is Litstack still maintained?

Development is discontinued and the project is in maintenance only mode, with only severe problems fixed for the maintainers' own production projects. The last push was on 2026-06-02, alongside the v3.8.6 release.

### What does the Litstack package actually give me in a Laravel app?

It provides an admin interface for managing your project's users, models and free form content for pages and settings, with CRUD created through Artisan commands and page content covering headlines, text and images. Multilanguage content is part of the description.

### How do I build the Litstack front end assets locally?

The npm scripts in `package.json` drive Laravel Mix: `dev` runs `npm run development`, `watch` runs `mix watch`, `hot` runs `mix watch --hot` and `prod` runs `npm run production`, which executes `mix --production`. Vue and JavaScript tests run through Jest with `vue-jest`.

### What licence is Litstack released under?

The package is open sourced under the MIT licence, with the licence file at the repository root. Pull requests fixing bugs are still welcomed by the maintainers.

## Sources

- [License: MIT](https://github.com/litstack/litstack/blob/3.x/LICENSE)
- [litstack/litstack on GitHub](https://github.com/litstack/litstack)
- [Project website](https://litstack.io)
- [README](https://github.com/litstack/litstack/blob/3.x/README.md)
- [Releases](https://github.com/litstack/litstack/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/litstack-litstack