- What is smorken/service and what problem does it solve in Laravel?
- smorken/service is a lightweight base service class for Laravel that gives you a dedicated place for business logic outside controllers and Eloquent models. You extend the provided Service class, add your own methods, and resolve it through Laravel's container so controllers stay thin. It is an additive convention rather than a replacement for the container, Eloquent, or the HTTP kernel.
- How do I install smorken/service with Composer?
- Add a repositories entry of type vcs pointing to https://bitbucket.org/scott_morken/laravel-service-package.git, then require smorken/service. Because there is no evidence of published semver tags, pin the dependency to a specific commit SHA instead of dev-master. Private Bitbucket access requires credentials such as an app password or SSH deploy key in CI.
- Does smorken/service support Laravel 10, 11, and 12?
- The available information does not confirm exact illuminate/* constraints, so Laravel 10, 11, and 12 support must be verified in the package's composer.json before adoption. The package appears aimed at modern Laravel 8-11 with PHP 8.x, but that is an assumption rather than a documented guarantee. An unpinned or narrow constraint can block framework upgrades, and with zero dependents upstream fixes are unlikely on a predictable timeline.
- Is smorken/service available on Packagist, and does it have versioned releases?
- There is no evidence of Packagist or GitHub distribution; the repository is hosted on Bitbucket. No published semver tags are confirmed, so Composer will likely resolve dev-master or a pinned commit hash. Use an explicit VCS repository entry and avoid moving branch references for reproducible builds.
- What license does smorken/service use, and can I use it commercially?
- No license file has been confirmed, which is a legal blocker for redistribution or commercial use until verified. Check the repository for a LICENSE file and confirm that the repository owner is the copyright holder. If you fork it internally, retain any license header and get legal sign-off before shipping it.
- How does smorken/service compare to action classes or repositories in Laravel?
- It provides a base Service class convention, while action classes and repositories are alternative patterns for organizing business logic. If your team already standardizes on App\Actions or repositories, this package adds a parallel convention rather than filling a gap. Its main architectural cost is single-inheritance coupling to a third-party base class for what is likely a small amount of glue code.
- Should I use smorken/service in production?
- Treat it as high risk: it has zero stars, zero dependents, a single maintainer, no visible CI, no release cadence, and unconfirmed licensing. The safer path is fork-and-vendor: copy the source into an internal package or App\Support namespace that you own outright. If you proceed, adopt it incrementally in one new bounded context and measure whether it actually reduces boilerplate.
- How do I test service classes built with smorken/service?
- Because the package is a thin base class, you can usually instantiate your extended service directly in unit tests or resolve it from Laravel's container in feature tests. Inject dependencies through the constructor so they can be mocked or swapped in tests. There is no visible test suite or CI in the repository, so you must write and maintain your own coverage.
- How do I avoid namespace collisions between smorken/service and App\Services?
- Check whether the package registers a ServiceProvider or facade and what class names or aliases it exposes, since a Service alias can collide with an internal App\Services convention. The recommended approach is to fork the code into an internal namespace such as Internal\LaravelService or App\Support\Service. Keep a thin wrapper so the underlying implementation can be replaced without touching consumer code.
- What are the alternatives to smorken/service for a Laravel service layer?
- You can use plain constructor injection and app()->make() with no base class, or standardize on action classes, repositories, or domain services under App\Services. You can also copy the package's small amount of glue logic into an internal base class in about a day. Any of these avoids the Bitbucket dependency, unconfirmed license, and single-maintainer risk.