LaRecipe serves docs from your own Laravel app, and its front end still runs on Mix 2
✏️ Write gorgeous documentation for your products using Markdown inside your Laravel app
At a glance
- What is it?
- LaRecipe is a Laravel package that puts product documentation inside the host application at a /docs endpoint, installed with a composer require and one artisan command. The repository is small and the README is a pointer to a separate manual site, so the useful detail sits in the manifest: five namespaces for one product, two lockfiles, and a webpack toolchain several majors behind the PHP side.
- Who is it for?
- Worth it if you want documentation hosted on the same domain and inside the same deploy as the product, and you are on a Laravel version that still tolerates a Vue 2 asset pipeline. Before installing, check that binarytorch/larecipe is the package your project actually wants, since the repository, the add-ons and the funding page all sit under different names, and pin a version rather than tracking the 2.9 line.
- 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 16 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 15, 2026, and from our analysis. They are not legal advice.
Star history
- saleem-hadad/larecipe2,531 ★ · +17
| Repository | 2026-09-29 | 2026-11-15 |
|---|---|---|
| saleem-hadad/larecipe | 2.5k | 2.5k |
17 Stars in the last 47 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The manual lives on a separate site and the README is a pointer to it
The README in this repository is about 166 words, and most of it is links. The feature description is a single sentence: LaRecipe is a code-driven package that provides an easy way to create documentation for a product or application directly inside the Laravel app. Everything else points outward, to the full documentation hosted at larecipe.saleem.dev, which is also the repository's declared homepage, and to a contributors page. What that means for anyone reading the source is that the interesting material is not here. The Markdown dialect the package consumes, the configuration keys, the layout and menu options and the caching behaviour all live on the documentation site, not in this tree. The README's own workflow is three steps: install the package through composer, run the install command, then visit your app domain with the /docs endpoint. Nothing else about the setup is described in the repository.
One product spread across five different namespaces
The names do not line up, and the install command is where it shows. The repository is saleem-hadad/larecipe, the composer package you install is binarytorch/larecipe, and the four official add-on packages are documented under the binarytorch namespace on the manual site: LaRecipe Dark Theme, LaRecipe RTL Support, LaRecipe Feedback and LaRecipe Swagger. Funding lives at opencollective.com/larecipe, recorded both as a Sponsors anchor in the README and as a collective block in the manifest. The in-progress .NET version lives under a third organisation entirely, at github.com/larecipe/larecipe-dotnet. So the same product is reachable under two personal or organisation handles, one vendor prefix that only applies to composer, one funding domain and one port repository. Anyone following a tutorial that says to require the repository name instead of the vendor name will not find it.
Two lockfiles at the root, and npm scripts that assume one of them
Both package-lock.json and yarn.lock are committed in the same tree, and every script in the manifest is written for npm, since the aliases are invoked as npm run development, npm run watch and npm run production. That combination is the ordinary way a Laravel package repository drifts: the npm path was set up first, yarn was added later without the npm lockfile being removed, and now two contributors on two package managers resolve two different dependency trees from the same source. The scripts themselves reach into node_modules directly, running node_modules/webpack/bin/webpack.js and node_modules/webpack-dev-server/bin/webpack-dev-server.js with a config path under node_modules/laravel-mix, which means a half-finished install produces a missing file error rather than a helpful message. For a package whose selling point is documentation that ships with your app, the asset build is the part least pinned.
Laravel Mix 2, Vue 2 and a tailwindcss 0.7 line, on a package built for modern Laravel
The dependency set dates from the Laravel 5 era even though the package installs through a current artisan command. laravel-mix is held at ^2.0 and webpack-dev-server at ^3.7.2, cross-env at ^5.1, vue at ^2.6.10 and jquery at ^3.4.0. tailwindcss is at ^0.7.4, a major version that predates most of the utility classes a documentation theme would use today, and vue2-transitions is pinned to the exact version 0.2.3 with no caret at all, so that one can never float. axios ^0.30.2, docsearch.js ^2.6.3, medium-zoom ^1.0.4 and clipboard ^2.0.4 fill out the runtime side, and tar ^4.4.10 sits in devDependencies, which is an odd thing to need for building stylesheets. The committed webpack.mix.js, tailwind.js and mix-manifest.json show the asset output is built and checked in. The gap between a PHP side that speaks to whatever Laravel you run and a JavaScript side stuck on Vue 2 is the single fact to weigh before choosing this package for a new application.
postinstall fires an Open Collective hook, but only inside a clone of this repository
The manifest sets postinstall to opencollective-postinstall, and both opencollective and opencollective-postinstall are devDependencies, with a collective block naming opencollective.com/larecipe as the type and url. Since the manifest is also marked private, that hook fires when someone installs this repository's own development dependencies inside a clone, which is the normal case for a contributor, and not when an application pulls the composer package into vendor. It is worth naming precisely because the pattern looks alarming in a manifest and is harmless here: the funding acknowledgement matches the Sponsors anchor already in the README. What it does add is one network call during setup, and a failure mode where a fresh clone stops partway through install for a reason that has nothing to do with the code.
Six script aliases funnel into the same Mix webpack config
The build surface is small and repetitive. dev is an alias for development, prod is an alias for production, and watch exists alongside watch-poll, which forwards to watch with an extra flag. hot starts webpack-dev-server with inline and hot enabled. All six end at the same place, a config path of node_modules/laravel-mix/setup/webpack.config.js, and the development and production variants differ only by a cross-env NODE_ENV value. Reading that list tells you the project is not maintaining a bespoke webpack configuration; it defers to whatever the installed Mix version ships, which is consistent with the version lag above. It also means there is no separate command for building a production bundle of documentation assets on demand, and no test command in the JavaScript half at all. The PHP side has its own harness, with phpunit.xml and a tests directory at the root, so the two halves of the repository are tested very differently.
Four add-on packages and an unfinished port carry the feature story
What LaRecipe itself does is described in one sentence, so the README spends its remaining space on satellites. Each of the four official tools is a separate package documented on the manual site: a dark theme, right to left support, a feedback widget and Swagger support. A badge on MadeWithVueJs points at the Vue dependency the theme layer is built on. Above them sits a note that a .NET version is being worked on, with a link to the larecipe organisation's larecipe-dotnet repository, which is a different runtime and a different repository with its own release cycle. Read as a whole, the README is less a description of a package than a directory of related projects, and a reader who stops there will not know which of those they need. Dark theme and RTL support are the kind of choice a documentation site usually has to make early, and here both are separate installs.
Three releases across a year, with the newest two months apart
The release record is short and recent. v2.8.1 shipped on 2025-07-14, v2.9.0 on 2026-04-03 and v2.9.1 on 2026-06-04, so the last two tags are about two months apart while the gap before them is closer to nine. The repository is not archived and the last push is dated 2026-09-02. Against 2515 stars and 266 forks there are 26 open issues, which is a modest queue for a package with that reach. The root carries the ordinary maintenance files, CHANGELOG.md, CODE_OF_CONDUCT.md, CONTRIBUTING.md and an MIT LICENSE that matches the licence named in the README, plus .gitattributes, stubs/, publishable/, resources/, routes/ and src/ for the package side. No topics are declared on the repository, so nothing in its metadata points a newcomer at the manual site.
Editorial conclusion
Worth it if you want documentation hosted on the same domain and inside the same deploy as the product, and you are on a Laravel version that still tolerates a Vue 2 asset pipeline. Before installing, check that binarytorch/larecipe is the package your project actually wants, since the repository, the add-ons and the funding page all sit under different names, and pin a version rather than tracking the 2.9 line. Read the manual on larecipe.saleem.dev before assuming the README told you what the package does, because it does not.
Frequently asked questions
What does LaRecipe add to a Laravel application?
It is a code-driven package for creating documentation for a product or application directly inside the Laravel app. The documentation is then reached on your own app domain at the /docs endpoint.
How is LaRecipe installed?
Two steps: composer require binarytorch/larecipe, then php artisan larecipe:install. After that you visit your app domain with the /docs endpoint. The package name to require is binarytorch/larecipe, not the repository name.
Does LaRecipe have official themes and extra features?
Four add-on packages are named: LaRecipe Dark Theme, LaRecipe RTL Support, LaRecipe Feedback and LaRecipe Swagger. Each is a separate package documented on the manual site.
Is there a LaRecipe version for .NET?
A .NET version is announced as being in progress, with its own repository at github.com/larecipe/larecipe-dotnet. It is a separate project under a different organisation handle from the PHP one.
What front end stack does the LaRecipe repository build with?
Laravel Mix 2 with webpack-dev-server 3, Vue 2.6, jquery 3.4 and tailwindcss 0.7, with vue2-transitions pinned to an exact 0.2.3. Committed webpack.mix.js, tailwind.js and mix-manifest.json files sit at the root.
Where is the full LaRecipe documentation kept?
On a separate site at larecipe.saleem.dev, which is also the repository homepage. The README itself is short and points there rather than describing the configuration, layout or Markdown options in the repository.
Official sources
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.
[](https://hysenlabs.com/projects/saleem-hadad-larecipe)Star history chart for your README
[](https://hysenlabs.com/projects/saleem-hadad-larecipe)Was this useful?