Framework
laravel/tinker avatar
laravel/tinker

Laravel Tinker: a REPL whose manual lives in the Artisan docs, now on the 3.x line

Powerful REPL for the Laravel framework.

7,442 stars140 forksPHPMIT

At a glance

What is it?
Laravel Tinker is the Laravel organization's interactive PHP shell for Laravel applications. This review covers what the repository itself tells you, where the real documentation lives, and what to check before moving from 2.x to 3.x.
Who is it for?
Adopt laravel/tinker if you work in a Laravel application and want an interactive PHP shell that starts inside the framework: the MIT license and the 2026 release activity (v3.0.2 on 2026-04-14, last push on 2026-10-16) raise no adoption blockers. Skip it for PHP projects that do not use Laravel, where it adds a dependency and gives nothing back.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 5 days ago.
What is it written in?
Mainly PHP, according to GitHub's language statistics.

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

From daily snapshots

Star history

  • laravel/tinker7,442 ★ · +2
Star history
Repository2026-10-072026-11-21
laravel/tinker7.4k7.4k

2 Stars in the last 45 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Tinker's usage manual sits inside the Artisan chapter of the Laravel docs

Laravel Tinker is a read-eval-print loop for the Laravel framework: you type a line of PHP, the shell evaluates it, prints the result and waits for the next line. The repository's own description stops at calling it a REPL "for the Laravel framework". How to start it, what it can reach and how to configure it are all delegated elsewhere.

The project homepage is https://laravel.com/docs/artisan#tinker, an anchor inside the Artisan page of the Laravel documentation rather than a site of its own. That placement says something about how the Laravel team treats the package: as one piece of the Artisan console tooling, not as a product with a separate manual.

For someone reading the GitHub repository, the consequence is direct. The README has six short sections (Introduction, Official Documentation, Contributing, Code of Conduct, Security Vulnerabilities, License) and no example session, no screenshot of a prompt and no list of commands. Anyone evaluating Tinker from GitHub alone has to open the Laravel docs before learning how to launch it.

How to install Tinker when the README has no command: Packagist and composer.json

The README of laravel/tinker does not include an install command, and guessing one is a poor substitute for the source the project names. What the repository does show is the distribution channel. The badge row at the top of the README links to packagist.org/packages/laravel/tinker, the Packagist page for the package, and a composer.json file sits at the repository root. Those two facts mark Tinker as a Composer package published through Packagist, written in PHP.

For the exact require line and the console command that opens the shell, follow the Artisan anchor on laravel.com. That indirection has a cost for anyone who manages dependencies carefully. The repository front page gives no table matching Tinker lines to Laravel releases, so the version constraint you write into composer.json has to be checked by hand.

The file to read is composer.json in the tag you intend to install. Its require block states which PHP and framework versions that tag accepts, which is the only compatibility statement the repository itself makes.

The jump from v2.11.1 to v3.0.0 arrives without upgrade notes in the README

The recent release history is short. v2.11.1 was tagged on 2026-02-10. v3.0.0 followed on 2026-03-17, and v3.0.2 on 2026-04-14. The default branch is 3.x, so anyone browsing the repository sees 3.x code first and new work targets that line.

A new major version number is the conventional signal that something incompatible moved. The README says nothing about what changed between 2.x and 3.x. For an application still pinned to the 2.x line, that silence matters: the front page cannot tell you whether your existing habits in the shell, or any published Tinker configuration, survive the move.

CHANGELOG.md at the repository root is the file to read before widening a Composer constraint from 2.x to 3.x. v3.0.2 landed four weeks after v3.0.0, so anyone who installed 3.0.0 on release day should compare the entries for both tags. If the changelog does not answer a specific question about your setup, do the upgrade on a branch and open the shell there before merging.

config/, src/ and tests/: what the repository layout shows about the package

The top level of the repository is small: config/, src/, tests/, art/ and .github/, plus composer.json, CHANGELOG.md, LICENSE.md and README.md. Several dotfiles show how the code is policed. phpunit.xml.dist configures the PHPUnit suite whose cases live in tests/. phpstan.neon.dist configures PHPStan static analysis. .styleci.yml holds StyleCI formatting rules, and .editorconfig sets editor defaults. The first README badge links to the repository's GitHub Actions page, so checks run in CI from workflows under .github/.

The config/ directory is the detail most relevant to users. Its presence means Tinker ships configuration of its own, separate from your application code. The README does not name a single key, default value or environment variable from it.

That gap has a practical consequence. If you want to change how the shell behaves in a project, nothing on the repository front page will tell you which knob to turn. Open the files under config/ in the tag you installed and read them directly, then cross-check against the Artisan documentation page.

Every line runs as soon as you press enter, so Tinker is the wrong place for repeatable work

A REPL trades reproducibility for immediacy. Each statement is evaluated the moment you submit it, and nothing about the session becomes code in your repository. That is exactly what you want when inspecting an object or checking what a helper returns.

It turns into a liability when the same steps must run again next week, on another machine, or pass review by a colleague. A sequence of statements that corrects data in a Tinker session leaves no migration, no test and no commit behind. Six months later, nobody can tell what was changed or why.

Mistakes get the same treatment. A statement with side effects runs against the application the shell was opened in, with no dry run step between typing and executing. The README of laravel/tinker does not discuss access control, confirmation prompts or any safeguard for shared or production servers, so whether a framework REPL may be opened there is a decision your team has to make on its own. For anything you will repeat, write it as code that lives in version control and run that instead.

PHP's built-in interactive mode versus a REPL that starts inside your Laravel application

PHP's command-line binary already has an interactive mode that evaluates code line by line. It is present wherever the PHP CLI is installed and needs no Composer package at all. The difference from Tinker is context. Plain interactive PHP starts empty: no autoloader, no framework and none of your application's classes unless you include files by hand.

Tinker's reason to exist is the phrase "for the Laravel framework". The loop is meant to start inside a Laravel application rather than in a bare interpreter, so the code you type can work with the framework you already depend on.

That makes the choice straightforward. If your project is not a Laravel application, Tinker gives you nothing over the interpreter's own interactive mode and adds a dependency to composer.json. If it is a Laravel application, the trade reverses: you accept one more package, and in return you skip the manual bootstrapping that a bare interactive session would require every time you open it.

Release pace, the MIT license and where Tinker vulnerability reports go

The last push to the repository was on 2026-10-16, and it is not archived. The three most recent tags fall between February and April 2026, so the 3.x line is current rather than dormant.

Laravel Tinker is released under the MIT license, with the full text in LICENSE.md. MIT permits use inside commercial and closed-source applications provided the copyright and permission notice is kept with copies of the software. For a Laravel application that pulls Tinker in through Composer, that is a light obligation, though anything unusual about your distribution model is a question for your own counsel.

Security issues have a dedicated route. The README asks reporters to review the security policy at github.com/laravel/tinker/security/policy for how to report a vulnerability. Contributions follow the general Laravel contribution guide at laravel.com/docs/contributions, and participants are asked to abide by the Laravel Code of Conduct. Tinker does not publish separate rules of its own on any of these points: contribution, conduct and documentation all point back to the framework's pages.

Editorial conclusion

Adopt laravel/tinker if you work in a Laravel application and want an interactive PHP shell that starts inside the framework: the MIT license and the 2026 release activity (v3.0.2 on 2026-04-14, last push on 2026-10-16) raise no adoption blockers. Skip it for PHP projects that do not use Laravel, where it adds a dependency and gives nothing back. Before moving an application from 2.x to 3.x, read the v3.0.0 entry in CHANGELOG.md and the files under config/, because the README covers neither.

Frequently asked questions

How do I install Laravel Tinker?

The laravel/tinker README gives no install command. It is a Composer package listed at packagist.org/packages/laravel/tinker, and setup and usage are documented on the Laravel website at laravel.com/docs/artisan#tinker.

What is the latest Laravel Tinker release?

The most recent tagged release is v3.0.2, published on 2026-04-14. It follows v3.0.0 from 2026-03-17 and v2.11.1 from 2026-02-10, and the default branch is 3.x.

What license does Laravel Tinker use?

Laravel Tinker is open-source software under the MIT license, with the license text in LICENSE.md at the repository root.

How do I report a security vulnerability in Laravel Tinker?

The README points to the project's security policy at github.com/laravel/tinker/security/policy, which explains how to report vulnerabilities.

Official sources

  1. laravel/tinker on GitHub
  2. License: MIT
  3. Project website
  4. README
  5. Releases
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/laravel-tinker.svg)](https://hysenlabs.com/projects/laravel-tinker)

Star history chart for your README

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

Was this useful?