torlink: a zero-setup terminal torrent finder that searches a curated source list at once

Finding torrents without the ad-choked websites

torlink is a torrent finder that lives in your terminal, and its pitch is a direct reaction to how bad torrent websites have become. The README describes the problem plainly: one site is a minefield of fake download buttons, another buries the real link under popups, and half the results are dead with zero seeders. torlink searches a short, curated list of reputable sources at once, and whatever you pick downloads straight to your downloads folder.

The user is someone who wants to find and fetch legal torrents, Linux ISOs, public-domain media, open datasets, without wading through the hostile web UIs that surround torrent search. It is zero-setup with nothing to configure, which is the whole point: the friction it removes is both the websites and the usual install ritual.

What makes it distinct is the curated-source approach. Rather than being one more index, torlink queries several reputable sources in a single search and merges the results, tagged with size and seeder count so you can see what will come down fast. It is MIT licensed and distributed through npm, so it is a thin client over existing sources rather than a tracker itself.

One search across every source, merged and tagged

The mechanism is aggregation with live streaming. The README says one search checks the curated sources at once, and results stream in from every source as they answer, each tagged with size and how many people are sharing it. That merge-and-tag behavior is what replaces visiting several sites: you type once and see combined, ranked results.

The interaction is entirely keyboard-driven. The README describes arrowing to a result and pressing `d` to save it, or `shift+d` to choose a different folder for that one download, with `?` bringing up the full key list. Beyond search, it accepts a magnet link, a bare infohash, or a `.torrent` file dragged onto the window, and pressing Enter on an empty box browses the curated library.

Because the downloaded files are saved to your downloads folder and are yours, torlink is a finder and fetcher, not a streaming service or a hosted index. The curated source list is the editorial judgment at the center of it: the value is that someone chose reputable sources so you do not have to evaluate each sketchy site yourself, which is also the thing you are trusting when you use it.

Getting started with one command

torlink's setup story is genuinely one line. The README's only prerequisite is Node, and the entire start is an npx invocation:

npx torlnk

The README notes that is the only thing you type: torlink opens straight to a search bar, and from there it is all keypresses with nothing to memorize. Because it runs through npx, there is no global install to manage and no configuration file, which is what the zero-setup claim means in practice.

The repository is a TypeScript project with a Nix flake (`flake.nix`, `flake.lock`) for reproducible development, so contributors get a defined environment, while end users only ever need Node and the npx command. The `preview/` assets in the tree are the splash and browse-view graphics the README shows.

The simplicity here is the feature. A tool whose full documentation for getting started is install Node and run `npx torlnk` has essentially no adoption cost, and the keyboard-only interface means the learning curve is a single `?` press away. That is a deliberate contrast to the friction-heavy experience of torrent websites it is built to replace.

The limitations: a curated list you trust, and legality is on you

The honest limitations start with the curated-source model itself. torlink's usefulness depends entirely on the quality and freshness of the source list it ships, which is a curatorial decision baked into the tool. If a source degrades or goes offline, your results narrow until the list is updated, and you are trusting the maintainer's choice of sources rather than picking them yourself. That trust is the trade for not having to vet sites, but it is real.

The deeper limitation is legal and entirely the user's responsibility. torlink finds and downloads torrents; what those torrents contain and whether you are entitled to download them is not something the tool judges. It is well suited to legal content, distributions, public-domain works, open datasets, and using it for anything else is on the user, not the tool.

There is also the inherent nature of torrents: results are only as good as their seeders. The README's seeder tagging helps you avoid dead torrents, but torlink cannot conjure availability that is not there, so a rare item with no seeders will not download regardless of how cleanly the search surfaces it.

Against a torrent website or a full BitTorrent client

The alternatives are a torrent search website plus a separate BitTorrent client, or a heavyweight desktop client with built-in search. A website gives the broadest reach but is exactly the hostile, ad-laden experience torlink exists to avoid, and it still needs a separate client to download. A full desktop client like a mature GUI torrent app offers deep features, queues, bandwidth scheduling, detailed peer management, but is a heavier install and a different workflow.

torlink's difference is that it collapses search and download into one zero-setup terminal tool over a curated source list, with no ads, no configuration and no separate client to install. The cost is scope: it is not a full-featured torrent client with fine-grained control, and its reach is bounded by its curated list rather than the whole torrent web. Choose a website plus client when you need maximum reach and are willing to fight the UI. Choose a full desktop client when you want detailed download management. Choose torlink when you want to find and grab a torrent quickly from reputable sources without setup or ads, and the curated list covers what you are after.

MIT, npx distribution, and where to start

torlink is MIT, so it can be forked, inspected and adapted with attribution, and its npm distribution means there is nothing to maintain locally: each `npx torlnk` runs the current published version. That also means updates to the curated source list and the client arrive automatically the next time you run it, which is important given that the source list is the part most likely to need refreshing.

Because the whole tool is a thin client with no persistent configuration and no local install, the maintenance burden on a user is effectively zero, and the Nix flake in the repository signals the maintainer keeps a reproducible development setup for updating it.

The concrete first step is simply to run it: install Node if you do not have it, run `npx torlnk`, and try a search for something you are entitled to download to see how the merged, seeder-tagged results look. Confirm the download lands in your downloads folder as the README describes, and press `?` to learn the keys, since the entire interface is keyboard-driven and that one keystroke is the full manual.

Editorial conclusion

Use torlink if you want to find and download legal torrents from reputable sources without ad-choked websites or any setup: the single npx torlnk command, the merged seeder-tagged results across a curated source list, and downloads straight to your folder are its whole appeal. It is the wrong tool if you need a full-featured BitTorrent client with detailed download management, or if you expect it to reach the entire torrent web rather than its curated list, and it makes no judgment about the legality of what you download, which is your responsibility. Start by installing Node, running npx torlnk, searching for content you are entitled to, and pressing ? to learn the keyboard-driven interface.

Frequently asked questions

Official sources

1. baairon/torlink on GitHub
2. License: MIT
3. Project website
4. README
5. Releases