Sitemap Bundle Laravel Package

Product Decisions This Supports

• Sitemap / SEO discoverability feature scoping. This package exists to solve one narrow problem: emit sitemap.xml from CMS content nodes so search engines can discover URLs without a hand-maintained list. The PM decision it informs is "do we build, buy, or adopt a dependency for sitemap generation?"
• Stack-fit validation (and a red flag to catch early). Despite being surfaced as a "Laravel/PHP package," kunstmaan/sitemap-bundle is a Symfony bundle tightly coupled to the Kunstmaan CMS NodeBundle. For a Laravel roadmap this is a non-starter; the decision it actually supports is rejecting a candidate and documenting why.
• Dependency risk budget. With 10 stars, 0 dependents, and a last release of 2014-04-05, this is effectively abandoned. It informs a "minimum maintenance bar" policy decision: what adoption signals (release cadence, dependents, maintainer responsiveness) we require before taking on a third-party dependency.
• Use cases it would cover if we owned it: editorial sites with frequent page creation, sectioned content sites needing a URL inventory, and locale/URL-variant listing — all of which we can satisfy with a short in-house controller plus a content query.
• Roadmap trade-off. A sitemap generator is a 1–2 day build for a competent team. The real decision is not "which package" but "do we spend a sprint slot on SEO plumbing at all, and does it need lastmod accuracy, sitemap index chunking, and image/video extensions?" — none of which this package credibly delivers today.

When to Consider This Package

Consider only if ALL of the following are true:

• You are running Symfony with the Kunstmaan CMS NodeBundle, and content is already modeled as Nodes.
• You need a sitemap this week and are willing to vendor/fork and own the code permanently.
• You have verified it runs on your PHP/Symfony version (the 2014 release predates Symfony 3+, so expect compatibility work).
• Your requirements are minimal: a flat URL list, no strict lastmod SLAs, no sitemap index, no GSC submission automation.

Look elsewhere (the default answer) if any of these apply:

• You are on Laravel. There is no integration path here. Use spatie/laravel-sitemap, or a route + Eloquent query returning XML — both are maintained and framework-native.
• You need maintained support, security patching, or a support policy. Zero dependents means zero peer review and no downstream bug surface.
• You need modern sitemap features: sitemap index files, accurate lastmod, image/video/news sitemaps, hreflang alternates, caching, or Search Console ping/submission.
• You need scale beyond a few thousand URLs (memory, chunking, generation time).
• Your org has any "no unmaintained dependencies" policy — this fails it outright. The scoring (0.08 overall, opportunity 23.75) reflects that reality.

How to Pitch It (Stakeholders)

To executives: Recommend not adopting. This is a single-purpose Symfony bundle from 2014 with 10 stars and no downstream users — effectively abandoned, and it does not work with our Laravel stack. The business need (search engines discovering our pages) is real and cheap to satisfy: a 1–2 day in-house build or a maintained library. Taking this on would create a permanent maintenance liability for a feature that should be a small, boring utility. Do not allocate budget to integration; allocate a small slice of an existing sprint to the build.

To engineering: Framing check first — this is a Kunstmaan/Symfony CMS bundle, not a Laravel package, so there is no integration to evaluate. Even on the "right" stack, what it does is thin: query CMS nodes, serialize URLs to XML. We can replicate that in-house with better control over lastmod, chunked sitemap indexes, caching, and multi-locale alternates — roughly 150–300 lines against our own content model. The dependency buys us almost nothing and costs us an unmaintained fork we'd have to patch ourselves. Decision: build the small thing, or use a maintained alternative; skip this package.