Weave Code
Feed Bundle Laravel Package
nekland/feed-bundle
Symfony bundle for generating and serving RSS/Atom syndication feeds. It helps expose blog posts, news, or other dynamic content as feeds with simple integration into Symfony applications and templates.
Deprecated in favor of https://github.com/eko/FeedBundle
Frequently asked questions about Feed Bundle
- What is nekland/feed-bundle?
- nekland/feed-bundle is a Symfony bundle for generating and serving RSS and Atom syndication feeds. It is thin glue: a Symfony DI extension plus configuration that wires up the underlying nekland/feed-manager library, which does the actual feed reading and writing. The package is deprecated in favor of eko/FeedBundle and contributes almost no business logic of its own. For Laravel applications, the bundle layer is dead weight; only the underlying library is a candidate for adoption.
- Can I use nekland/feed-bundle in a Laravel application?
- No, not in any idiomatic way. It is a Symfony bundle, confirmed by the Bundle naming, the DI-extension pattern, and the repository description. In Laravel you would either pull nekland/feed-manager alone and wrap it in a service provider, or skip it entirely in favor of a Laravel-native option such as spatie/laravel-feed. The bundle layer itself provides no value outside Symfony.
- How do I install nekland/feed-bundle?
- Installation is via Composer, followed by registering the bundle in your Symfony kernel and supplying configuration for your feeds. Because the package is deprecated and old, verify that its PHP and Symfony version constraints resolve against your current framework before committing. A short discovery spike in an isolated branch is the safest way to confirm installation and generate a sample RSS and Atom feed. If you are on Laravel, installation is not recommended at all.
- Which Symfony and PHP versions does nekland/feed-bundle support?
- The exact constraints must be verified from the package's composer.json rather than assumed, because the project is old and has no recent releases. Expect version constraints that may block modern Symfony and PHP upgrades. Run a dependency resolution test against your current framework version before adopting it. If constraints conflict, use the framework-agnostic library or a native alternative instead.
- Is nekland/feed-bundle still maintained?
- No. The package is deprecated in favor of eko/FeedBundle and shows the classic signals of a single-maintainer, low-adoption project: around 31 stars and zero dependents. Expect stale dependencies, no recent releases, and version constraints that can block upgrades. If you must keep it, commit it to a private fork or path/VCS repository so you control patches.
- What are the best alternatives to nekland/feed-bundle for Laravel?
- For Laravel, spatie/laravel-feed is the native, actively maintained option with route and controller integration. laminas/laminas-feed is a mature, framework-agnostic alternative if you want to own the integration. You can also depend directly on nekland/feed-manager and write a small adapter of roughly 100 to 200 lines, which preserves feed generation while removing the abandoned bundle dependency. The bundle layer itself is not a good fit for Laravel.
- Does nekland/feed-bundle protect against XXE attacks when parsing XML feeds?
- This must be verified rather than assumed. XML feed parsing should disable external entity loading, for example with libxml_disable_entity_loader or the LIBXML_NONET flag, to avoid XXE vulnerabilities. Inspect the underlying nekland/feed-manager library's defaults and test a malicious feed in an isolated environment. If the defaults are unsafe, patch or wrap the parser before using it in production.
- Can I use nekland/feed-manager without the Symfony bundle?
- Yes. The bundle is only Symfony DI glue; the reusable asset is the underlying nekland/feed-manager library that actually reads and writes RSS and Atom. In Laravel you can depend on that library directly and wrap it in a service provider or a small FeedGenerator/FeedParser adapter. This framework-agnostic extraction is the most portable option and keeps the vendor choice reversible.
- Is nekland/feed-bundle safe to use in production?
- The scope risk is low because feed generation is a bounded problem with a blast radius limited to feed endpoints, not core application flows. However, maintenance risk is high due to deprecation and low adoption, and supply-chain risk is medium because the transitive dependency chain is abandoned. Before committing, run composer audit, verify constraint resolution, and confirm XXE hardening in the parser. If you proceed, fork or vendor the package so upstream disappearance cannot break you.
- What license does nekland/feed-bundle use?
- The package is MIT licensed, which is permissive and a low concern for most teams. You should still confirm the license in the repository and retain the required copyright and attribution notices. If you vendor or fork the code, keep the license file intact. MIT imposes no copyleft obligation on your application.
Weaver
How can I help you explore Laravel packages today?