How to tell if a GitHub repo is really theirs
Anyone can fork a repository, copy it, or paste a link to someone else's work. A link to a repo tells you the code exists, not that this person wrote it.
Look at who committed
Open the commit history and see whose account made the changes, how many, and over what period. One person with a steady history is a different story from a single large commit on a single day.
Check whether it is a fork
A fork is a copy of someone else's project. Forks are fine when the person has added to them, but the contribution is the difference from the original, not the repository itself.
Read the code, not the README
A README is easy to write. Look at the structure, tests, how problems are handled, and whether the choices make sense for the problem. Boilerplate and templates look busy and say little.
What Nexr checks
Nexr imports code projects through the person's own connected GitHub account. It reads the commit history to work out whether they are the primary builder or a contributor, detects the stack from the package files, and filters out empty repositories, single-file bookmarks and pure templates.
Questions
Does a GitHub link prove someone wrote the code?
No. A link only shows the repository exists. Commit history, whether it is a fork, and the person's role in it are what show authorship.
How does Nexr decide if someone built a repository?
Through the connected GitHub account and its commit and contribution history, which sets whether they are shown as the primary builder or a contributor.
Nexr is the pre-verified portfolio platform for digital creatives. See how verification works.