Package search
search.solnix.io is full-text search over the Solnix
package set — the illumos analog of search.nixos.org/packages. Use it to find
whether a tool is packaged, which architectures it is built for, and how to
install it.
Using it
- Type a name or keyword; results rank the best match to the top and refine as you type.
- Prefix matching:
rtlfindsrtldbefore you finish typing. - Typo-tolerant:
opnsshstill findsopenssh. - By meaning: set Match to Names and meaning to also find packages by what
they do, when you don’t know the name:
compress filesfindszip,gzip,bzip2;terminal multiplexerfindstmuxandscreen. Meaning only drops the name match. Keyword stays the default. Meaning comes from short descriptions (from nixpkgs, matched by exact attribute name) that about 1,500 of the 3,556 packages have so far, so packages without one only match by name. If meaning search is busy or down, the page says so and shows keyword matches. - A package’s detail view lists related packages: the closest by description.
- Each result shows the architectures it is available for and, in the detail
view, how to install it (declarative
environment.systemPackages,nix profile install nixpkgs#<name>,nix-env -iA nixos.<name>, or an ephemeralnix shell nixpkgs#<name>) plus links to its man pages and dependencies. On Solnix,nixpkgsandsolnixboth mean the Solnix package set; pin withsolnix:26.11#<name>. From another Nix host usegit+https://git.solnix.io/solnix.git?ref=unstable#<name>. - Many catalogued packages are not installable yet: only names the Solnix flake exports resolve. Their detail view says so instead of showing a command.
Everything found there is served by the binary cache — add the cache and the package installs without recompiling.
Following new packages
The registry publishes update feeds so you can track new and changed packages:
The announce@ mailing list rolls these up (once list
subscription is open).
Programmatic access
There is a public REST + GraphQL API for the package data (search, package detail, dependency graph, man pages, systems). See the API reference at https://search.solnix.io/api/v1/openapi.json — this is tooling for building on top of Solnix, not something you need for everyday use.
Every search endpoint (REST packages, manpages, handbook/search, search;
GraphQL packages, manpages, handbookSearch; the MCP search tools) takes
mode=keyword|semantic|hybrid. keyword is the default. semantic ranks by
meaning (384-dimension bge-small-en-v1.5 embeddings in Postgres, through the
pg_turbovec extension). hybrid fuses the keyword and meaning rankings
(reciprocal rank fusion). If the query embedder is busy, slower than 300 ms,
rate-limited (60 meaning searches per minute per address) or down, you get keyword
results and the reply says so: "semantic": {"used": false, "reason": ...}
(header X-Solnix-Semantic on /api/v1/packages, whose body stays a plain list).
GET /api/v1/related?kind=package&ref=pkgs.solnix.zstd returns a stored package’s,
man page’s (kind=manpage&ref=gzip/1) or handbook section’s nearest neighbours.