Install anubis with Homebrew, apk, dnf, MacPorts, Nix, pacman, zypper

Project links

• Homepage
• Repository
• Package manager page

Commands and aliases

• anubis

Project history

The official README frames Anubis as a response to heavy scraper traffic from AI companies, especially for smaller sites that cannot or do not want to depend on a larger hosted protection service. The setup docs describe it as a component that sits between a reverse proxy such as Nginx or Caddy and the target service, one Anubis instance per protected service.

The project is implemented and released actively through the TecharoHQ/anubis repository. Its release feed shows a fast-moving 1.x series, with v1.26.0-pre1 in June 2026 including security, metrics, policy, localization, and performance work.

Adoption history

Anubis entered package-manager ecosystems quickly for a young security tool: the input package facts list Homebrew, Alpine, Fedora, MacPorts, Nix, Arch, and openSUSE packaging. The README also links a Repology packaging badge, suggesting upstream cares about distribution visibility.

Its adoption story is tied to the post-LLM web: administrators use it when they need proof-of-work challenges, allow/deny/challenge bot rules, and reverse-proxy integration without moving the whole site behind a proprietary edge service.

How it is used

Operators run Anubis as a reverse proxy or sidecar and configure target service routing with environment variables plus a policy file. Official docs document BIND, TARGET, PUBLIC_URL, cookie settings, metrics settings, and POLICY_FNAME, while the policy docs define YAML or JSON rules for paths, user agents, headers, remote addresses, actions, challenge difficulty, and metrics.

The policy file is the important package-nerd surface: it is not just a daemon config, it is the distribution of bot behavior. The default policy file, local overrides, known-good bot allowlists, and reverse-proxy examples are where the package turns from binary into operational security posture.

Why package nerds care

Anubis is interesting because it is a small, installable answer to an infrastructure-wide problem. It sits at the intersection of Go single-binary packaging, container images, reverse proxy snippets, and web-administration policy files.

For package maintainers, Anubis also has a moving target problem: security advisories, bot identifiers, browser behavior, and AI-crawler names change quickly, so the value of a package is not only the binary but also timely updates and clear policy migration notes.

Timeline

• 2025: Public 1.x tags and package-manager entries establish Anubis as a distributable CLI service.
• 2026: v1.26.0-pre1 release notes include security-advisory work, metrics policy moves, pprof gating, localization, and performance improvements.

Related projects

• Caddy, Nginx, Traefik, HAProxy, Apache, and Kubernetes appear in official deployment documentation as front-end environments for Anubis.
• The official default bot policy file is the related configuration artifact most users customize.

Sources

• Official README, installation docs, policy docs, release feed, and source_facts.package-manager.