A repository link still opening does not mean the person you remember still owns that username or account. GitHub normally redirects repository links after a username change, while links to the old profile return 404 instead of redirecting. Confirm current ownership by asking for the current public profile link, and treat the redirecting repository alone as inconclusive.
Find public social profile clues with our TraceSeek app.
Why the repository and the profile behave differently
GitHub applies different continuity rules to different kinds of links. When someone changes their username, the old username is freed and links to the previous profile return 404 rather than redirecting automatically. Repository links, by contrast, normally redirect to the renamed account. This explains the odd pairing you see: the repository page still resolves, but the profile you knew no longer exists. The two results come from separate link behaviors, not from one page failing and another succeeding for a shared reason. [GitHub Docs: username changes]
A redirecting repository can be overridden
The redirect is a convenience, not a guarantee of identity. GitHub notes that a new owner of the freed old username can create the same repository name, which overrides the redirect. So a repository link opening at a familiar address is not proof that the original owner is still behind it. Profile, repository and gist links each follow their own continuity rules, and none of them settles who currently controls an account. [GitHub Docs: username changes]
Separating observation from inference
What you can actually observe is narrow: whether the profile address returns 404, whether a repository link resolves and where it lands, and the date you checked. What you cannot observe from those facts is why the username changed, who controls the account now, or what the person's intentions are. Keep the observation and the inference apart in your notes. A 404 is a page state, not a statement about honesty, activity or relationship.
- Record the exact profile address and the 404, with the date.
- Note where the repository link resolves, without assuming the owner.
- Write any guessed explanation in a separate column marked as unverified.
Asking for the current public profile
The reliable next step is a direct, low-pressure request for the current public profile link. Ask only for what the person is willing to share publicly, and accept silence or a partial answer as a boundary rather than a signal. Do not treat a stale display, a redirect or a matching name as proof of identity or intent. If you are using a mobile app, remember that some views can keep showing an earlier username until you sign out and back in, which is another display artifact rather than evidence. [GitHub Docs: username changes]
- Ask: could you share your current public GitHub profile link?
- Do not ask for account access or private credentials.
- If no link is offered, record unavailable and stop there.
Comparing the two outcomes
The table below keeps the observation, its limit and the practical next step in separate columns so that a page state is not mistaken for a conclusion about a person.
| observation | limit | next step |
|---|---|---|
| Old profile address returns 404 | Shows the username is no longer linked to a profile; does not explain why | Ask for the current public profile link |
| Repository link resolves | Normally reflects a rename redirect; can be overridden by a new owner of the old username | Do not treat it as proof of current ownership |
| Mobile view shows an earlier username | Can persist until sign-out; a display artifact | Rely on the current profile the person shares |
When the documented behavior is unavailable
If the profile or repository page cannot be reached at all, or GitHub's current documentation no longer matches what you see, record the result as unavailable and stop at the access boundary. Do not attempt to work around it with private-account access, similarity matching or covert tracking. Use GitHub's official current help pages only for general behavior, and otherwise wait for a voluntary current link from the person concerned. [GitHub Docs: username changes]
A couple more questions
If the repository opens, does that mean the same person still owns it?
No. Repository links normally redirect after a username change, and a new owner of the freed old username can create the same repository name and override that redirect. The opening page does not establish current ownership.
Why does the profile return 404 while the repository works?
GitHub frees the old username on a change, and links to the previous profile return 404 instead of redirecting automatically, while repository links normally redirect. The two link types follow different rules.
What is the most useful thing to ask for?
Ask for the person's current public profile link and nothing private. If they decline or stay silent, record that as a boundary and stop rather than inferring ownership from the repository link.
Sources & editorial notes
Official references checked on October 23, 2026. Checklists, comparison tables and example wording are DateClues editorial tools, not official tests or validated risk scores.
General information. No guide or tool can certify a person’s identity, intentions or safety. Read our editorial standards.