Modern IT projects are often carried out in teams, necessitating a fair evaluation of each member’s contribution. This is relevant both in academic settings, where instructors aim to assess the engagement of students working on programming projects accurately, and in software companies that need to distribute bonuses or decide about promotions fairly. Many methods for contribution assessment exist, but they are often either too simple or too complex and have low performance. There remains a need for a quick, balanced solution, particularly for short-lived projects developed under time pressure or for long-lived projects created by junior programmers, where quality is achieved by applying specific tools or checking by more experienced staff. This paper presents a new method for measuring team members’ contributions that addresses this gap. In addition to code complexity, code uniqueness is considered a contributing factor. The method has been implemented in a tool that analyzes Java source code controlled by the Git version control system. The method’s effectiveness has been tested on real data, and the results have been compared with other simpler methods and a selected method from the literature. Data analysis confirmed the limited usefulness of the former solutions and demonstrated results comparable to those of the latter.