Skip to main content
Activity scores indicate the level of activity associated with a repository. Activity information is based on metadata gathered from a code hosting and version control system such as GitHub. Higher levels of activity can mean that the repository is well maintained and will continue to be in the future. The following factors have a positive contribution to the activity score:
  • Activity from corporate affiliated accounts indicates that the project can have reliable backing and support.
  • Activity from reputable accounts indicates that the repository is well-maintained. An account is considered reputable if it participates in multiple open-source projects and has a high rating on a source control system such as GitHub.
  • Consistent and continuous commit activity over longer periods of time indicates that the project is active.
  • The repository has frequent releases, indicating a commitment to maintaining and supporting the codebase.
  • Activity in the form of comments on issues shows there is engagement in the project.
  • A high ratio of issues opened by external contributors indicates that the project is active.
  • More issues being closed than opened indicates that the project is active.
  • The repository keeps releasing updates to earlier release trains. This is a sign of a commitment to maintaining and supporting the users of the project.
  • When a repository belongs to an organization, there is a lower risk of it getting abandoned in the future.
  • Recent issue and commit activity means the project is active.
  • Configuring topics is an indication that the repository is well-maintained.
The following factors have a negative contribution to the activity score:
  • Archived repositories are not active and have a low score.
  • A high ratio of rejected pull requests indicates that the project may not be actively developed.
  • The lack of recent issue activity may indicate that the project is not actively used.
  • Significantly more pull requests being submitted than merged indicates that the project may not be maintained.
  • The repository does not have any recent releases. This could mean that it is not actively maintained.
  • When a repository is personal, there is a higher risk of it getting abandoned in the future.
  • If the majority of the repository’s activity comes from a tiny number of accounts, the project could be at risk if these accounts cannot continue their contributions.