HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
TecharoHQ
anubis
Go2025–2026
TecharoHQ / anubis

anubis

Weighs the soul of incoming HTTP requests to stop AI crawlers

67Distinct people
80Mentions
1Explicit recommenders
24.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Weighs the soul of incoming HTTP requests to stop AI crawlers

GitHub

Where it is used

The last source check was inconclusive. This does not establish whether a product uses it.

What people are saying

This is just like security; the most secure system is the one that nobody can use. I think the proof-of-work approach that anubis[0] takes is pretty interesting. I love the…

wolttam used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 8:59:02 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month80 dated mentions

Observed mentions: 2025-03-18 05:45:12 UTC to 2026-10-18 18:22:03 UTC.

051015202025-03-01 00:00:00 UTC to 2025-04-01 00:00:00 UTC (exclusive): 12 mentions; 3 submissions, 9 commentsMar 20252025-04-01 00:00:00 UTC to 2025-05-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2025-05-01 00:00:00 UTC to 2025-06-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2025-06-01 00:00:00 UTC to 2025-07-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2025-07-01 00:00:00 UTC to 2025-08-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2025-08-01 00:00:00 UTC to 2025-09-01 00:00:00 UTC (exclusive): 20 mentions; 1 submissions, 19 comments2025-09-01 00:00:00 UTC to 2025-10-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-10-01 00:00:00 UTC to 2025-11-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-11-01 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2025-12-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 commentsDec 20252026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-01 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-04-01 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2026-05-01 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-06-01 00:00:00 UTC to 2026-07-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2026-07-01 00:00:00 UTC to 2026-08-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-08-01 00:00:00 UTC to 2026-09-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2026-09-01 00:00:00 UTC to 2026-10-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-10-01 00:00:00 UTC to 2026-11-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 commentsOct 2026

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 20252025-03-01 00:00:00 UTC2025-04-01 00:00:00 UTC1239
Apr 20252025-04-01 00:00:00 UTC2025-05-01 00:00:00 UTC606
May 20252025-05-01 00:00:00 UTC2025-06-01 00:00:00 UTC505
Jun 20252025-06-01 00:00:00 UTC2025-07-01 00:00:00 UTC211
Jul 20252025-07-01 00:00:00 UTC2025-08-01 00:00:00 UTC413
Aug 20252025-08-01 00:00:00 UTC2025-09-01 00:00:00 UTC20119
Sep 20252025-09-01 00:00:00 UTC2025-10-01 00:00:00 UTC101
Oct 20252025-10-01 00:00:00 UTC2025-11-01 00:00:00 UTC101
Nov 20252025-11-01 00:00:00 UTC2025-12-01 00:00:00 UTC505
Dec 20252025-12-01 00:00:00 UTC2026-01-01 00:00:00 UTC404
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC000
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC000
Mar 20262026-03-01 00:00:00 UTC2026-04-01 00:00:00 UTC101
Apr 20262026-04-01 00:00:00 UTC2026-05-01 00:00:00 UTC211
May 20262026-05-01 00:00:00 UTC2026-06-01 00:00:00 UTC202
Jun 20262026-06-01 00:00:00 UTC2026-07-01 00:00:00 UTC404
Jul 20262026-07-01 00:00:00 UTC2026-08-01 00:00:00 UTC303
Aug 20262026-08-01 00:00:00 UTC2026-09-01 00:00:00 UTC404
Sep 20262026-09-01 00:00:00 UTC2026-10-01 00:00:00 UTC101
Oct 20262026-10-01 00:00:00 UTC2026-11-01 00:00:00 UTC303

What Hacker News says

5 sources
They do use SubtleCrypto digest [0] in secure contexts, which does the hashing natively. Specifically for Firefox [1] they switch to the JavaScript fallback because that's actually faster [2] (because of overhead probably): > One of the biggest sources of lag in Firefox has been eliminated: the use of WebCrypto. Now whenever Anubis detects the client is using Firefox (or Pale Moon), it will swap over to a pure-JS implementation of SHA-256 for speed. [0] https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypt... [1] https://github.com/TecharoHQ/anubis/blob/main/web/js/algorit... [2] https://github.com/TecharoHQ/anubis/releases/tag/v1.22.0
In You Don't Need Anubis
> Work functions don't make sense as a token tax; there's actually the opposite of the antispam asymmetry there. Every bot request to a web page yields tokens to the AI company. Legitimate users, who far outnumber the bots, are actually paying more of a cost. Agreed, residential proxies are far more expensive than compute, yet the bots seem to have no problem obtaining millions of residential IPs. So I'm not really sure why Anubis works—my best guess is that the bots have some sort of time limit for each page, and they haven't bothered to increase it for pages that use Anubis. > with a content protection system built in Javascript that was deliberately expensive to reverse engineer and which could surreptitiously probe the precise browser configuration a request to create a new Youtube account was using. > The next thing Anubis builds sho
Read the rest
uld be that, and when they do that, they should chuck the proof of work thing. They did [0], but it doesn't work [1]. Of course, the Anubis implementation is much simpler than YouTube's, but (1) Anubis doesn't have dozens of employees who can test hundreds of browser/OS/version combinations to make sure that it doesn't inadvertently block human users, and (2) it's much trickier to design an open-source program that resists reverse-engineering than a closed-source program, and I wouldn't want to use Anubis if it went closed-source. [0]: https://anubis.techaro.lol/docs/admin/configuration/challeng... [1]: https://github.com/TecharoHQ/anubis/issues/1121
In You Don't Need Anubis
> But it still works, right? People use Anubis because it actually stops LLM bots from scraping their site, so it must work, right? > Yeah, but only because the LLM bots simply don’t run JavaScript. I don't think that this is the case, because when Anubis itself switched from a proof-of-work to a different JavaScript-based challenge, my server got overloaded, but switching back to the PoW solution fixed it [0]. I also semi-hate Anubis since it required me to add JS to a website that used none before, but (1) it's the only thing that stopped the bot problem for me, (2) it's really easy to deploy, and (3) very few human visitors are incorrectly blocked by it (unlike Captchas or IP/ASN bans that have really high false-positive rates). [0]: https://github.com/TecharoHQ/anubis/issues/1121
In You Don't Need Anubis

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.