- Is fkr/simplepie-bundle compatible with Laravel?
- No. It is a Symfony2 bundle, not a Laravel package. It relies on Symfony's kernel and DI extension system, which Laravel does not provide. You cannot register it in a Laravel app as-is.
- Can I install fkr/simplepie-bundle via Composer in a Laravel project?
- Composer may download it, but it will be inert. There is no Laravel service provider or bundle registration mechanism. Its Symfony 2.x constraints conflict with modern Laravel's symfony/* v6/v7 components.
- How do I integrate SimplePie RSS parsing in Laravel?
- Do not use this bundle. The practical path is to adopt a framework-agnostic parser such as laminas/laminas-feed and wrap it in a Laravel service provider. Register a singleton binding, add config/feeds.php for cache path and TTL, and inject the parser where needed. This mirrors the bundle's thin DI wrapper without Symfony dependencies.
- What is the Laravel equivalent of fkr/simplepie-bundle?
- There is no direct Laravel equivalent. The bundle is only a small DI wrapper around SimplePie. Reimplement the same idea with a first-party FeedServiceProvider and a maintained parser like laminas/laminas-feed. That gives you the configuration surface (cache path, TTL, autodiscovery flags) without the archived Symfony code.
- Does fkr/simplepie-bundle support Laravel 10 or Laravel 11?
- No. The bundle targets Symfony 2.x, which reached end of life in November 2018. Its Composer constraints and PSR-0-era autoloading do not resolve cleanly against Laravel 10 or 11. Modern Laravel ships Symfony 6/7 components, not the Symfony 2 kernel this bundle expects.
- Is fkr/simplepie-bundle maintained?
- No. The repository is archived, has roughly 11 stars and zero dependents, and its last release was 2022-10-09. There is no active maintainer and no security response channel. Treat it as a reference implementation, not a dependency.
- Is SimplePie safe for parsing untrusted RSS feeds?
- SimplePie is in maintenance-only mode, and feed parsing is a risky surface for untrusted XML. Risks include XXE, SSRF via feed URLs or redirects, entity-expansion memory exhaustion, and unbounded payloads. For internet-facing Laravel apps, prefer an actively maintained parser and add URL allowlisting, size limits, and HTML sanitization for rendered feed content.
- What are alternatives to fkr/simplepie-bundle for Laravel feed parsing?
- Use laminas/laminas-feed, which is actively maintained, PSR-friendly, and framework-agnostic. Wrap it in a Laravel service provider and config file. If you need to render untrusted feed HTML, pair it with a sanitizer such as HTML Purifier. That combination is a safer long-term choice than an archived Symfony2 bundle.
- How do I configure SimplePie cache and TTL in Laravel?
- You would not configure it through this bundle in Laravel. Instead, create config/feeds.php with a cache path and TTL, then bind a configured parser instance in a service provider. If you migrate to laminas-feed, set its HTTP client and cache storage through Laravel's config and filesystem services. This reproduces the bundle's cache directory and cache duration settings without Symfony DI.
- How do I test RSS/Atom feed parsing in a Laravel app?
- Mock the HTTP layer so tests do not hit live feed URLs, and use fixtures for RSS, Atom, and malformed XML cases. Assert that your service provider binding returns a configured parser and that cache TTL behavior is respected. Also test encoding edge cases and namespace handling, since unmaintained parsers fail quietly on malformed feeds.