Weave Code
Laravel Repositories Laravel Package
saritasa/laravel-repositories
Saritasa's Laravel Repositories package provides a structured repository layer for Eloquent models, including base repository classes, reusable query criteria, and helper abstractions that keep controllers and models lean while centralizing data access, filtering, and persistence logic.
saritasa/laravel-repositories adds a clean repository layer between your Laravel application and its data sources. It ships base repository classes and contracts that keep Eloquent queries out of controllers and services, making code easier to test, swap, and maintain.
- Ready-to-extend base repository with common CRUD and query helpers
- Interfaces for dependency injection and easy mocking in tests
- Composable criteria/filters for reusable query logic
- Laravel auto-discovery and simple configuration
- Cache-friendly, framework-agnostic design
Frequently asked questions about Laravel Repositories
- How do I install saritasa/laravel-repositories in a Laravel application?
- Install it with Composer using composer require saritasa/laravel-repositories, then confirm whether the package registers a service provider or bindings automatically or whether you must add them manually. Because the repository is archived, read the source and composer.json first to confirm the package's Laravel and PHP constraints match your application. Run the command in a branch or throwaway project so you can inspect what lands in your lock file before committing.
- Which Laravel and PHP versions does this package support?
- There is no published compatibility matrix or roadmap, so the only reliable source is the require section of the package's composer.json. Check the Laravel framework and PHP version constraints there against your application's own constraints before installing. Since the project is archived, no future Laravel or PHP releases will be added to those constraints by the maintainer.
- Is saritasa/laravel-repositories maintained, and is it safe to use in production?
- The repository is archived, so there are no bug fixes, security patches, or Laravel and PHP compatibility updates coming from upstream. It also has very low adoption (roughly 2 stars and no dependents), which means no community validation or reference implementations to lean on. It can still be used, but treat maintenance as your team's responsibility and pin the exact version. For production, the safer route is to replicate the minimal base repository and criteria classes you need internally.
- What classes and interfaces does saritasa/laravel-repositories actually expose?
- The package provides repository pattern building blocks on top of Eloquent: base repository classes, repository contracts, and reusable query criteria. The exact API surface is small and should be confirmed by reading the src directory and the package's tests, since there is no maintained documentation site or changelog. Identify which classes you would extend or implement, and how tightly they couple to Eloquent internals, before designing around them.
- How do query criteria work in this repository package?
- Criteria are reusable query fragments you apply to a repository so complex filtering, sorting, or eager loading logic lives outside your controllers and models. The package ships base classes for composing these criteria with Eloquent queries, but the precise contract depends on the version you install. Review the criteria base class and any bundled examples, then write a small test around one criterion to confirm the behavior you expect.
- Does the package handle transactions, pagination, caching, or eager loading?
- Repository layers typically pass these concerns through to Eloquent rather than reimplementing them, so pagination and eager loading usually work the way your query builder calls do. Transactions and caching are rarely handled automatically by a base repository and are normally your application's responsibility. Verify each behavior by inspecting the base repository methods and writing a focused integration test before relying on it.
- How should I test repositories built with saritasa/laravel-repositories?
- Test repositories through their contracts so the tests describe behavior rather than the package's internals, using an in-memory SQLite database or a test database with RefreshDatabase. Add regression tests around the criteria and base repository methods you actually use, which also protects you if you later fork or replace the package. Because upstream is archived, your own test suite becomes the de facto compatibility check for future Laravel upgrades.
- Will saritasa/laravel-repositories work with Laravel 11 or 12?
- That depends entirely on the framework constraints in its composer.json, and an archived package will not have been updated for newer releases. Run a short compatibility spike on the Laravel version you target, exercising the base repository and criteria classes you plan to use. If the constraint blocks installation, you can fork the package and widen it, but you then own that maintenance permanently.
- Should I use this package or just write my own base repository classes?
- For most teams, a couple of internal base repository and criteria classes deliver the same benefit with far lower ownership risk than an archived third-party dependency. Eloquent is already a persistence abstraction, so a repository layer only pays off when it isolates domain logic or centralizes genuinely complex query logic. Use this package as a pattern reference, or as a short-lived scaffold you replace with in-house code.
- Can I fork or vendor saritasa/laravel-repositories into a private repository?
- The package is MIT licensed, which generally permits forking, vendoring, and modification as long as the license notice is preserved. If you fork, pin the original commit, keep the license file, add your own tests, and publish it under a private Composer repository so your CI controls the version. That approach converts an abandoned dependency into code your team explicitly owns and can upgrade on your own schedule.
Weaver
How can I help you explore Laravel packages today?