Weave Code
Rss Bundle Laravel Package
rockbee/rss-bundle
Rockbee RSS Bundle is a PHP/Symfony package for reading, parsing, and rendering RSS and Atom feeds. It simplifies fetching feed items, normalizing content, and exposing feeds to templates or APIs with minimal configuration.
Enables integration of the RSS-PHP library into symfony2 projects.
Frequently asked questions about Rss Bundle
- Can I use rockbee/rss-bundle in a Laravel application?
- No. rockbee/rss-bundle is a Symfony2 bundle, not a Laravel package. It ships no service provider, no facade, no publishable config, and no Package Auto-Discovery, so Composer will install the code but the Laravel kernel will never boot it. Dropping it into a Laravel app accomplishes nothing beyond adding dead weight to vendor/.
- How do I install rockbee/rss-bundle?
- You install it with Composer and then register the bundle in a Symfony2 application's AppKernel, which is where the bundle actually takes effect. There is no artisan command, no vendor:publish step, and no Laravel registration hook. If you are not running Symfony2, installation gives you an inert dependency.
- How is rockbee/rss-bundle configured?
- Configuration happens through the Symfony dependency injection container and the bundle's semantic config tree in config.yml. Laravel developers expect a publishable config file such as config/feeds.php plus environment-driven overrides, and none of that exists here. In a Laravel codebase you would have to write your own config file and service provider from scratch anyway.
- Does rockbee/rss-bundle support Laravel 10, 11, or 12?
- No. The package targets Symfony2, which reached end of life in November 2018, and it declares no support for any Laravel version. The Symfony2 era implies PHP 5.x to 7.x constraints and pre-PSR-11 conventions that modern Laravel does not accommodate. There is no release branch or tag that changes this.
- Will rockbee/rss-bundle run on PHP 8?
- Probably not cleanly. The Symfony2 generation of code predates typed signatures and modern PSR-4 and PSR-11 conventions, so installing it on PHP 8.x invites SimpleXML deprecation noise at best and hard incompatibilities at worst. The underlying rss-php library may fare better, but you would need to check its tags against your PHP version independently of the bundle.
- How do I test feed parsing if I adopt rockbee/rss-bundle?
- There is no practical testing story, because there is no facade to fake and no documented injection points for the fetcher. In Laravel you would normally bind a FeedReader interface in the container and swap in a fake, using Http::fake() to avoid live network calls. That pattern requires your own wrapper, which is exactly the integration route the bundle does not provide.
- Is it safe to parse untrusted RSS feeds with an unmaintained parser?
- Treat it as a real risk. Feed parsing is an untrusted-input surface where XXE, entity expansion, and SSRF via attacker-supplied feed URLs are all realistic concerns, and there is no evidence of a security response process for this package. If you parse feeds at all, disable external entity loading, restrict allowed schemes and hosts, and enforce timeouts on fetching.
- What are the alternatives to rockbee/rss-bundle for RSS and Atom feeds?
- For framework-agnostic parsing, use the upstream rss-php library directly or a maintained option such as laminas/laminas-feed. For the Laravel-native path, spatie/laravel-feed covers publishing a feed of your content and willvincent/feeds wraps reading in a Laravel-friendly way. All of these are actively maintained and fit Laravel without a Symfony shim.
- Is rockbee/rss-bundle actively maintained?
- There is no meaningful maintenance signal. It has zero stars, zero dependents, and a composite score of 0.03, and zero dependents means there are no downstream patches or issue reports to learn from. Combined with the Symfony2 end-of-life date, you should assume the package is effectively abandoned.
- How do I read RSS or Atom feeds in Laravel without a Symfony bundle?
- Composer require the framework-agnostic rss-php library, then wrap it in your own small service provider. Define narrow FeedReader and FeedWriter interfaces in your domain layer, bind implementations in the container, and read settings from config/feeds.php. This is roughly half a day of work and gives you full control over HTTP handling, caching, and error behaviour instead of inheriting an unmaintained bundle.
Weaver
How can I help you explore Laravel packages today?