Methodology

How records enter this catalogue, what the ordering means, where the facts come from, and what the catalogue does not claim. Every figure on this page is derived from the data at build time, not written by hand.

Catalogue as it stands

Public records

83

Core relevance

70

Mechanism

10

Adjacent

3

No licence detected

17

Archived

0

Verified but withheld

1

Hugging Face artifacts

14

Repository data synced

Aug 23, 2026

Two kinds of source, kept apart

Repository facts (stars, licence, last push and archived state from GitHub; likes, downloads, licence tags and gated access from Hugging Face) are synced daily by scripts and never hand-written; relevance, the bilingual summaries and the maturity rating are editorial judgement and are never overwritten by a sync. That is why each card carries two dates. A star count or download figure moving does not refresh the editorial date, and does not refresh the sitemap lastmod either.

Hugging Face artifacts (models, datasets, Spaces) measure differently from GitHub: likes are not stars, the download figure covers the trailing thirty days, and this catalogue never converts or co-ranks the two. On records marked gated, the metadata is public but downloading the files requires accepting the author’s terms on Hugging Face. Hugging Face has no archived state, so that badge only ever appears on GitHub records.

What gets in

• The primary deliverable is code, data, a spec, templates or a maintained resource list in a public repository.
• It has a stateable, direct relation to GEO, generative search, AI citation, or the retrieval and ranking machinery those depend on. Relevance is graded core, mechanism or adjacent by which layer the deliverable acts on, not by what its author intended.
• Every record is checked by hand — README read, licence state and repository identity confirmed, verification dated. Unverified records do not appear on the site.
• A low star count is not grounds for rejection, and neither is a long gap since the last push: the date is shown and the reader judges.

What does not

• General SEO projects with no derivation chain to generative search, and general-purpose LLM frameworks with no GEO connection.
• Repositories whose substance is marketing copy, auto-generated low-quality collections, and forks with no meaningful divergence from upstream.
• Malicious code, credential harvesting, and infringing mirrors.
• Practitioner tools that recommend manipulation. Research code documenting attacks and poisoning is catalogued, because that is evidence of a vulnerability; a tool that recommends cloaking-adjacent practice, self-placement or manufactured entity consensus is not listed alongside legitimate optimization. Such records count toward "verified but withheld" above.

Ordering

The default order is curated: relevance first, then name. Stars are a popularity signal, not a quality or relevance score, so they do not participate in the ordering; they appear on the card as one fact among several. This catalogue computes no health score and gives no project an overall grade.

Licences

No licence detected. Publicly viewable source code does not by itself grant permission to copy, modify or redistribute it. Check with the repository owner.

No licence detected does not mean proprietary, and nothing here is a legal conclusion. Upstream code remains under its own terms; this site's CC BY 4.0 does not extend to third-party code.

What this catalogue is not

• Inclusion is not a security audit and not a recommendation to run anything in production. We do not execute, install or scan upstream code.
• Available means only that the platform API answered and the repository is neither archived nor disabled. It does not mean active, safe, or production-ready.
• We do not mirror READMEs, scrape contributor profiles, or build developer leaderboards.
• We make no completeness claim. The distribution above is the current boundary, and its gaps are visible in it.

Coverage by task and maturity

Maturity is an editorial judgement. It is never derived from stars, releases or push dates, and is always shown alongside the date it was last reviewed.

Freshness and corrections

Repository facts are synced once a day, with separate snapshots for GitHub and Hugging Face; the index reports the older of the two sync times. Past 72 hours the index says so; past fourteen days the volatile counts (stars, likes, downloads) stop being shown rather than being presented as current.

Found a factual error? Write to support@geo.wiki. Project submissions are not open at this time.

Back to the project index