- What is radicalloop/eodhistoricaldata used for in Laravel?
- It is a thin Laravel/PHP client wrapper for the EOD Historical Data API. It lets Laravel applications fetch end-of-day stock quotes, historical prices, dividends, splits, and related market data for global symbols. It fits read-only dashboards, research, and low-volume ingestion, but it is not a full data platform with storage, scheduling, normalization, or an SLA.
- How do I install and configure radicalloop/eodhistoricaldata?
- Install it with Composer using the radicalloop/eodhistoricaldata package name. The assessment notes Laravel auto-discovery, config publication, API key configuration, and facade or dependency-injection usage as straightforward integration points. After publishing config and setting your EODHD API key, run a short spike against a sandbox key to confirm endpoint coverage and response behavior.
- Which Laravel and PHP versions does this package support?
- The provided assessment does not list specific Laravel or PHP version constraints. It recommends verifying PHP, Laravel, Guzzle, and dependency constraints in composer.json before adoption. Pin versions and confirm compatibility on your target runtime and in CI, not just locally.
- What EOD Historical Data endpoints and asset classes can it fetch?
- The overview describes end-of-day stock quotes, historical prices, dividends, splits, and other market data for global symbols. Exact endpoint and asset-class coverage is not fully specified, so confirm the symbols, exchanges, and endpoints you need in a time-boxed spike. The assessment also flags response typing and pagination as items to verify.
- Does this package support caching and rate-limit handling?
- The assessment does not confirm built-in caching, retries, timeouts, pagination, or 429 handling. It describes the package as a thin client and recommends putting caching, rate limiting, backoff, and response normalization in an adapter. For end-of-day data, cache aggressively and avoid per-user API calls in latency-sensitive paths.
- Is radicalloop/eodhistoricaldata production-ready?
- It is a useful but not production-hardened wrapper, with a maturity score around 2.77/5 and low community adoption. Production use requires an internal adapter, contract tests, secrets management, caching, rate-limit backoff, observability, and a documented fallback. The package has no SLA, and the MIT license covers code, not market data rights.
- How should I test the EOD Historical Data integration?
- The assessment flags unclear test and CI coverage for the package itself, so your team should add contract tests. Use a sandbox API key and mocked responses to verify endpoint coverage, response schema, timeouts, retries, and 429 behavior. Keep tests in CI so vendor API changes or schema drift are caught early.
- What are alternatives to this Laravel EODHD wrapper?
- Consider the official EODHD SDK or a small internal HTTP client, especially for Symfony, plain PHP, or polyglot services. If you keep this package, wrap it behind an internal MarketDataProvider interface and adapter so you can swap in the official SDK or direct HTTP calls later. Avoid spreading the Laravel facade across domain code.
- Who maintains radicalloop/eodhistoricaldata and what if it is abandoned?
- The package has low community adoption and likely single-maintainer risk. Support is community-only for the wrapper, with separate vendor support from EODHD, and there is no package-level SLA. The team should own dependency updates, compatibility testing, monitoring releases and issues, and be prepared to fork or replace the package.
- Can I redistribute market data fetched through this package?
- The MIT license covers the package code, not the EOD Historical Data market data or redistribution rights. You must verify your EODHD plan limits and display or redistribution terms before exposing data to users or downstream systems. Treat licensing as a separate production readiness checkpoint.