- Can I use kami/icobench-bundle in a Laravel application?
- Not idiomatically. kami/icobench-bundle is a Symfony bundle, and Laravel does not implement Symfony's bundle and DI extension lifecycle. The practical path is to ignore the bundle layer, copy the thin ICO Bench client into your app, and bind it through a Laravel ServiceProvider. That is a small job, but it is a fork-and-wrap effort rather than a normal Composer install.
- Is kami/icobench-bundle still maintained?
- No. The last release was 2018-11-10, with no maintainer activity or security response path since. It has one star and zero dependents, so there is no community to surface breakage or fixes. Treat it as abandoned source material, not a maintained dependency.
- Does the ICO Bench API still work?
- Assume it is dead or degraded until a live spike proves otherwise. ICO Bench ceased public operations around 2020, and the wrapper has no value if the endpoints are unreachable. Run one request against a known historical ICO before any design work. If the API is gone, look for a licensed dataset or alternative rating provider instead.
- How do I install kami/icobench-bundle?
- You can try composer require kami/icobench-bundle, but 2018-era PHP and Symfony constraints will likely conflict with PHP 8.x and modern Symfony components. Expect to need --ignore-platform-reqs hacks or a fork just to install it. For Laravel, do not install it as-is; vendor the client code instead.
- What Laravel versions does this package support?
- None officially. This is a Symfony bundle with no Laravel ServiceProvider, facade, package discovery, or Laravel version constraints. It cannot be consumed idiomatically by any Laravel version without manual integration or a fork. Do not expect Laravel 10 or 11 support.
- How do I configure ICO Bench API credentials in Laravel?
- The bundle manages credentials and endpoints through standard Symfony configuration, not Laravel config. In Laravel you would define your own config entry for the base URL and API key, then bind the extracted client in a provider. Given the upstream API risk, confirm the service is reachable before building configuration around it.
- Is kami/icobench-bundle safe for production?
- Not recommended. The risks are concentrated outside the code: the upstream API is likely dead, the package is abandoned, and it is a single-maintainer dependency with near-zero audience. You also inherit data licensing and provenance questions for ICO ratings. Pinning it in a production composer.json is a poor supply-chain choice.
- What PHP and Symfony versions does kami/icobench-bundle require?
- Check composer.json first. The package dates from 2018, so its PHP and Symfony constraints almost certainly conflict with PHP 8.2+ and current Symfony releases. It may also rely on deprecated Symfony HTTP client abstractions or EOL Guzzle versions. A fork is usually required before installation on a modern stack.
- How should I test an ICO Bench integration in Laravel?
- There are no upstream tests, so you must write your own coverage. Wrap the HTTP transport behind an interface or repository so you can mock responses, and add contract tests against either a live spike or recorded fixtures. If the API is dead, test against archived payloads and treat the client as a parser, not a live integration.
- What are alternatives to kami/icobench-bundle for ICO data in Laravel?
- For a live feature, use a small Guzzle or Saloon client against a surviving data provider, or license an ICO dataset and import it. For a one-time backfill, an archived dump is usually cheaper than any wrapper. If you must reuse this code, vendor the thin client and discard the Symfony bundle scaffolding. Have legal review any third-party ratings used on user-facing pages.