Development Activity Metric

Definition

Development Activity metric shows the 'pure' development activity. It excludes events that are not related to development like:

• Comments on issues;
• Issues created and closed;
• Creating of forks;
• Comments on commits;
• People following an issue;
• Downloading releases;
• Watching a repository;
• Project management events;
• Other.

This allows for better comparison between projects that use GitHub for issue tracking and projects that use an external tool (like Notion) for issue tracking. If such events are not excluded then some projects have inflated activity just by discussing what they are going to build without actually building it. Inactive projects might have non-zero activity caused by people creating issues and asking the team to fix something, without any actual work being done.

There are 3 development activity metrics available:

• dev_activity - 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_1d - Precomputed daily 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 - Precomputed for each ecosystem. An ecosystem dev activity is defined as the sum of the dev activities of all assets that belong to it. For example the ethereum ecosystem contains all the projects that build on the Ethereum blockchain or contribute to the blockchain in any other way.

Access

Free Access

Data Type

Timeseries Data

Change Metrics

Change Metrics

Frequency

• dev_activity - Five-Minute Intervals
• dev_activity_1d - Daily Intervals
• ecosystem_dev_activity - Daily Intervals

Latency

Development Activity Data Latency

Available Assets

• dev_activity available assets
• dev_activity_1d available assets
• ecosystem_dev_activity available ecosystems

SanAPI

Fetch the dev activity for an asset:

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

Run in Explorer

Fetch the dev_activity for an arbitrary organization. You need to provide only the organization name to the parameter, not the whole URL. Github links look like this: https://github.com/<organization>/<repository>.

1
2
3
4
5
6
7
8
9
10
11
12
13
{
  getMetric(metric: "dev_activity") {
    timeseriesData(
      selector: {organization: "google"}
      from: "2020-01-13T00:00:00Z"
      to: "2020-01-18T00:00:00Z"
      interval: "1d"
    ) {
      datetime
      value
    }
  }
}

Run in Explorer

Fetch the ecosystem_dev_activity, combining the dev activities of all assets that contribute to that ecosystem:

1
2
3
4
5
6
7
8
9
10
11
12
{
  getEcosystems(ecosystems: ["ethereum"]) {
    timeseriesData(
      metric: "ecosystem_dev_activity"
      from: "2024-03-01T00:00:00Z"
      to: "2024-03-10T00:00:00Z"
      interval: "1d") {
        datetime
        value
      }
  }
}

Run in Explorer

To check what assets are part of the ecosystem and what are their github links:

1
2
3
4
5
6
7
8
9
{
  getEcosystems(ecosystems: ["ethereum"]){
    name
    projects{
      slug
      githubLinks
    }
  }
}

Run in Explorer