Weave Code
Rss Laravel Package
vinelab/rss
Vinelab RSS is a Laravel package for building and serving RSS feeds from your application. Define channels and items with a fluent API, manage feed metadata, and output valid RSS XML for readers and aggregators.
Simple RSS Client
Frequently asked questions about Rss
- How do I install vinelab/rss in a Laravel application?
- Install it with Composer using composer require vinelab/rss. The package ships a Laravel service provider and facade, and if configuration publishing is available you can publish the vendor config with artisan vendor:publish. After that you can load a feed URL and iterate its items. Verify the package constraints during installation because the last release was in March 2022.
- Which Laravel and PHP versions does vinelab/rss support?
- The package is in the PHP 7.4 to 8.1 and Laravel 8 to 9 band by default based on its March 2022 release. You need to check the current HEAD composer.json and any open issues or pull requests before using it on Laravel 10 or 11 or PHP 8.2 and above. Because the integration surface is small, a compatibility fork is a realistic fallback if upstream has not added modern support.
- Does vinelab/rss fetch RSS feeds over HTTP or only parse XML?
- It is a thin RSS and Atom read client that is typically used by loading a URL and iterating items, but you should verify whether it performs the HTTP call itself or expects a pre-fetched payload. If it fetches internally, confirm that timeout, redirect, user-agent, proxy, and TLS settings are configurable. A safer production pattern is to control HTTP fetching in your own application layer and use the package only as the parser.
- Can vinelab/rss parse both RSS and Atom feeds?
- It is positioned as an RSS client, but exact format coverage must be validated against your sources. Test RSS 0.9x and 2.0, Atom, RDF, CDATA sections, date parsing variance, and non-UTF-8 encodings before relying on it broadly. Thin clients often fail on these edge cases, so fixture-based compatibility tests are essential. If you need broad format coverage, compare maintained parsers such as laminas/laminas-feed or SimplePie.
- Is vinelab/rss safe for parsing untrusted RSS feeds?
- You must confirm that the parser disables external entity loading and DTD expansions to prevent XXE, and that malformed or truncated XML does not cause fatal errors. Safety also depends on transitive dependencies such as Guzzle, SimpleXML usage, and Laravel support staying patched. Review the parser behavior with malicious and broken fixtures, and keep a fork-and-patch path open because upstream activity is limited.
- How does vinelab/rss handle malformed or truncated feed XML?
- The behavior needs to be verified: it may throw an exception, return a partial result, or silently return an empty feed. Test truncated XML, invalid characters, missing required elements, and broken CDATA before using it in an ingestion pipeline. Wrap the parse step in your own adapter so failures are mapped to domain exceptions and do not break background jobs.
- Is vinelab/rss actively maintained?
- The indicators point to maintenance stasis: a March 2022 release, a small star count, and a single-maintainer lineage. There is no guaranteed security patch path if a transitive dependency or Laravel support goes stale. The code footprint is small, so the blast radius of failure is contained, but the safety net is also small. Decide your fork-and-patch appetite before adopting it for production.
- Should I use vinelab/rss or laminas/laminas-feed or SimplePie?
- Choose vinelab/rss if you want a low-ceremony Laravel-native facade, your PHP and Laravel versions fit, and your ingestion needs are simple. Choose a better-maintained or broader parser such as laminas/laminas-feed, simplepie/simplepie, or willvincent/feeds if format coverage and long-term support matter more. In either case, hide the library behind your own FeedReader interface so you can swap adapters later.
- How should I test a Laravel app that uses vinelab/rss?
- Do not hit live feeds in tests. Use fixture XML payloads and mock the HTTP layer if the package performs its own fetching. Bind a fake FeedReader adapter that returns normalized DTOs, and test malformed XML, encoding issues, CDATA, date formats, and empty feeds. Keeping vendor types out of your domain code makes these tests and future migrations much easier.
- What is the best integration pattern for vinelab/rss in production?
- Treat the package as an implementation detail behind a domain-level FeedReader port that returns normalized FeedItem DTOs with guid, title, link, published-at, content, and a raw payload hash. Run feed ingestion as a background job and own scheduling, idempotency, deduplication, normalization, and storage in your application. The package is not a feed store, deduper, or scheduler, so those pipeline concerns remain yours. This boundary also makes replacing or forking the adapter straightforward.
Weaver
How can I help you explore Laravel packages today?