Incorrect AI contributor "claude Claude" showing in repository

[hephaex]

Select Topic Area

Question

Body

Issue

Repository: https://github.com/hephaex/mecab-ko

"claude Claude" incorrectly appears in the Contributors section (showing 2 contributors), but this should not be there.

Evidence

1. GitHub API shows only 1 contributor:
   gh api repos/hephaex/mecab-ko/contributors
   Returns: only "hephaex" (295 commits)

2. No commits by claude user:
   gh api repos/hephaex/mecab-ko/commits?author=claude
   Returns: 0 results

3. Git log shows only Mario Cho:
   All 310 commits are authored by Mario Cho <hephaex@gmail.com>

4. No Co-authored-by trailers mention Claude or Anthropic

Screenshot

[Contributors showing "claude Claude" incorrectly]

Question

How can I remove this incorrect contributor entry? The API and UI are inconsistent.

[jayDevCodes]

This usually comes from commit/automation/bot metadata — the commit author name/email or an integration may be set to something like "claude".

Check the repository’s Contributors graph and recent commit history, and review Actions / third-party apps in Settings → Integrations to see if a bot or CI is making commits.

If commit author metadata is wrong, you can fix it locally with tools like git filter-repo or git rebase --interactive to rewrite author info, then force-push — but coordinate with your team because this changes history.

If GitHub’s UI is incorrectly attributing an AI contributor (a platform bug), gather a screenshot and repo details and report it to GitHub Support.

[itxashancode]

This is GitHub's AI contribution attribution feature incorrectly flagging code as AI-generated. I've seen this happen with Claude-named contributions before.

Go to your repo Settings → Code security and analysis → scroll to "AI-powered features" → disable "AI contribution attribution".

That setting adds an "AI" contributor when GitHub's detection thinks code was AI-generated. Since your logs show no actual claude user commits, it's a false positive from the analysis. Disabling it removes the entry.

The API and UI inconsistency happens because the contributor list includes this synthetic AI entry, while the raw contributor API doesn't.

[hephaex]

Thank you so much for your help! Disabling the *'AI contribution attribution'* setting as you suggested completely resolved the issue. I really appreciate you clarifying the inconsistency between the UI and the API. Your explanation was incredibly helpful! Thanks. Mario Cho. 2026년 4월 8일 (수) 오전 6:48, Ashan Abdur Rehman Zahid ***@***.***>님이 작성:

…

This is GitHub's AI contribution attribution feature incorrectly flagging code as AI-generated. I've seen this happen with Claude-named contributions before. Go to your repo Settings → Code security and analysis → scroll to "AI-powered features" → disable "AI contribution attribution". That setting adds an "AI" contributor when GitHub's detection thinks code was AI-generated. Since your logs show no actual claude user commits, it's a false positive from the analysis. Disabling it removes the entry. The API and UI inconsistency happens because the contributor list includes this synthetic AI entry, while the raw contributor API doesn't. — Reply to this email directly, view it on GitHub <#188915 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA43KTUPQIVOMNKH4AXFKST4UVZTPAVCNFSM6AAAAACWKXUDJ2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNBYGE3TCNQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Err0r-v2]

This feature doesn't appear on my repo

[bellonet]

Same. I don't see "Code security and analysis" at all. I only see the security tabs in attached menu and and couldn't find "AI contribution attribution" in any.

[javicueto]

same, where is that option?

[neilmanfredit]

I have the same bug on two repos of mine, when there has been no comits etc by claude etc I tried to raise a support request on this but it was closed as above as well I dont have the feature on my repos also

[roman-dvorak]

I have the same issue

[neilmanfredit]

I agree completely but GitHub closes the request to review

…

On Wed, 5 Aug 2026, 16:31 Razaakhtar-coder, ***@***.***> wrote: The Contributors page and the /contributors API aren't generated from exactly the same data, so it's possible for them to disagree temporarily or in edge cases. A few things to check: - Inspect the repository's *Insights → Contributors* page and compare it with the repository homepage's Contributors section, as they may be refreshed on different schedules. - Search the full commit history (including all branches) for claude as both an author and committer: git log --all --format="%H %an <%ae> | %cn <%ce>" | grep -i claude - Check whether there were any force-pushes or rewritten commits. GitHub's cached contributor data can lag behind history rewrites. - If you've verified that there are no commits, no co-author trailers, and the REST API also reports only one contributor, then this is likely a stale cache or an indexing issue rather than repository metadata you can edit yourself. Repository owners can't manually remove an entry from the Contributors section. If the incorrect contributor persists after GitHub has had time to refresh its indexes, it's worth reporting as a GitHub bug with: - the repository URL, - the output of the /contributors API, - evidence that no commits are attributed to the reported user, - and screenshots showing the discrepancy. In short, if the REST API consistently reports only one contributor while the UI shows two, there's nothing in the repository configuration that you can change to remove the extra entry yourself—the inconsistency would need to be resolved by GitHub's backend. — Reply to this email directly, view it on GitHub <#188915?email_source=notifications&email_token=CFKNPN455XDMQBOE52N4SPL5INHMHA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZZGA4DGNJYUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17908358>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CFKNPN7LS6DWE3I2KYDUF435INHMHAVCNFSNUABHKJSXA33TNF2G64TZHMZTAMJVG4ZTGNBUHNCGS43DOVZXG2LPNY5TSNJZG44DSMFBOYBA> . You are receiving this because you commented.Message ID: ***@***.***>