saloonphp/saloon: a Guzzle layer that turns API calls into classes
🤠 Build beautiful API integrations and SDKs with Saloon
At a glance
- What is it?
- Saloon moves HTTP requests into reusable connector and request classes for PHP, with caching, OAuth2, pagination and test recording named as built in features. Its README is a page of links, one code sample, and a feature list that argues with itself.
- Who is it for?
- Saloon fits teams that want one shape for every outbound HTTP call, and it does not fit a project that needs to read its dependencies before installing. Two checks are worth doing.
- 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 11 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
- saloonphp/saloon2,454 ★ · +12
| Repository | 2026-09-30 | 2026-11-15 |
|---|---|---|
| saloonphp/saloon | 2.4k | 2.5k |
12 Stars in the last 46 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The default branch is v4, so the major version lives in the branch name
The default branch of this repository is v4, not main. That single choice shapes how the project is versioned in practice: the major number is not only in the tag, it is in the name of the branch you land on when you clone. It also means the usual shorthand for a stable checkout, which is the default branch, points at a moving minor version rather than at a stable major line, because every 4.x release lands on it. The three newest tags are v4.3.0, v4.4.0 and v4.5.0, which is consistent with a project still climbing inside its fourth major version. For a consumer this is a small thing to get wrong and an awkward thing to explain: there is no main branch to pin, and a fork that tracks the default branch tracks the current minor series by definition. The README does not mention the branch layout at all, so this is a fact you get from the repository rather than from the file that introduces the project.
Two of the three newest releases are dated after the last push on record
The dates line up oddly and are worth reading carefully. The last recorded push to the default branch is 2026-09-18T21:39:30Z. The v4.3.0 release carries the same timestamp to the second. Then v4.4.0 is dated 2026-10-02T21:21:01Z and v4.5.0 is dated 2026-10-03T14:00:51Z, both of them later than the last push the repository reports. So the three most recent releases do not sit in one chronological sequence with the branch tip: one of them coincides with it exactly, and the two newer ones sit after it. That pattern follows from how a release is published, since the publish time is not the commit time, but it leaves a reader with a gap: the newest tags are newer than anything the push record accounts for. Nobody should read that as evidence of anything beyond the two fields being recorded at different moments. It does mean the release list, not the push date, is the thing to check when you want to know what is actually out there.
The one code sample hands an API token to a constructor
The README carries a single PHP sample of three lines, and it is the only executable thing in the file.
<?php
$forge = new ForgeConnector('api-token');
$response = $forge->send(new GetServersRequest);
$data = $response->json();The shape it teaches is the package's whole idea: a connector class holds the connection details, a request class holds one call, send returns a response object, and json reads the body. The part worth pausing on is the credential. The token arrives as a positional constructor argument, a bare string in the sample, with no named argument, no environment variable and no config file mentioned anywhere near it. Nothing in the README says where that string is supposed to come from at runtime, whether the connector accepts a second source of credentials, or what happens when it is missing. The class names also imply a servers API without naming a provider, so the sample teaches the pattern rather than a specific integration.
phpstan-baseline.neon sits next to the static analysis config
The root carries phpstan.dist.neon and phpstan-baseline.neon as a pair, which is the standard arrangement for a project that runs static analysis and also carries a list of findings it has decided to live with. A baseline means the analysis run passes while known errors are excluded by name, so the presence of the file tells you the tool is wired in and also that the codebase is not clean under it. The naming is worth noting, since the config uses a dot, dist.neon, while the baseline uses a hyphen. Alongside them sit .php-cs-fixer.dist.php for code style, phpunit.xml for the test suite, .editorconfig for whitespace and .gitattributes, plus art/ for the artwork the credits mention and src/ with tests/ for the code itself. That is a conventional PHP package layout, and it is described nowhere in the README, which instead routes every reader to the documentation site.
Two relative links point out of the repository
The Contributing and Security sections do not link to files in this repository. Both use a relative path that steps up a level first: one to .github/CONTRIBUTING.md above the repository root, and one to .github/SECURITY.md above it as well. On a hosting service those paths resolve outside the project, so a reader following them from the rendered README does not arrive at a contributing guide or a security policy. The files those sections are meant to point at are not in the visible top level listing either, where .github/ appears as a single directory entry with nothing under it. So a project that asks outsiders to contribute and to report vulnerabilities does so through two links that do not resolve. Neither section says what the policy is, and the security section in particular gives a reader no fallback address, no disclosure process and no contact point at all.
The credits link resolves to a different repository path
The Credits section names Sam Carré with a profile link, thanks the contributors through a link, and adds a credit for the logo. The contributors link is the interesting one. It points at a path under Sammyjo20/Saloon rather than at saloonphp/saloon, so the link that is supposed to show the project's contributor graph names a different repository path than the repository itself. Whether that path redirects or resolves to something else is not something the file says, and either way the two do not match on the page. The same section is where the page's own branding lives: the title pairs a lone star metaphor with a phrase that uses the word your twice in one line, which reads as an editing slip rather than a choice. None of this affects the code, and all of it is the kind of detail a prospective contributor meets before deciding whether to open a pull request.
Framework agnostic, Laravel complete, and lightweight, in one list
The Key Features list makes three claims that pull against each other. It calls the package framework agnostic, it claims full Laravel support in the same breath, and it closes by calling the package lightweight with few dependencies while promising request recording, request concurrency, caching, data transfer objects, OAuth2 and pagination. Those are not small features to assemble, and the file gives no dependency count to check the lightness claim against. composer.json is present at the root, so the answer exists, but it is not in the README and not on the documentation site landing page either. Two other things the file does not state: a minimum PHP version, and the license terms. The metadata records MIT and a LICENSE file sits at the root, yet the README has no license section and ends with the credits. For a package you install with Composer, both are the sort of detail you end up checking yourself.
Editorial conclusion
Saloon fits teams that want one shape for every outbound HTTP call, and it does not fit a project that needs to read its dependencies before installing. Two checks are worth doing. Open composer.json, since the README calls the package lightweight with few dependencies while promising caching, OAuth2, pagination and concurrency, and gives no dependency count to check against. And decide how you will pin it, because the default branch is v4 rather than main, and the two newest releases are dated after the last push the repository records, so a branch name alone does not tell you what is published. Installation, provider details and configuration keys are all on docs.saloon.dev; the README contributes a code sample, a feature list and two links that point out of the repository.
Frequently asked questions
What is saloonphp/saloon used for?
It is a PHP library that moves API requests into reusable classes so API configuration lives in one place, aimed at building API integrations and SDKs. The README says it is built on top of Guzzle, is framework agnostic, and includes caching, OAuth2, pagination and request recording.
How do I install saloonphp/saloon?
The README contains no install command. Its Getting Started section is a single link to the installation page on docs.saloon.dev, and the documentation link above it is the only route the file offers.
Does saloonphp/saloon require Laravel or a minimum PHP version?
Neither is stated as a requirement. The feature list calls the package framework agnostic while also claiming full Laravel support, and no minimum PHP version appears anywhere in the README.
Which branch and releases does saloonphp/saloon publish from?
The default branch is v4 rather than main, so the major version is carried in the branch name. The three newest releases are v4.3.0 on 2026-09-18, v4.4.0 on 2026-10-02 and v4.5.0 on 2026-10-03.
What license does saloonphp/saloon use?
MIT, recorded in the repository metadata with a LICENSE file at the root. The README itself has no license section, and the file ends with the credits.
Who is behind saloonphp/saloon?
The credits name Sam Carré, thank the contributors through a link, and credit Caneco for the logo. The contributors link points at the path Sammyjo20/Saloon rather than at the saloonphp/saloon repository itself.
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/saloonphp-saloon)Star history chart for your README
[](https://hysenlabs.com/projects/saloonphp-saloon)Was this useful?