Weave Code
Dingo Api Custom Laravel Package
saritasa/dingo-api-custom
Saritasa's Dingo API Custom package extends Dingo API for Laravel projects with Saritasa-specific conventions, helping standardize API routing, responses, and integration points while reducing repetitive setup for Dingo-based services.
saritasa/dingo-api-custom is a Laravel package that extends dingo/api with opinionated customizations for building consistent, production-ready REST APIs. It layers additional request handling and response formatting on top of Dingo's routing and versioning, so teams can standardize API behavior without rewriting boilerplate.
- Custom response transformers and error formatting for consistent JSON output
- Extended request validation and exception handling
- Helpers for API versioning and route configuration
- Drop-in integration with existing Dingo-based applications
Frequently asked questions about Dingo Api Custom
- What is saritasa/dingo-api-custom used for?
- It is a thin customization layer over the dingo/api package that layers Saritasa's own adjustments and helpers on top of Dingo's versioned REST API features. It does not provide a standalone capability; it extends and overrides Dingo's routing, response formatting, and authentication behavior. You should only consider it if your Laravel application is already committed to Dingo/API.
- How do I install saritasa/dingo-api-custom with Composer?
- Installation itself is a standard Composer require, but the real effort is dependency resolution. Because dingo/api's release cadence has trailed Laravel majors, run composer why-not against your actual application to confirm the supported Laravel and PHP window before committing. Do not rely on the README alone to prove compatibility.
- Does saritasa/dingo-api-custom support Laravel 10 or Laravel 11?
- There is no published compatibility matrix, and the repository is archived, so no Laravel-major compatibility work is happening. The feasible Laravel and PHP version window is narrow and must be proven with Composer against your own lockfile. If you are on Laravel 10 or 11 with native API Resources and Sanctum, adopting this package is a supportability regression.
- Is saritasa/dingo-api-custom still maintained?
- No. The GitHub repository is archived, which means no security patches, no issue triage, and no new releases. It has roughly one star and zero dependents, so there is no community validation and no bus factor beyond the original author. Treat it as abandoned internal tooling that happened to be published rather than a maintained library.
- Do I need dingo/api installed to use this package?
- Yes. saritasa/dingo-api-custom is a customization layer on top of dingo/api, so it brings in Dingo's routing layer, response factory, transformer contract, and service provider bootstrapping. Adopting this package means adopting Dingo/API's architecture wholesale, so the decision is really about Dingo rather than about this fork.
- What does saritasa/dingo-api-custom change compared to upstream dingo/api?
- The available public information does not include a diff, changelog, or commit history summary, so the exact blast radius is not knowable without auditing the repository yourself. That matters because the fork can silently alter routing, response formatting, and error payloads, which propagates into every API consumer contract you expose.
- Is saritasa/dingo-api-custom safe to use in production?
- For a new service, no. An archived package with no dependents and no patching path means a CVE in Dingo/API or in a transitive HTTP or content-negotiation dependency will not be fixed for you. If the stack is already Dingo-based and the customization is load-bearing, vendoring the code into your own repository is safer than depending on Composer.
- How do I test saritasa/dingo-api-custom before adopting it?
- There is no test suite visibility from the package metadata, so you will need to write your own integration tests around the API contracts it touches. Focus on response formatting, error payloads, and route registration, since those are the areas the fork can change. A Composer why-not check plus a smoke test of your endpoint contracts is the minimum bar.
- What are the alternatives to saritasa/dingo-api-custom?
- Laravel's native stack covers the same ground with first-party support: API Resources for response transformers, Sanctum for authentication, the rate limiter middleware, and route prefixes or groups for versioning. Those primitives avoid the Dingo dependency entirely and are the recommended path for anything with a multi-year horizon.
- What is the exit cost if we adopt saritasa/dingo-api-custom?
- The exit cost depends on how many touchpoints in your codebase reference Dingo-specific contracts such as transformers, the response factory, and route registration. Because this package overrides upstream behavior, you cannot simply bump dingo/api underneath it without re-validating the customizations. Plan for either not adopting it at all or vendoring the fork so you control patching and removal.
Weaver
How can I help you explore Laravel packages today?