How to show open-source work on a freelance CV
Point to a specific contribution, explain what you changed and distinguish a merged contribution from one still under review.
Choose contributions a reader can inspect
Link to a repository, pull request, issue or release that shows your actual contribution. Prefer a specific change over a profile link with no context, and make sure the project is public and safe to share.
A contribution can be documentation, testing, accessibility work, bug fixing or code. Name the task and the part you handled; do not imply that you created or maintain the whole project if you contributed to only one part.
Report the status accurately
A pull request that is still open is not the same as a change accepted into the project. Use labels such as “proposed”, “under review” or “merged” only when the repository record supports them.
GitHub’s contributor guidance recommends reading each project’s contribution rules and review process. Those details matter on a CV too: they help explain how your change was submitted and what the maintainers accepted.
Check the licence and remove sensitive details
Review the repository licence and project guidance before copying code, screenshots or other material into a portfolio. A public repository is not automatically permission to reuse every asset in any way; the licence sets important terms.
Do not expose credentials, private issue content or client code in a public link. If you cannot share the repository, describe the contribution at a high level and say that the supporting material is private.
UK considerations
This is general CV guidance. Follow the UK employer, client or application system’s instructions, especially when it requests a specific format or set of details.
Keep code contributions beside your other project evidence. Create your CV and tailor the examples to a technical brief.