Beskedfordeler Symfony Laravel Package

Product Decisions This Supports

• Feature scoping for Danish public-sector integrations. beskedfordeler-symfony is a Symfony bundle for Denmark's Beskedfordeleren (the national message-distribution component used by municipalities, regions and agencies). It matters only if your roadmap includes Danish public-sector customers or obligations around Digital Post–adjacent message delivery. If that's not on the roadmap, this package carries zero product value.
• Build vs. borrow vs. buy. With 0 stars, 0 dependents and no release since March 2023, this is not a "buy" decision — it's a reference implementation. The real decision is: fork and own it, lift the domain logic into our own codebase, or implement from the official spec. The package shortens the estimate for the third option.
• Stack alignment / architecture bet. The package is Symfony, not Laravel. That forces an explicit decision: adopt a Symfony component in a Laravel product (service provider wrapper, config translation), or reimplement the message envelope/transport layer behind our own interface. Either way, this is a decision to record, not to stumble into.
• Support-cost modeling. Near-zero adoption means no community safety net, no issue triage, no security patch stream. Any business case built on this dependency must include an internal owner for certificate handling, API-version drift and monitoring — a real line item, not an afterthought.
• Use cases it enables: routing case-management notifications to citizens/businesses via the Danish message distributor; audit/logging requirements in public-sector integration contracts; a protocol-shape reference for teams writing their own client.
• Risk flag on the message path. Public-sector messaging is a compliance-sensitive path. Unmaintained third-party code in that path is a policy question, not just a technical one — surface it early to security/compliance rather than at review time.

When to Consider This Package

Consider it when:

• You are building for a Danish kommune/region/styrelse and must integrate with Beskedfordeleren.
• Your stack is Symfony (PHP 8 era) — the bundle's natural home — or you only need the message DTO/envelope logic, which is typically small enough to lift.
• You need a working reference for the protocol faster than digesting the official Serviceplatformen documentation, and you have PHP engineers who can audit a single small library.
• You are prepared to fork, pin the commit, add CI and integration tests against a mock endpoint, and assign an owner.

Look elsewhere / decline when:

• Your product is Laravel and you expect drop-in integration. Container, bundle config and lifecycle semantics differ; the effort is closer to a port than an install.
• You require vendor SLA, security guarantees, or a responsive maintainer — last release March 2023, zero dependents, effectively single-maintainer.
• Your compliance posture prohibits unmaintained code in the message path (likely true here).
• You operate outside Denmark or don't touch the fælleskomponenter — no relevance.
• A maintained alternative exists (official Kombit/Serviceplatformen SDKs or a direct client) — prefer it.

How to Pitch It (Stakeholders)

To executives: This is a small open-source Symfony bundle for connecting to Denmark's national message distributor. It is effectively an unmaintained reference implementation — zero adoption, no release in roughly two years. I do not recommend adopting it as a dependency on our critical message path. I do recommend a short engineering spike (1–2 days) to read it, because it materially de-risks our estimate for the Danish public-sector integration: it shows the message envelope, transport and certificate handling that the official spec takes considerably longer to absorb. The recommendation is borrow the knowledge, not the dependency — then either fork-and-own with tests, monitoring and a named maintainer, or reimplement the domain layer in-house.

To engineering: Symfony bundle, PHP, last tagged March 2023, no ecosystem traction. Read the source and extract the DTOs and transport logic. If we keep it: fork under our org, pin the commit, add CI plus integration tests against a mocked Beskedfordeler endpoint, and assign an owner for certificate and API-version upkeep. If our product is Laravel, do not attempt to install it — port the logic behind an interface instead.