- What is lde/api-helper used for in Laravel?
- lde/api-helper is a Laravel package that provides convenience utilities for consuming APIs, including standardized responses, resource helpers, and exception handling. It is intended to reduce boilerplate and keep controllers clean. The evaluation describes it as a thin convenience layer above the HTTP transport and below domain services, with XML-to-array or object handling as its main differentiator.
- How do I install lde/api-helper in Laravel?
- Install it with Composer using composer require lde/api-helper. As a Laravel package it should register through service-provider auto-discovery, though you should confirm that against your target Laravel version. The last release is from 2022, so run the install as a proof of concept before committing.
- Does lde/api-helper support Laravel 10 and Laravel 11?
- Laravel 10 and Laravel 11 support is not verified in the provided evaluation. The last release is dated 2022-03-04, placing it in the Laravel 8/9 era, and PHP 8.2/8.3 compatibility is also unconfirmed. Test Composer resolution and package behavior on your exact Laravel and PHP versions before adoption.
- Is lde/api-helper safe for parsing XML responses?
- XML parsing is a historically dangerous area, with XXE, entity expansion, and unsafe deserialization as standard failure modes. The evaluation says whether the package disables external entity loading and enforces parser limits is the most important code-review question. Do not assume safe defaults; review the XML handling code before using it with untrusted feeds.
- Does lde/api-helper use Guzzle or Laravel's Http facade?
- The provided evaluation does not confirm whether lde/api-helper uses Guzzle directly or Laravel's Http facade. Inspect composer.json and the source before adoption, because Laravel's Http facade is preferable when you want to inherit middleware, logging, and fakes. Direct Guzzle use means you must verify TLS, redirect, and SSRF-related behavior yourself.
- Is lde/api-helper still maintained?
- The evaluation reports no release since 2022-03-04, only 5 stars, 0 dependents, and single-organization provenance. There is no evidence of an active maintainer, issue-triage history, or downstream community to absorb maintenance. Treat it as an unmaintained dependency and budget for forking if you adopt it.
- Does lde/api-helper handle retries, caching, and non-2xx responses?
- lde/api-helper does not provide retry policies, circuit breaking, credential rotation, or observability; those remain your responsibility. The evaluation also does not confirm whether it caches, retries, or normalizes non-2xx responses. Inspect the source and assume raw responses may pass through until verified.
- Does lde/api-helper have a test suite and CI?
- The evaluation flags test suite and CI status as unresolved questions, and no test suite or CI status is confirmed in the provided context. Before adoption, inspect the repository for tests and CI configuration and run them against your target Laravel version. An absence of tests increases upgrade and XML security risk.
- What are the production risks of adopting lde/api-helper?
- The main risks are abandonment, security exposure from XML parsing and outbound HTTP, upgrade drag at every Laravel major, and effectively zero field testing from adoption metrics. The package is a helper, not a resilience framework, so retries, circuit breaking, and observability stay with your team. Run a proof-of-concept install and a focused code review before production use.
- What alternatives to lde/api-helper should I consider?
- The direct alternative is a hand-rolled service class in app/Services/Integrations using Laravel's Http facade, which keeps control over retries, logging, XML limits, and upgrades. If XML normalization is the only feature you need, a small internal helper may be safer than taking on an unmaintained dependency. Use lde/api-helper only if its convenience layer justifies the fork-maintenance risk.