- What is tabuna/stone used for in a Laravel application?
- tabuna/stone is a lightweight Laravel package that provides a small, expressive foundation for building structured application features. It focuses on composable building blocks that keep reusable logic organized without adding unnecessary abstraction. It is aimed at developers who want Laravel-native conventions and a readable API rather than a heavy framework layer.
- How do I install tabuna/stone with Composer?
- Install it with composer require tabuna/stone, which is the standard path for any Laravel package. Laravel package auto-discovery will typically register the service provider, but confirm that in the repository README and the package composer.json before assuming it. Installing into a disposable skeleton application first is the safest way to validate the documented quickstart end to end.
- Which Laravel and PHP versions does tabuna/stone support?
- The supported Laravel and PHP matrix is not documented in the information currently available, so check the illuminate/support and illuminate/contracts constraints in composer.json and the README. A narrow illuminate/* constraint effectively becomes a ceiling on your own framework upgrade path. If the package caps Laravel below the major version you run, treat it as disqualified regardless of feature value.
- Is tabuna/stone production-ready?
- The current release is 0.0.1 with an empty changelog, which under semver conventions is a pre-stability first public release where breaking changes can arrive in any 0.0.x bump. That is acceptable for a spike or internal tool, but for anything customer-facing you should pin an exact version and keep the package behind an application-owned interface. Confirm license, security disclosure process, and CI status before shipping.
- Does tabuna/stone publish migrations, models, or a database connection?
- This is not confirmed by the available material and needs to be verified from the README and the service provider source. The answer materially changes the risk profile: a config-and-facade wrapper is easy to remove, whereas a package that ships migrations and Eloquent models inserts itself into your data layer. If it does own schema, decide explicitly who owns those tables and how they get migrated.
- Is the tabuna/stone service provider auto-discovered?
- Most Laravel packages declare their provider under extra.laravel.providers in composer.json so auto-discovery handles registration. Verify that entry in tabuna/stone, and check whether the provider registers middleware, routes, commands, or scheduled tasks at boot. Anything registered at boot should be noted in your integration plan so you know exactly what the package touches.
- How should I evaluate tabuna/stone before adopting it?
- Treat it as a half-day spike: install into a throwaway Laravel skeleton, run the documented quickstart, and record the actual commands involved. Wrap the package behind a thin application-owned interface such as an adapter or repository binding so its classes never appear directly in domain code. That containment makes removal or replacement cheap if the package stalls.
- How does tabuna/stone compare with other Laravel packages for structuring application logic?
- The available information does not include head-to-head comparisons, so evaluate it on its stated traits: lightweight footprint, minimal dependencies, Laravel-native integration, and an extensible but simple API. Compare candidates on dependency constraints, test coverage, changelog quality, and maintainer activity rather than on feature lists. For small packages, the constraint on illuminate/* and the release discipline usually matter more than the API surface.
- Who maintains tabuna/stone and what is the bus factor risk?
- tabuna/stone comes from the Tabuna ecosystem and appears to be a single-maintainer project at the 0.0.x stage, where abandonment probability is meaningfully higher than for mature packages. Before adoption, check the license, security policy, maintainer count, and issue-tracker responsiveness. Budget for the fork-or-remove cost now rather than discovering it during a framework upgrade.
- How do I upgrade tabuna/stone safely as it moves toward 1.0.0?
- There is no documented breaking-change or deprecation policy yet, and the release notes are empty, so pin an exact version in composer.json instead of using a caret constraint. Read the diff between releases and the in-repo CHANGELOG.md if one exists, and run your test suite against the new tag before merging. Keeping the package behind an adapter means an upgrade that breaks can be reverted without touching domain code.