Code Stats

Elevate your performance analysis beyond the contributors page.
Dive in and transform your team workflows!

Report a bug · Request a feature · Meet & say thanks

Built using

       

       

Support

         

About The Project

Have you ever visited the Contributors page of a GitHub project? If not, take a look – the data presented there can be very insightful! You can view data like code frequency, amount of contribution from authors, liveliness of the project.

However, the GitHub page leaves a lot to be desired. For example, have you ever wondered about your project's Cycle Time? Are you blocking each other, or things are moving smoothly through your development pipeline? Have you wondered about the evolution of this metric over time? This metric (and many more) can be computed using the raw contribution data available in code repositories and at GitHub.

To make time theft more visible, Code Stats aims to provide an alternative interface to GitHub's insights pages. Take a look at some of the examples below.

Getting Started

The project is build with Kotlin/Native (supporting multi-platform native binaries). However, due to complications with the automation pipelines and some issues with Kotlin's native compiler (Konan), native binary outputs are temporarily disabled.

For the time being, you can still use the packages available for the Java Virtual Machine (JVM).

Prerequisites for running

In order to not get blocked by GitHub for "too many requests" to their APIs, it is mandatory to provide an authentication token created inside of GitHub.

This is done by setting an environment variable called GITHUB_TOKEN.

JVM

To run the JVM flavor, you need:

• Java installed and available on the Path; OpenJDK is fine.

Prerequisites for building

JVM

To build the JVM flavor, you need:

• Java installed and available on the Path; OpenJDK is fine.

How to run

JVM

Simply download the latest version from Releases and run it using Java:

$ java -jar codestats.jar --help

How to build

JVM

Clone the project's repository to your local machine. Then, from the project's root directory run:

$ ./gradlew shadowJar

Your output should be exactly the same as the latest Release, and stored in build/libs/codestats.jar.

Usage

For readability purposes, we use codestats instead of java -jar codestats.jar even when running the JVM flavor.

Help

The simplest usage is help (-h, --help):

$ codestats --help

Launch modes

There are several modes that Code Stats can run in.

1. Fetch – fetches fresh contribution data and stores it locally for analysis
2. Print – calculates and prints all the code stats (metrics) to stdout
3. Report – prints a short report on what data is available locally
4. Serve – launches a backend server locally, and prints the access URL for the web UI
5. Purge – deletes all locally stored data

To choose a mode, simply add a --mode modifier:

$ codestats --mode=serve

Analysis scope

The basic configuration for the runner comes from a YAML file. This file can either be next to the codestats binary, or pointed to using environment variables and modifiers.

Here's an example:

owner: nasa                 # GitHub repository owner
startDate: 2023-01-01       # no data before this date
endDate: 2023-03-15         # no data after this date

teams: # all teams you'd like to inspect
  - title: Flight Team      # GitHub user-friendly team name
    name: nasa-flight       # GitHub team ID
    codeRepositories: # where the code lives
      - openmct
      - HyperCP
      - cmr-stac
      - cFS
    discussionRepositories: # where discussions live
      - cFS

You can also supply an external configuration file using the --config-file modifier:

$ codestats --config-file=~/.configs/code-stats.yaml

You can also refer to the sample configuration file.

Environment configuration

There are even more configuration options you can use as environment variables:

• GITHUB_TOKEN – the (mandatory) authentication token for communicating with GitHub
• GITHUB_URL – a REST GitHub Enterprise URL; default is api.github.com
• GITHUB_GRAPHQL_URL – a GraphQL GitHub Enterprise URL; default is api.github.com/graphql
• GITHUB_PAGING_LIMIT – how many items to fetch per page (when paging); default is 100
• GITHUB_VERBOSE – whether to print verbose update in the console; default is false
• GITHUB_PRINT_PROGRESS – whether to print progress updates for GitHub API fetch; default is true
• GITHUB_RATE_LIMIT_DELAY_MILLIS – a rate-limiting delay for requests to GitHub; default is 2.1s
• DATABASE_PATH – which local database to use (file path); default is code-stats.db
• STATS_PORT_API – on which port to launch the server for the web UI; default is 8080

The executable will automatically read these variables and apply them before running.

Contributing and contact

Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated. Don't forget to give the project a star! ❤️

To read the contributions guideline, go to CONTRIBUTING.

License

Distributed under the Non-Toxic GNU GPL v3 License. See LICENSE for more information about this particular license.