Mentions Laravel Package

Product Decisions This Supports

• Community/engagement roadmap: flarum/mentions is the extension that powers @username mentions and "reply to post" quoting inside a Flarum forum. It is the mechanism behind the re-engagement loop (mention → notification → return visit), so any roadmap item framed as "drive repeat participation," "reduce time-to-first-reply," or "improve discussion discoverability" depends on this behavior being on.
• Build vs. buy (clearly: don't build): mention parsing, username resolution, permission checks, post-quote formatting, and notification fan-out are deceptively fiddly (edge cases in display names, deleted users, private-tag visibility). This is a maintained, MIT-licensed, first-party extension — the correct call is to adopt rather than spec a custom implementation.
• Forum platform selection: because mentions ships as part of the standard Flarum bundle, it is a checkmark item in a Flarum-vs-Discourse-vs-NodeBB evaluation, not a standalone dependency decision. It should be scored as "table stakes included," not as a differentiator.
• Use-case fit: support communities (agents replying to specific customer posts), internal Q&A/knowledge bases (routing a question to a subject-matter expert), and creator/fan communities (directed replies). It is poorly suited to broadcast-style announcement channels where targeted pinging creates noise.
• Moderation and notification policy decisions: enabling mentions forces downstream product choices — can members mute mentions? Are mentions allowed in restricted tags? Does an @mention of a user without read access leak existence? These are policy decisions the PM owns, not the package.

Caveat on the framing: this is a PHP package, but not a Laravel package. Flarum is a standalone PHP forum application (it borrows some Illuminate components, but there is no service provider, no config/app.php registration, no drop-in Composer install into a Laravel app). Any roadmap item that assumes "add mentions to our Laravel product" is mis-scoped and should be re-triaged.

Caveat on the metrics: 18 stars and 0 dependents understate the package badly. It is consumed as part of the Flarum core distribution rather than installed directly, so star count and dependent count are near-meaningless as adoption proxies here. Treat the "opportunity: 48.31" score as a signal of low standalone discoverability, not low value. The 2026-10-18 last-release date is also an anomaly worth verifying with the maintainers before quoting it in any planning document.

When to Consider This Package

Adopt when:

• You are running, or have committed to, Flarum as your community platform. In that case this is effectively free — enable the bundled extension, confirm notification defaults, and move on.
• You need @mentions plus reply-to-a-specific-post threading with per-user notification preferences, out of the box, under a permissive MIT license and a self-hosted deployment model.
• Your team is PHP-comfortable and wants to avoid owning a bespoke notification/reference-graph subsystem.
• You need an extension point: Flarum extensions can hook mention formatting and notification behavior, so light customization (custom mention rendering, additional notification channels) is feasible without a fork.

Look elsewhere when:

• You are building on Laravel and assumed "PHP" meant "Laravel." There is no integration path. For a Laravel app you would either hand-roll mention parsing (a library plus your own notification layer) or pick a product with an API/SDK and integrate at the HTTP boundary.
• You need real-time or rich notification semantics — websocket delivery, @here/@channel-style broadcast mentions, escalation rules, on-call paging, or cross-posting mentions into Slack/Teams. Flarum mentions is forum-scoped and deliberately simple.
• You require enterprise controls: mention auditing, rate-limiting abusive mention patterns, or admin-configurable mention policy per group. Expect to build or find a separate extension.
• Your risk model cannot tolerate single-maintainer, small-ecosystem dependencies. Mitigation here is that your real dependency is Flarum itself — so evaluate Flarum's governance and release cadence, not this package's 18 stars.
• You need a stable, independently versioned API contract to build against. This package versions with the Flarum release train; pin to Flarum, not to mentions.

How to Pitch It (Stakeholders)

For executives (one paragraph): Mentions is a free, MIT-licensed feature that already ships inside our Flarum community platform. It lets members address a specific person or reply to a specific post, and it automatically notifies the recipient — the single most reliable mechanic we have for turning a lurker into a participant and for getting questions answered faster. There is no purchase, no vendor contract, and no incremental infrastructure cost. The recommended action is to enable and configure it, set a clear notification and moderation policy, and measure reply latency and repeat-visit rate against a pre-launch baseline. The main thing to be careful about is scope: this is a Flarum feature, not a component we can lift into our Laravel product — if that is what a stakeholder is imagining, we should correct it now, before it reaches a roadmap.

For engineering (the honest version): This is a bundled Flarum extension, enabled by default — so integration effort is configuration and QA, not development. It handles username parsing, post-quote rendering, permission-aware visibility, and notification dispatch, all of which we would otherwise build and maintain. Our real dependency is Flarum's release train: we pin to Flarum and inherit mentions with it, so upgrade risk is Flarum upgrade risk, not package risk. Two things to verify before we commit: the repository shows zero direct dependents and an anomalous last-release date, which likely reflects bundled consumption and metadata drift rather than abandonment — confirm with the maintainers. And note the ecosystem mismatch: no Laravel service provider, no drop-in Composer install for our application code. If we need mentions outside Flarum, that is a separate integration through the API and should be estimated as such. Customization is available through Flarum's extension hooks rather than a fork, which keeps us on the supported upgrade path.