Semmle Limited

Microsoft Technology Licensing, LLC

Robin Neatherway

Arthur Baars

Sebastian Bauersfeld

Methods, systems, and apparatus, including computer programs encoded on computer storage media, for attributing violation introductions and removals. One of the methods includes receiving a request to compute a number of violation introductions attributable to a particular developer entity in a plurality of ancestor snapshots of an original snapshot in a revision graph of a code base. A respective match set for each of a plurality of violations occurring in the plurality of ancestor snapshots of the original snapshot are computed, wherein each match set for a particular violation in a particular snapshot includes any transitively matching violations in the ancestor snapshots of the particular snapshot that transitively match the particular violation. A count of unique match sets having at least one violation that was introduced by the particular developer entity is computed. The number of unique match sets is provided in response to the request.

Violation match sets

Methods, systems, and apparatus, including computer programs encoded on computer storage media, for linearizing the commit history of a code base. One of the methods includes receiving a request to attribute source code contributions to a particular snapshot in a project having a revision graph with multiple branches. Source code contributions occurring in each non-merge commit on a single path through the revision graph are attributed to a responsible developer entity of the non-merge commit. Each merge commit is processed on the single path including identifying contributions introduced by the merge commit, identifying one or more respective responsible developer entities for the contributions occurring in the one or more feature branch snapshots from one or more feature branches, and attributing source code contributions occurring in the one or more feature branch snapshots from the one or more feature branches to the identified one or more respective responsible developer entities.

Commit history linearization

Methods, systems, and apparatus, including computer programs encoded on computer storage media, for generating a commit graph for a software project maintained in a version control system having a directory-based branching structure. One of the methods includes receiving data representing a commit history of a software project maintained in a version control system having a directory-based branching system in which each branch of the commit history has a respective branch directory and each revision is identified by a branch path and a revision number. The commit history is traced backward in time from a starting commit of a branch to identify an initial commit in which a branch directory for the branch was created. The commit history is then processed forward in time from the initial commit to generate a tree-structured commit graph.

Commit graph generation

Methods, systems, and apparatus, including computer programs encoded on computer storage media, for attributing external dependencies in a software project. One of the methods includes receiving data representing a child snapshot and a parent snapshot in a revision graph of a software project. One or more pairs of matching source code files is identified, and for each pair having a first file and second file, a first count of external dependencies on an external dependency target in the first file and a second count of external dependencies on the external dependency target in the second file are computed. If the first count is different than the second count, an introduction or a removal of one or more external dependencies on the external dependency target in the second file of the pair of matching source code files is attributed to an author of the child snapshot.

Growing community of inventors

Oxford, United Kingdom

Robin Neatherway