Question 1

What is StarMapper?

Accepted Answer

StarMapper is a free web tool that shows you where your GitHub repository's stargazers are located. It fetches all stargazers via the GitHub API, geocodes their profile locations, and renders them on an interactive world map with country, city, and company statistics.

Question 2

Is StarMapper free to use?

Accepted Answer

Yes, StarMapper is completely free. No account, no login, and no credit card required. Just paste a GitHub repository URL and click Map It.

Question 3

How does StarMapper work?

Accepted Answer

StarMapper fetches the list of stargazers for a GitHub repository using the GitHub GraphQL API. It then geocodes each user's self-reported location using a shared geocoding cache. The results are rendered on an interactive MapLibre GL map with native clustering, grouped by country and city.

Question 4

Does StarMapper work with private repositories?

Accepted Answer

StarMapper only works with public GitHub repositories. Private repository data is not accessible via the public GitHub API.

Question 5

How accurate is the stargazer location data?

Accepted Answer

Location accuracy depends on what GitHub users enter in their profile. StarMapper geocodes free-text location fields, so accuracy varies. On average, 60–80% of stargazers have a mappable location. Users who leave their location blank appear in the 'Unmapped' list.

Question 6

Can I embed a StarMapper badge in my README?

Accepted Answer

Yes. After scanning a repository, StarMapper generates an embeddable SVG badge showing the star count and number of mapped countries. You can copy the Markdown snippet directly from the map page.

Question 7

Where does the stargazer data come from?

Accepted Answer

StarMapper uses the GitHub public API (GraphQL + REST) with an authenticated token to access publicly visible profile fields: username, display name, and the self-declared location field. Location text is geocoded using Jawg, Geoapify, and Nominatim. Results are displayed as geographic clusters, not searchable individual records. See our Privacy Policy for details.

Question 8

How do I request removal of my data from StarMapper?

Accepted Answer

Send an email to florian@bruniaux.com with your GitHub username and confirmation that you own the account. We will delete your profile data and star events within 30 days. Alternatively, remove your location from your GitHub profile settings — the next scan will reflect the change automatically.

Signal	Gate	Thresholds	Weight
Fork / Star ratio	stars ≥ 5 000	≥ 10% → 100 · 7% → 50 · ≤ 2% → 0	30%
Watcher / Star ratio	always	≥ 0.5% → 100 · 0.1% → 50 · ≤ 0.01% → 0	5%
% zero-follower stargazers	sample ≥ 30	≤ 10% → 100 · 30% → 50 · ≥ 60% → 0	45%
Releases cadence	always	≥ 100 → 100 · 20 → 60 · 5 → 30 · 0 → 0	20%

Repo	Expected	Stars	Fork/★	Watch/★	Zero-fol.	Releases	Score	Tier	✓
pallets/flask	healthy	71 432	23.5%	2.9%	—	~140	100	Healthy	✅
langchain-ai/langchain	healthy	134 373	16.5%	0.6%	3.4%	~210	93	Healthy	✅
Significant-Gravitas/AutoGPT	healthy	183 636	25.2%	0.8%	—	~70	92	Healthy	✅
crewAIInc/crewAI	healthy	49 425	13.7%	0.7%	—	~55	92	Healthy	✅
langgenius/dify	healthy	138 645	15.7%	0.6%	3.9%	~320	92	Healthy	✅
agno-agi/agno	healthy	39 573	13.4%	0.6%	—	~100	91	Healthy	✅
mem0ai/mem0	healthy	53 711	11.2%	0.4%	—	~85	90	Healthy	✅
browser-use/browser-use	healthy	89 197	11.4%	0.5%	3.7%	~30	92	Healthy	✅
rtk-ai/rtk	healthy	32 308	5.8%	0.26%	7.4%	147	74	Healthy	✅
NousResearch/hermes-function-calling	healthy	1 292	—	1.4%	—	~5	68	Moderate	❌
yargs/yargs	healthy	11 471	8.9%	0.7%	—	~110	75	Moderate	✅
unionlabs/union	suspicious	74 134	5.2%	2.2%	—	~30	41	Suspicious	✅
shardeum/shardeum	suspicious	31 497	2.2%	0.9%	—	~10	8	Suspicious	✅
Anoma/anoma	suspicious	33 916	12.1%	0.6%	—	~20	91	Healthy	❌
langflow-ai/langflow	suspicious	147 213	6.0%	0.3%	—	~340	44	Suspicious	✅
sindresorhus/awesome	control	457 552	7.5%	1.8%	3.5%	—	70	Moderate	—
facebook/react	control	244 629	20.8%	2.7%	3.5%	~50	100	Healthy	—

Signal	StarMapper	StarScout	Notes
Fork / star ratio	✓ 30%	✓	Reduced from 40% — fork/star penalises CLI tools with low fork rates by nature
% zero-follower stargazers	✓ 45%	partial	Strongest discriminator when sample size ≥ 30. Reduced slightly to make room for releases signal
Watcher / star ratio	✓ 5%	—	Weakly discriminating in practice — weight kept low
Releases cadence	✓ 20%	—	New signal — total GitHub releases as proxy for active, maintained project
Clustering (account overlap across repos)	—	✓	Key signal in StarScout — requires full graph analysis
Temporal burst (stars in short window)	—	✓	Requires star timestamp history at scale
Account age + activity pattern	—	✓	Detects sophisticated fakes — not available from public API alone

Organic Score — Calibration Data

Signal Normalisation (0 → 100)

Corpus Results

Methodology vs. StarScout

Caveats

References