Github Activity Contributors Count

    Definition

    The Github Activity Contributors Count metrics show the unique number of people (represented as Github accounts) that have contributed to a public Github repository in an organization that is followed.

    There are 3 development activity contributors count metrics available:

    • dev_activity_contributors_count - Computed on-the-fly using the Github data. Because of this the metric can compute data for any asset or just any random Github organization that has public repositories like Google, Facebook, or any other organization.
    • dev_activity_contributors_count_7d - Precomputed weekly metric for each asset that is available on Santiment. This allows the metric to be aggregated when the value is needed for all assets at once.
    • ecosystem_dev_activity_contributors_count_7d - Precomputed for each ecosystem. The metric is defined as the total count of unique contributors that contributed to the github organization of at least one of assets that belong to it.

    Note: The precomputed metrics github_activity_contributors_count_7d and ecosystem_github_activty_contributors_count_7d cannot be aggregated using the SUM aggregation, i.e. you cannot obtain the number of monthly contributors by taking the sum of 4 weekly values. This is because the same contributors may or may not make up the separate values, so the SUM operation can count some contributors multiple times. To achieve monthly contributors, use the github_activity_contributors_count metric with interval: "30d"


    Access

    Free Access


    Measuring Unit

    Number of github accounts


    Data Type

    Timeseries Data


    Frequency


    Latency

    Development Activity Data Latency


    Available Assets


    SanAPI

    Fetch hourly github_activity_contributors_count for an asset:

    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    {
      getMetric(metric: "github_activity_contributors_count") {
        timeseriesData(
          slug: "santiment"
          from: "2020-01-01T00:00:00Z"
          to: "2020-03-01T00:00:00Z"
          interval: "1h"
        ) {
          datetime
          value
        }
      }
    }

    Run inExplorer


    Fetch monthly github_activity_contributors_count for an asset:

    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    {
      getMetric(metric: "github_activity_contributors_count") {
        timeseriesData(
          slug: "santiment"
          from: "2020-01-01T00:00:00Z"
          to: "2020-03-01T00:00:00Z"
          interval: "30d"
        ) {
          datetime
          value
        }
      }
    }

    Run inExplorer


    Fetch the precomputed weekly github_activity_contributors_count_7d for an asset:

    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    {
      getMetric(metric: "github_activity_contributors_count_7d") {
        timeseriesData(
          slug: "santiment"
          from: "2020-01-01T00:00:00Z"
          to: "2020-03-01T00:00:00Z"
          interval: "7d"
        ) {
          datetime
          value
        }
      }
    }

    Run in Explorer


    Because github_activity_contributors_count_7d is precomputed, you can also fetch an aggregated value for many assets at the same time:

    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    {
      allProjects(
        selector: {
          baseProjects: {slugs: ["bitcoin", "ethereum", "santiment", "maker"]}
        }) {
          slug
          contributors: aggregatedTimeseriesData(
            metric: "github_activity_contributors_count_7d"
            from: "utc_now-1d"
            to: "utc_now"
            aggregation: LAST
          )
      }
    }

    Run in Explorer