A developer frustrated by the poor user experience on most distribution package websites has built a new search tool that indexes nearly 2.8 million packages across 129 Linux repositories. pkg.bot, created by Nadh, launched in early September 2026 and aims to make finding Linux packages fast and straightforward.
Why another package search tool exists
Most Linux distributions maintain their own package search interfaces, but the quality varies widely. When Nadh switched to NixOS recently, he found the official package site cumbersome to use: no sorting by date or version, no way to share a direct link to a package page. The experience mirrored what many developers encounter across Debian, Fedora, Arch, and other ecosystems, where each distro ships its own search tool with inconsistent features and interface quality.
The core problem is fragmentation. A developer looking for a specific library or tool might need to check three or four different distribution sites, each with different search syntax and limited filtering options. pkg.bot consolidates all of this into one interface.
What the tool actually does
The search engine pulls package metadata from Repology, a well-known project that aggregates package information across distributions. Data refreshes weekly, keeping version numbers and repository listings reasonably current. The tool covers mainstream distributions like Ubuntu, Debian, Fedora, Arch, and openSUSE alongside niche projects like Parabola, Pardus, and Manjaro variants.
Search supports full-text matching across package names, descriptions, and keywords. Developers can filter results by license, maintainer, platform, or package status, such as identifying which packages are outdated or contain known issues. Version comparisons work with standard operators, for example finding all packages where the version exceeds 2.0, and date filtering lets you narrow results to packages updated after a specific cutoff.
Building on existing infrastructure
The project is built on Repology's data rather than crawling individual repository websites. This approach gives pkg.bot consistent metadata across all supported distributions while avoiding the maintenance burden of tracking changes on hundreds of separate package sites. Repology itself normalizes package names, versions, and metadata across different packaging formats like deb, rpm, and nix.
The project is open source and available on GitHub. A JavaScript API and a simple Bash CLI script are provided for integration into existing workflows.
Why developers should care
The practical value shows up in two places. First, the web interface gives you a single place to search across any distribution without navigating different websites. You can quickly compare what versions are available across Alpine, Fedora, and Ubuntu without leaving one page.
Second, the API and CLI tools enable automation. The API returns JSON by default, and also supports CSV output that can be piped directly into other tools or used by LLMs. A developer could script a check for outdated dependencies across their target distributions, or build a notification system for new package releases. The Bash CLI lets you search packages without leaving the terminal.
Looking at the broader pattern
pkg.bot fits into a growing trend of developers building better tooling around existing open infrastructure. Rather than creating yet another package format or distribution, the project improves how people interact with information that already exists. The Repology data already covers these repositories, but most developers never use it directly because the individual distribution websites make the experience painful.
With 129 repositories and nearly 2.8 million packages indexed, the tool provides a useful snapshot of the Linux packaging ecosystem. The RSS feed support is a nice touch, letting developers follow updates to specific packages or search results without relying on third-party monitoring services.
The project is still new, and the maintainers are actively working on features. Contributions and feedback are welcome on GitHub.