PHPackages tryhackx/flarum-magnet-link - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. tryhackx/flarum-magnet-link ActiveFlarum-extension[Utility & Helpers](/categories/utility) tryhackx/flarum-magnet-link =========================== Secure magnet link integration for Flarum with SHA-256 token protection, SSRF-hardened tracker scraping, live click counters, and an optimized discussion list preview tooltip. 2.9.1(1w ago)2111↓76.7%MITPHPPHP ^8.3 Since Apr 23Pushed 1w ago1 watchersCompare [ Source](https://github.com/TryHackX/flarum-magnet-link)[ Packagist](https://packagist.org/packages/tryhackx/flarum-magnet-link)[ RSS](/packages/tryhackx-flarum-magnet-link/feed)WikiDiscussions main Synced today READMEChangelogDependencies (10)Versions (11)Used By (0) TryHackX Magnet Link ==================== [](#tryhackx-magnet-link) A powerful, secure, and highly customisable Flarum extension for embedding and managing **magnet links**. Token-protected magnet URIs, live tracker scraping (Seeders / Leechers / Completed), per-link click counters with anti-spam protection, custom display names, a discussion-list hover tooltip, and a CLI / one-click admin backfill for posts that were written before the extension was enabled. πŸš€ Versions & Compatibility ------------------------------ [](#-versions--compatibility) This extension is developed in parallel to support both legacy and modern Flarum installations: - **Version 2.x** β€” Fully compatible with the latest Flarum 2.x routing and frontend architecture. **Actively developed.** - **Version 1.x** β€” Supports legacy Flarum 1.8.0 and above. **No longer actively developed** β€” stays available for legacy installs but won't receive new features. > **Latest highlights (2.9.0):** > > - **Hardened scraper engine (now the default)** β€” a cURL engine that pins the resolved tracker IP, closing the DNS-rebinding / SSRF window for HTTP(S) and UDP (strict TLS, IPv6, bounded response, re-validated redirects). A *Classic*`file_get_contents` engine stays as a no-cURL fallback. (2.8.0 / 2.8.1) > - **Separate, configurable scrape time budgets** β€” the discussion-list tooltip and the open-topic card now have independent, admin-set time budgets (default 4 s vs 15 s, hard-capped at 30 s), so the tooltip can reach a live tracker on magnets with many (or dead-first) trackers instead of giving up early. > - **Hover concurrency limit** β€” rapid hovering no longer piles up scrape requests on PHP workers: a client-side limit (default 2) aborts the oldest in-flight request, and leaving / opening a discussion aborts pending ones (`AbortController`). > - **Tooltip-specific tracker tuning** β€” optional per-tooltip tracker timeout and max tracker count (both inherit the global value by default), tuned independently of the topic. > - **Opt-in tracker host allowlist** β€” restrict scraping to a list of trusted hosts, fully closing the SSRF surface for attacker-supplied trackers. (2.6.1) > > **Earlier highlights (2.3.0):** > > - **Restricted-discussion leak fixed** β€” the discussion-list tooltip endpoint now enforces per-discussion / per-post visibility, so members can't enumerate magnet metadata (or, via the token, the URI) from topics they aren't allowed to see. > - **Tokens re-secured** β€” magnet tokens now use a random, per-install secret salt (the previous fallback salt was effectively public), so a token in the page source can no longer be reversed to the magnet URI. After upgrading, run `php flarum magnet:retokenize` or click *Re-secure magnet tokens* once. > - **Priority trackers** β€” optionally list trusted tracker hosts to query first, improving stat quality and latency in the default "first responder" mode. > - **Configurable tracker redirects** β€” follow a few HTTP redirects (e.g. for a tracker behind Cloudflare), with every hop re-validated by the SSRF guard. > - **Lighter discussion list** β€” `hasMagnetLinks` is read from a denormalized column instead of eager-loading first posts, and tooltip custom-name lookups are batched into one query. > > **From 2.2.0:** > > - **SSRF-hardened scraping** β€” tracker hosts come from post content, so the scraper now refuses trackers that resolve to private / loopback / reserved addresses (internal services, cloud metadata), with an admin opt-in for intentional private trackers. Tracker contacts are capped and bounded by a wall-clock budget so a malicious magnet can't tie up a worker. > - **Configurable result cache** β€” seed/leech/download stats are cached (server + browser) with admin controls to set the lifetime or turn it off; the refresh button forces a genuine re-scrape. > - **Rate-limited manual refresh** β€” the refresh button is bounded by a global per-magnet cooldown (one refresh updates the shared result everyone sees) and a per-IP sliding-window quota (guests included), all admin-configurable. > - **Responsive card + display styles** β€” reworked mobile layout (full wrapping name, single-line stats with a fluid font), plus an admin option to use that mobile layout on desktop too, with line-clamp and stats-alignment controls. > - **"Check All" / "Display Type" now actually work** β€” they aggregate seeders/leechers/completed across trackers (average / average-max-downloads / max-all); previously they were inert settings. > - **Click IP from Flarum core** β€” click de-dup / ban tracking now uses the framework's resolved IP instead of spoofable proxy headers. > - **Magnet backfill** β€” re-parse posts whose `[magnet]` BBCode was saved before the extension was active (via `php flarum magnet:reparse` or the admin button). ✨ Features ---------- [](#-features) ### Core functionality [](#core-functionality) - **Secure embedding** β€” raw magnet URIs are never exposed in the HTML source. They're protected by SHA-256 tokens and retrieved via API. Guests can be locked out entirely. - **Text editor integration** β€” adds a magnet icon to the Flarum editor; wraps the current selection or inserts `[magnet][/magnet]` at the cursor. - **Multilingual** β€” English and Polish bundled. ### Real-time statistics (scraper) [](#real-time-statistics-scraper) - **Tracker scraping** for HTTP / HTTPS / UDP trackers, with live **Seeders / Leechers / Completed** counts (powered by the [Scrapeer](https://github.com/medariox/scrapeer) library). - **SSRF protection** β€” tracker hosts are resolved and validated before any request; private / loopback / reserved targets are blocked by default (admin opt-in for intentional private trackers). Contacts are capped and time-budgeted so a single magnet can't exhaust a worker. - **Aggregation modes** β€” with *Check All Trackers* on, results are combined across trackers as average, average-max-downloads, or max-all. - **Two scraper engines** β€” the default *hardened* engine pins the resolved tracker IP (cURL + `CURLOPT_RESOLVE`, strict TLS, dual-stack UDP) to close the DNS-rebinding window; *classic* (`file_get_contents`, no cURL) is kept as a fallback. - **Result caching** β€” stats are cached server-side and in the browser; the lifetime is configurable and caching can be turned off entirely. - **Performance knobs** β€” separate, admin-configurable scrape time budgets for the in-topic card and the list tooltip (hard-capped at 30 s), plus a per-tracker timeout and max tracker count β€” each also overridable just for the tooltip. - **Manual refresh (rate-limited)** β€” per-link refresh button to re-pull fresh stats (bypasses the cache for a genuine re-scrape). Bounded by a global per-magnet cooldown β€” one refresh updates the shared result everyone sees β€” and a per-IP sliding-window quota that covers guests too; both configurable. ### Discussion-list tooltip [](#discussion-list-tooltip) - **Hover tooltip** on the discussion list that previews the topic's magnets and their current stats β€” without opening the topic. - **Smart gating** β€” the tooltip only fires for discussions that actually have a magnet in the opening post (`hasMagnetLinks`attribute), so non-magnet discussions never trigger an API call. - **Tracker error rendering** β€” when no tracker responds (or the magnet has no trackers, no HTTP trackers, etc.) the tooltip shows the localised error message instead of nothing, mirroring the in-post widget. - **Permission message rendering** β€” for guests / unverified / no-permission users you can choose to show "You must be logged in to view magnet links. Login or Register" (toggle in admin, on by default) instead of letting "Loading…" flash and disappear. - **Configurable client cache** β€” the same magnet hovered repeatedly only hits the API once within the cache lifetime (default 5 minutes; adjustable or disable-able from admin, in sync with the server-side cache). - **Bounded hover load** β€” a per-hover scrape time budget plus a client-side concurrency limit (default 2, abort-oldest via `AbortController`) keep rapid hovering from piling up synchronous scrape requests on PHP workers; leaving or opening a discussion aborts pending requests. Optional tooltip-only tracker timeout / max-tracker overrides tune reach vs. cost independently of the topic. ### Backfill for old posts [](#backfill-for-old-posts) For discussions whose `[magnet]…[/magnet]` BBCode was written **before**this extension was enabled, the parsed XML stored in `posts.content`doesn't contain `` tags β€” so neither the in-post button nor the tooltip works. This release ships two ways to fix it: - **CLI:** `php flarum magnet:reparse` β€” batched, idempotent, no HTTP timeout (preferred for large forums). - **Admin button:** *Re-parse old magnet links* in the extension settings β€” calls a small admin-gated endpoint that runs the same re-parser synchronously (handy after a fresh install / content import). Both use the same `MagnetReparser` service, which: - Targets only posts whose XML contains the literal `[magnet]` BBCode but not yet a `` tag. - Goes through them in chunks of 50 (`chunkById`). - Re-parses each post via the content accessor / mutator β€” which unparses the stored XML back to its source and re-parses it with the now-active formatter, producing `` tags. - Is safe to run repeatedly: posts that already have `` are excluded by the query; re-parsing one that's already correct produces identical XML. ### Custom torrent names [](#custom-torrent-names) - Post authors can rename their magnet links from the post UI. - The custom name is stored per magnet Γ— post pair, so the same magnet can appear under different names in different topics. ### Analytics & protection [](#analytics--protection) - **Click counters** β€” live-updating clicks per magnet, shared across all posts that embed the same magnet. - **Anti-spam / IP banning** β€” configurable cooldowns, self-click intervals and temporary IP bans against click spam. ### Access control [](#access-control) - **Group permissions** β€” restrict viewing of magnet links per Flarum user group (`tryhackx-magnet-link.viewMagnetLinks`, default Members). - **Email confirmation gate** β€” optionally require email-verified users. - **Guest gate** β€” show or hide magnet links to unregistered visitors. πŸ” How it works (security) ------------------------- [](#-how-it-works-security) 1. The user inserts `[magnet]magnet:?xt=...[/magnet]` into a post. 2. On post save the magnet URI is validated and stored in `magnet_links` with a SHA-256 token derived from a random, **per-install secret salt**. 3. In the rendered HTML *only* that token is exposed (`data-token`) β€” never the magnet URI, and the secret salt means the token can't be reversed back to it. 4. When the user clicks the link, JavaScript sends the token to `/api/magnet/info/{token}`. 5. The API checks permissions (group, guest, email verification) and returns the magnet URI only to authorised users. 6. The browser opens the magnet link. **Tracker scraping safety:** a magnet's tracker URLs are attacker-controlled, so before contacting any tracker the server resolves its host and refuses private / loopback / link-local / reserved addresses (preventing the scraper from being used to reach internal services β€” SSRF). HTTP redirects are not followed unless you opt in (*Max Tracker Redirects*), and even then every hop is re-validated against the same host policy and only http/https targets are followed. The number of trackers contacted per magnet and the total time spent are both capped, the response size is bounded, and results are cached, so scraping can't be turned into a denial-of-service vector. Click counting uses Flarum's resolved client IP (honouring trusted proxies) rather than spoofable request headers. **Bundled scraper library:** the BitTorrent scraping uses a **hardened in-tree fork**of [Scrapeer](https://github.com/medariox/scrapeer) (under `src/Scraper/`, PSR-4 `Scrapeer\`). It ships **two engines**, selectable in admin: - **Hardened (default)** β€” a cURL-based engine that **pins the resolved IP**: the tracker host is resolved and range-validated once, and the connection is forced to that exact IP (`CURLOPT_RESOLVE` for HTTP(S), a connected socket for UDP), so there is **no second DNS lookup to rebind** between the check and the connection. TLS is strictly verified (peer + host) against the original hostname, the protocol is restricted to HTTP(S), the response size is bounded, and redirects are followed manually β€” each hop re-validated and re-pinned. UDP is dual-stack (IPv6). *Requires the cURL extension.* - **Classic** β€” the original `file_get_contents` engine (no cURL dependency) with a documented residual DNS-rebinding window; kept as a fallback for hosts without cURL. Because the fork is vendored rather than required through Composer, upstream changes are **tracked and ported by hand**, and `composer audit` will not surface them automatically. The `src/Scraper/` subtree keeps its upstream **CC BY-SA 3.0** license (the rest of the extension is MIT) β€” see `src/Scraper/NOTICE.md`. Screenshots ----------- [](#screenshots) [![Mobile view of the discussion list across multiple TryHackX layout combinations](assets/ALL_MOBILE.png)](assets/ALL_MOBILE.png) *Mobile view β€” discussion list rendered with different combinations of TryHackX extensions (thumbnails + ratings + views, thumbnails + views, thumbnails only, ratings only, views only, vanilla Flarum).* [![Magnet Link admin settings β€” backfill, access gates, tracker scraping, click tracking, tooltip and anti-spam controls](assets/Magnet_Link_BBCode.png)](assets/Magnet_Link_BBCode.png) *Magnet Link admin panel β€” magnet backfill button, guest / activated-users gates, tracker scraping toggles (HTTP(S)-only, check-all, display mode, timeout, max trackers), click tracking, discussion-list tooltip with permission-message option, custom torrent names, spam protection (ban duration / interval / threshold, self-click interval) and the `viewMagnetLinks` permission row.* [![Desktop discussion list with the full TryHackX stack β€” thumbnail sliders, star ratings and the magnet button](assets/ALL_VIA_MAGNETS.png)](assets/ALL_VIA_MAGNETS.png) *Desktop discussion list with the full TryHackX stack β€” thumbnail sliders on the left, star ratings on the right, the magnet button rendered next to each topic title.* [![Desktop discussion list β€” magnet tooltip mid-load on a topic](assets/ALL_VIA_MAGNETS_v2.png)](assets/ALL_VIA_MAGNETS_v2.png) *Desktop discussion list β€” hover state showing the magnet tooltip loading inline (the new `hasMagnetLinks` gate keeps it from firing on magnet-less topics).* Support Development ------------------- [](#support-development) If you find this extension useful, consider supporting its development: - **Monero (XMR):** `45hvee4Jv7qeAm6SrBzXb9YVjb8DkHtFtFh7qkDMxS9zYX3NRi1dV27MtSdVC5X8T1YVoiG8XFiJkh4p9UncqWGxHi4tiwk` - **Bitcoin (BTC):** `bc1qncavcek4kknpvykedxas8kxash9kdng990qed2` - **Ethereum (ETH):** `0xa3d38d5Cf202598dd782C611e9F43f342C967cF5` You can also find the donation option in the extension's admin settings panel. πŸ“¦ Installation -------------- [](#-installation) ``` composer require tryhackx/flarum-magnet-link ``` ### Updating [](#updating) ``` composer update tryhackx/flarum-magnet-link php flarum migrate php flarum cache:clear ``` After installing the extension on a forum that already has posts with `[magnet]…[/magnet]` content, run the backfill **once**: ``` php flarum magnet:reparse ``` …or click *Re-parse old magnet links* in the admin settings panel. βš™οΈ Configuration ---------------- [](#️-configuration) Go to **Admin β†’ Extensions β†’ Magnet Link**. SettingDefaultNotesVisible to GuestsOffIf off, guests get a permission message (see below).Activated Users OnlyOffRequire email confirmation.Enable Tracker ScrapingOnOff β†’ only name + click counter shown.**Scraper Engine****Hardened***Hardened* (default) = cURL engine that pins the resolved IP (closes the DNS-rebinding / SSRF window), strict TLS, IPv6 UDP β€” **requires the cURL extension**. *Classic* = the original `file_get_contents` engine (no cURL) with a documented residual rebinding window; pick it only if cURL is unavailable.HTTP(S) Trackers OnlyOffUseful if UDP is blocked on your host.**Allow Private/Internal Trackers****Off**Off blocks trackers resolving to private / loopback / reserved IPs (SSRF protection). Enable only for an intentional tracker on a private network.Check All TrackersOffOn β†’ contact every allowed tracker and aggregate; off β†’ stop at the first responder.Display TypeAverageHow to aggregate across trackers when *Check All* is on (average / average-max-downloads / max-all).Tracker Timeout2 sPer-tracker (clamped to the remaining time budget).Maximum Trackers0Max trackers contacted per magnet. 0 = built-in safety cap (12); a wall-clock budget also applies.**Topic Scrape Time Budget (seconds)****15**Total tracker-scrape time for a magnet shown in the open topic (the in-post card). Clamped to 2–30 s (a hard 30 s ceiling bounds the worker no matter what). Raise it for magnets with many trackers.**Max Tracker Redirects**0HTTP(S) redirects to follow per tracker (0–5). 0 = don't follow. Raise to 1–2 for a tracker behind Cloudflare/CDN that redirects httpβ†’https; every hop is re-validated by the SSRF guard.**Priority Trackers***(empty)*Optional, one tracker host per line. Listed hosts are queried first (in order) when a magnet contains them β€” better stats/latency in the default "first responder" mode. Reorder only; never adds trackers not in the magnet.**Tracker host allowlist (security)***(empty)*Optional, one trusted tracker host per line. When non-empty, **only** these hosts are ever contacted β€” tracker URLs from post content that aren't listed are skipped entirely, closing the SSRF / DNS-rebinding surface for attacker-supplied trackers. Empty = scrape any public host (still behind the SSRF guard).**Cache Tracker Results****On**Cache stats (server + browser) so repeated views / hovers don't re-query trackers. The main brake on hover-driven load.**Cache Lifetime (seconds)****300**How long cached stats stay valid. 0 disables caching.**Refresh Cooldown (seconds)****30**Global per-magnet cooldown for the manual refresh button. One refresh updates the shared result everyone sees; the magnet can't be re-refreshed sooner. 0 = no cooldown. Needs caching on to share the result.**Refresh Limit (per IP)****10**Max manual refreshes a single IP (guests too) may do within the window below. 0 = unlimited.**Refresh Limit Window (seconds)****600**Rolling window for the per-IP refresh limit; used slots free up one by one as they age out.Enable Click TrackingOnShow click counts and feed the ban system.Enable Discussion TooltipOnShow the hover tooltip on the discussion list.Max Magnets in Tooltip3Truncate longer lists.**Tooltip Scrape Time Budget (seconds)****4**Time budget shared across all magnets scraped for one discussion-list hover. Kept short (the scrape holds a worker while you hover); the open topic uses the larger budget above. Clamped to 2–30 s. Raise it if the tooltip often shows "no response".**Max Concurrent Tooltip Requests****2**How many hover-scrape requests may run at once (1–6). Hovering past this aborts the oldest in-flight request; leaving or opening a discussion aborts pending ones. Caps how many workers rapid hovering can tie up.**Tooltip: Max Trackers to Query**0Max trackers the tooltip contacts per magnet. 0 = inherit *Maximum Trackers*. A different value gets its own cache entry, so it never poisons the topic's full result.**Tooltip: Tracker Timeout (seconds)**0Per-tracker timeout for tooltip scrapes. 0 = inherit *Tracker Timeout*. Lower it (e.g. 1) so dead trackers fail faster and more get tried within the budget β€” the most effective way to reach a live tracker when dead trackers are listed first.**Show permission message in tooltip****On**Render "You must be logged in…" in the tooltip when permissions block the request, instead of letting the loading state flash and disappear.Enable Custom Torrent NamesOnAuthors can rename their own magnets.**Desktop card style****Standard***Standard* (single-row) or *Mobile style (also on desktop)* β€” applies the phone layout at all widths. Phones always use the mobile layout.**Max name lines****3**(Mobile layout) Max lines the wrapped torrent name may use before it's clamped with an ellipsis.**Stats alignment****space-between**(Mobile layout) How the seed/leech/download stats spread across their line: `space-between` / `space-around` / `center` / `flex-start`.Enable Spam ProtectionOnTemporarily ban IPs that click too many magnets.Ban Duration / Interval / Threshold20 min / 10 min / 100Tuning for the ban system.Self-Click Interval1 dayHow long before the same IP can re-bump a click.πŸ›  Usage ------- [](#-usage) Wrap a magnet URI in BBCode: ``` [magnet]magnet:?xt=urn:btih:EXAMPLEHASH&dn=Example.File[/magnet] ``` Or use the editor button to insert / wrap the selection automatically. Permissions ----------- [](#permissions) PermissionDefaultWhat it grants`tryhackx-magnet-link.viewMagnetLinks`MembersOpen the magnet link / use the tooltip / fetch stats.CLI --- [](#cli) CommandPurpose`php flarum magnet:reparse`Re-parse posts whose `[magnet]` BBCode was saved before the extension was active. Idempotent; safe to run multiple times.`php flarum magnet:retokenize`Re-derive all magnet tokens onto the current secret-salt scheme. Run once after upgrading from ≀ 2.2.x. Idempotent.`php flarum magnet:prune-clicks --days=N`Delete `magnet_clicks` rows older than *N* days to bound table growth. Aggregate `click_count` totals are kept; only the per-row click history (and the topic-scoped click *sorts*' time window) is trimmed. `--dry-run` reports the count without deleting.`php flarum magnet:prune-bans [--minutes=N]`Delete **expired** IP bans from `magnet_bans` (older than the ban window; defaults to the `ban_time` setting). `isBanned()` only clears expired bans lazily for IPs that get re-checked, so on a bot-targeted forum the table otherwise grows unbounded. `--dry-run` reports the count without deleting.> **Retention is opt-in by design.** Nothing prunes `magnet_clicks` automatically β€” the topic-scoped click sorts count from it directly, so the retention window is the operator's call, not ours. On a busy tracker, wire it into your system cron, e.g. `0 4 * * * php /path/to/flarum magnet:prune-clicks --days=90`. (There is deliberately no built-in scheduler registration: auto-pruning would silently shrink the click-sort window without the operator choosing it.) > > `magnet:prune-bans` is the same idea for the IP-ban table, and is safe to schedule freely (it only ever removes already-expired bans), e.g. `0 4 * * * php /path/to/flarum magnet:prune-bans`. Database -------- [](#database) TablePurpose`magnet_links`Tokens, info hashes, and the full magnet URIs.`magnet_clicks`Click history per IP / user.`magnet_bans`Temporary IP bans.`magnet_custom_names`Per-author custom display names per magnet Γ— post.🚨 Troubleshooting ----------------- [](#-troubleshooting) - **UDP trackers don't work** β€” enable *HTTP(S) Trackers Only* or install / enable the `sockets` PHP extension. - **Stats show "no usable trackers"** β€” the tracker host may resolve to a private / reserved IP and be blocked for safety. If that's intentional (e.g. a LAN tracker), enable *Allow Private/Internal Trackers*. - **In-post magnets show as raw `[magnet]…[/magnet]` text** β€” run the backfill (`php flarum magnet:reparse` or the admin button). - **500 from the API** β€” check the Flarum logs, ensure migrations have been run. - **Stats look stale** β€” they're cached; use the per-link refresh button to force a re-scrape, or lower *Cache Lifetime* (set 0 to disable caching). πŸ”— Links & credits --------------------- [](#-links--credits) - [GitHub Repository](https://github.com/TryHackX/flarum-magnet-link) - [Report an Issue](https://github.com/TryHackX/flarum-magnet-link/issues) - Scraper library: [Scrapeer](https://github.com/medariox/scrapeer) by medariox - Extension author: TryHackX Β© 2026 ### Health Score 46 β€” FairBetter than 92% of packages Maintenance98 Actively maintained with recent releases Popularity16 Limited adoption so far Community4 Small or concentrated contributor base Maturity55 Maturing project, gaining track record How is this calculated?**Maintenance (25%)** β€” Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** β€” Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** β€” Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** β€” Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~17 days Recently: every ~25 days Total 8 Last Release 13d ago Major Versions 1.0.2 β†’ 2.0.02026-02-21 1.0.6 β†’ 2.0.82026-04-23 1.0.8 β†’ 2.0.92026-05-30 PHP version history (2 changes)2.0.0PHP ^8.2 2.9.1PHP ^8.3 ### Community Maintainers ![](https://www.gravatar.com/avatar/21efa76fc04b119116af8bed43651ffee8de017be7318127f6e3996dc29b0974?d=identicon)[TryHackX](/maintainers/TryHackX) --- Tags extensionscrapertorrentbbcodeflarumtrackertooltipbackfillmagnetssrf-protectiontoken-securityclick-counter ### Embed Badge ![Health badge](/badges/tryhackx-flarum-magnet-link/health.svg) ``` [![Health](https://phpackages.com/badges/tryhackx-flarum-magnet-link/health.svg)](https://phpackages.com/packages/tryhackx-flarum-magnet-link) ``` ### Alternatives [flarum-lang/russian Russian language pack for Flarum. 12128.3k](/packages/flarum-lang-russian)[flarum-lang/french French language pack to localize the Flarum forum software plus its official and third-party extensions. 1938.7k](/packages/flarum-lang-french)[fof/masquerade User profile builder extension for your Flarum forum. 2025.4k5](/packages/fof-masquerade)[fof/sitemap Generate a sitemap 1899.7k2](/packages/fof-sitemap)[flarum/gdpr Features for GDPR, PII management 1338.8k22](/packages/flarum-gdpr)[fof/discussion-language Specify the language a discussion is written in & sort by language 1034.8k4](/packages/fof-discussion-language) PHPackages Β© 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)