CLI tool
tmdh/laravel-kit avatar
tmdh/laravel-kit

Laravel Kit runs Artisan from a desktop window, and two of its README links point at headings that are not there

A desktop Laravel admin panel app

1,314 stars131 forksTypeScriptGPL-2.0

At a glance

What is it?
Laravel Kit is an Electron desktop app for running Artisan commands, editing code and serving a Laravel project locally, shipped for Windows, macOS, Ubuntu, Arch and AppImage. The installers are handled carefully; the documentation is not.
Who is it for?
Laravel Kit is worth a look if you want Artisan in a window instead of a terminal and you are willing to install PHP yourself; it is the wrong choice for a Windows user who needs signed installers, for anyone on a Linux distribution outside Ubuntu and Arch, or for anyone who needs a stated PHP or Laravel version before committing.
Can I use it commercially?
Yes, with conditions. GPL-2.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Activity is slowing. The repository last received commits 6 months ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • tmdh/laravel-kit1,314 ★ · -3
Star history
Repository2026-09-112026-11-15
tmdh/laravel-kit1.3k1.3k

-3 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The one line description promises an admin panel the feature list never mentions

The repository summary calls this a desktop Laravel admin panel app. Nothing in the feature list builds an admin panel. The six bullets are no configuration required, running Artisan commands from a nice interface, editing the project in a code editor, serving the application locally from a button, a VSCode inspired dark theme, and Artisan commands retrieved from your Laravel project. There is no mention of models, controllers, migrations, views, routing or authentication. What you get is a front end for a Laravel project you already have, reading the commands that project exposes. The README's own subtitle is the accurate one: a desktop application for managing your Laravel applications. The summary line is not.

No configuration required, stated directly above a PHP prerequisite

The first line of the installation section is the whole prerequisite list: PHP must be installed in your system. There is no version number for it, no PHP extension list, and no Laravel version anywhere in the file, even though the app's usefulness depends entirely on what your project exposes through `artisan list`. The no configuration bullet is about the app's own settings, not about the environment behind it. Nothing is asked for on first launch and nothing has to be pointed at a project path in a config file. What you do have to supply is a working Laravel installation on the same machine, since the commands are retrieved from it at runtime rather than bundled with the app.

Five install routes, and the Ubuntu one is pinned to a version number

Windows takes a setup executable from the releases page, and that route is the only one with a stated behaviour afterwards: updates are checked automatically. macOS is recommended through Homebrew:

bash
brew install laravel-kit --no-quarantine

The alternative there is a dmg from the releases page, with the warning that the dmg release is not code signed and a pointer to install instructions kept in a comment on issue 40. Ubuntu and its derivatives get a deb fetched by URL:

bash
wget https://github.com/tmdh/laravel-kit/releases/download/v2.0.9/laravel-kit_2.0.9_amd64.deb
sudo apt install ./laravel-kit_2.0.9_amd64.deb

Both the path and the filename carry the version, and the target is `amd64`, so the documented command keeps naming build 2.0.9 after a newer tag appears. Arch Linux goes through the AUR package `laravel-kit`. Everything else gets an AppImage and the sentence that proper methods will be added very soon.

The dependency list spells out what each button really executes

The runtime dependencies are a readable map of the features. `which` locates the PHP binary on the system, and `execa` spawns the processes behind every Artisan call. `strip-ansi` at 7.0.1 removes terminal escape sequences from command output before it is rendered, which is what makes Artisan output readable in a window at all. `monaco-editor` at 0.52.0 is the editor behind the bullet about tinkering with the project. `tree-kill` handles the process tree behind the serve button, so stopping it does not leave a stray PHP server holding the port. `electron-store` at 8.0.1 persists settings between launches, and `electron-updater` at 4.6.1 is the whole of that automatic update check on Windows. `anser` handles prompts, `vuex` holds state, and `vue` 3.2.29 drives the interface.

Private in package.json, so there is no package manager route at all

One line in package.json decides how you cannot install this. The package is marked private, which means it is never published to a registry, so `npm install laravel-kit` or a yarn equivalent has nothing to resolve. The same file also rules out treating it as a library: it is an application, its entry point is `dist/main.js`, and its build scripts are the ones you would run yourself. The dependency surface is correspondingly narrow, with no Laravel or PHP package in it at all, because the app talks to your project by running the project's own Artisan binary. Everything framework specific comes from the project on disk, which is also why the app cannot tell you which Laravel versions it supports.

Development runs two processes, and one script the README leaves out

The build flow is split in a way that trips up first-time contributors. Development needs both halves running: one starts the Vite dev server, the other builds and launches Electron.

bash
# Start development server with Vite
yarn run dev:one
# Start Electron
yarn run dev:two

The second of those runs `node build.js --dev && electron .`, so it depends on `build.js` at the repository root and on the Vite server being up. Production is the same pair in sequence, `yarn run prod` followed by `yarn run pack`, where pack calls electron-builder with a directory build. package.json also defines a `start` script that runs `electron .` directly, and the README's command list never mentions it. The root carries both `jsconfig.json` and `tsconfig.json` for a repository whose primary language is TypeScript, and the eslint parser options stop at ecmaVersion 2018.

Two navigation links have no heading behind them

The header of the file is HTML rather than Markdown, with a centred title block, a version badge pointing at the latest release, and a row of links. Features and Documentation have real targets. The other two do not. Installation links to the anchor `#download`, and Contribution links to `#contribution`, while the headings in the file are Features, Installation, Screenshots, Development and Documentation. There is no Download heading and no Contribution section anywhere, so both links land at the top of the page. The contribution material does exist, just somewhere else: it is scattered across the wiki link and the development commands. The Screenshots section fares no better, since its Light and Dark table has headers and empty cells.

The newest tag is about fifteen months older than the last commit

Three releases are published: v2.0.7 in October 2022, v2.0.8 in February 2023, and v2.0.9 in February 2025. The version field in package.json reads 2.0.9, matching the newest tag, and the last commit to the repository landed on 2026-05-01. So the source tree has moved well past the newest downloadable build, and the master branch is where any newer work sits. Two other details point the same way: the copyright line in the README still ends at 2022, and the Ubuntu download command still names build 2.0.9. Anyone building from source gets the newer code; anyone installing from the releases page gets the February 2025 one.

Editorial conclusion

Laravel Kit is worth a look if you want Artisan in a window instead of a terminal and you are willing to install PHP yourself; it is the wrong choice for a Windows user who needs signed installers, for anyone on a Linux distribution outside Ubuntu and Arch, or for anyone who needs a stated PHP or Laravel version before committing. Verify three things before the first run: that your `php` binary is on the path the app can find, which Laravel version your project actually exposes to `artisan list`, and whether the build you installed matches the source, since the newest tag predates the last push by about fifteen months.

Frequently asked questions

What does Laravel Kit do?

It is a desktop application for managing Laravel applications, built with Electron, Vue.js 3, Tailwind CSS and Vite. Its features are running Artisan commands retrieved from your project, editing code in a built in editor, and serving the application locally from a button.

Does Laravel Kit need PHP installed?

Yes. The installation section opens with the single prerequisite it names: PHP must be installed in your system. No PHP version is given, and no Laravel version is named either, so the range you can use is decided by your own project.

How do I install Laravel Kit on macOS?

The recommended route is Homebrew, with the command `brew install laravel-kit --no-quarantine`. A dmg from the releases page is the alternative, and the file warns that the dmg release is not code signed, with install instructions kept in a comment on issue 40.

Which platforms have install instructions for Laravel Kit?

Windows uses a setup executable from the releases page, macOS uses Homebrew or a dmg, Ubuntu and derivatives use a deb fetched with wget and installed with apt, Arch Linux uses the AUR package named laravel-kit, and other distributions get an AppImage only.

Can I install Laravel Kit with npm?

No. The package is marked private in package.json, so it is never published to a registry and a package manager has nothing to resolve. The supported routes are an exe, a dmg, a deb, an AUR package and an AppImage.

Official sources

  1. License: GPL-2.0
  2. Project website
  3. README
  4. Releases
  5. tmdh/laravel-kit on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/tmdh-laravel-kit.svg)](https://hysenlabs.com/projects/tmdh-laravel-kit)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/tmdh-laravel-kit.svg)](https://hysenlabs.com/projects/tmdh-laravel-kit)

Was this useful?