whoogle-search

benbusby/whoogle-search

A self-hosted, ad-free, privacy-respecting metasearch engine

SearchFor consumersSelf-hostable

Ship status

Gone silent
Last push
Aug 14, 2026
49 days ago
Stars, last 7 weeks
Stars, weekly: 11,595 → 11,569 (Aug 18 – Sep 29, 2026)
−12 stars in the 28 days to 2026-09-29

GitHub reports this repository as archived. That forces the status to silent whatever the last push says.

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
11.6K
Forks
1.1K
Open issues
1
Watchers
103
Primary language
Python
Created
Jan 21, 2020
Owner
benbusby · User

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 110 startups in the directory ship primarily in Python.

Topics

#adblock#docker#easy-deploy#flask#heroku#metasearch#metasearch-engine#privacy#python#search#search-engine

How it got here

What the classifier decided, and when.

Read by Jev, TypeSafe’s classifier, on Sep 22, 2026, which did not call this an open-source startup — it chose a package or library instead, and put os_startup at 11% (self-hostable 97%, hosted offering 8%). The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory. This one is in that queue, waiting for a person — removing a listing is a pull request a human opens.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: silent — last push 2026-08-14This is the badge for benbusby/whoogle-search, as served from the URL below.
[![OSSEAN: silent](https://ossean.com/badge/benbusby/whoogle-search.svg)](https://ossean.com/benbusby/whoogle-search)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.