Create a repository with the same name as your GitHub username if it's not already done.

The README.md of it will be displayed on your user profile :

From the Developer settings of your account settings, select Personal access tokens to create a new token.

No additional scopes are needed, unless you want to include your private repositories metrics.

With a scope-less token, you can still display private contributions by enabling Include private contributions on my profile in your account settings :

Some plugins also require additional scopes, which is indicated in their respective documentation. In case your token does not have the required scope (and plugins_errors_fatal is not enabled), it will be directly notified in the plugin render like below :

Go to the Settings of your personal repository to create a new secret and paste your freshly generated GitHub token there.

Create a new workflow from the Actions tab of your personal repository and paste the following :

name: Metrics
on:
  # Schedule updates
  schedule: [{cron: "0 * * * *"}]
  push: {branches: "master"}
jobs:
  github-metrics:
    runs-on: ubuntu-latest
    steps:
      # See action.yml for all options
      - uses: lowlighter/metrics@latest
        with:
          # Your GitHub token
          token: ${{ secrets.METRICS_TOKEN }}
          # GITHUB_TOKEN is a special auto-generated token restricted to current repository, which is used to push files in it
          committer_token: ${{ secrets.GITHUB_TOKEN }}

See all supported options in action.yml.

When using a token with additional permissions, it is advised to fork this repository to minimize security risks :

      - uses: my-github-username/metrics@latest

In this case, consider watching new releases of this repository to stay up-to-date and enjoy latest features !

It is possible to use @master instead of @latest to use new features before their official release. Breaking changes may occur occasionally on @master, which could result in your metrics not being generated temporarily.

A new metrics image will be generated and committed to your repository on each run.

Check out this workflow file which generates metrics daily.

Note that most of steps presented there are illustrative examples for this readme and are actually not needed to generate your own metrics.

Edit your repository readme and add your metrics image :

![Metrics](https://github.com/my-github-user/my-github-user/blob/master/github-metrics.svg)

Since GitHub API has rate limitations, the shared instance has a few limitations :

• Images are cached for 1 hour
  • Your generated metrics won't be updated during this amount of time when queried
• A rate limiter is enabled, although it won't affect already cached users metrics
• Plugins which consume additional requests, or require additional token scopes are disabled

If you're appreciating this project, consider using it as a GitHub Action instead.

You will need a server where you can setup and run a NodeJS application.

From the Developer settings of your account settings, select Personal access tokens to create a new token.

No additional scopes are needed.

Connect to server and ensure NodeJS is installed (see tested version in workflow).

Run the following commands to clone this repository, install dependencies and copy configuration example file :

git clone https://github.com/lowlighter/metrics.git
cd metrics/
npm install --only=prod
cp settings.example.json settings.json

Edit settings.json to configure your instance.

{
  //See settings.example.json for all options
  //GitHub API token
    "token":"****************************************"
}

See all supported options in settings.example.json.

Run the following command to start your instance once you've finished configuring it :

npm start

From your browser, you should be able to access your web instance on the port you provided in setting.json.

Edit your repository readme and add your metrics image from your server domain :

![Metrics](https://my-personal-domain.com/my-github-user)

To ensure that your instance will be restarted in case of reboots or crashs, you should setup it as a service. This is described below for linux-like systems which supports systemd.

Create a new service file /etc/systemd/system/github_metrics.service and paste the following after editing paths inside :

[Unit]
Description=Metrics
After=network-online.target
Wants=network-online.target

[Service]
Type=simple
WorkingDirectory=/path/to/metrics
ExecStart=/usr/bin/node /path/to/metrics/index.mjs

[Install]
WantedBy=multi-user.target

Reload services, enable it, start it and check if it is up and running :

systemctl daemon-reload
systemctl enable github_metrics
systemctl start github_metrics
systemctl status github_metrics

The following errors code can be encountered on a web instance :

Generated metrics images from a web instance can be configured through url parameters.

Base content is enabled by default, but passing ?base=0 will disable all base content. You can choose to selectively enable or disable a specific <section> with ?base.<section>=<1|0>.

For example, to opt-out from activity, community and metadata, append ?base.activity=0&base.community=0&base.metadata=0 to your metrics url.

Plugins are disabled by default, but passing ?<plugin>=1 will enable a specific <plugin>. Plugin options can be passed with ?<plugin>.<option>=<value>.

For example, to enable music plugin and configure music plugin, you could append the following to your metrics url : ?music=1&music.provider=spotify&music.mode=recent&music.limit=4.

Basically, most of action.yml options can actually be used by web instance, with plugin_ prefix dropped, and . instead of _.

To use repository template, you'll need to provide a repository name in query option.

If repository owner is different from token owner, use user option to specify it.

Add the following to your workflow :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    template: repository
    user: "repository-owner"
    query: '{"repo":"repository-name"}'

By default, generated metrics contains the following sections :

• header, which usually contains your username, your two-week commits calendars and a few additional data
• activity, which contains your recent activity (commits, pull requests, issues, etc.)
• community, which contains your community stats (following, sponsors, organizations, etc.)
• repositories, which contains your repositories stats (license, forks, stars, etc.)
• metadata, which contains informations about generated metrics

You can explicitely opt-out from them, which can be useful if you only want to keep a few sections or to use a plugin as standalone.

For example, to keep only header and repositories sections, add the following to your workflow :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    base: "header, repositories" # opt-out from "activity", "community" and "metadata"

By default, the community section only counts public organizations memberships. You can change your membership visibility in the People tab of your organization :

To include private organizations memberships, you'll need to add the read:org scope to your personal token.

Although not mandatory, you can generate an API key for PageSpeed API here to avoid 429 HTTP errors.

The website attached to the GitHub profile will be the one to be audited. Expect 10 to 30 seconds to generate the results.

Add the following to your workflow :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    plugin_pagespeed: yes
    plugin_pagespeed_token: ${{ secrets.PAGESPEED_TOKEN }}

You can display a detailed report along with scores :

See performance scoring and score calculator for more informations about how PageSpeed compute these statistics.

Add the following to your workflow instead :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    plugin_pagespeed: yes
    plugin_pagespeed_detailed: yes
    plugin_pagespeed_token: ${{ secrets.PAGESPEED_TOKEN }}

You can also display the screenshot taken by PageSpeed API :

Add the following to your workflow :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    plugin_pagespeed_screenshot: yes

It is possible to audit a different website from the one linked to your GitHub account by using plugin_pagespeed_url option.

Add the following to your workflow :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    plugin_pagespeed_url: https://********

It will consume two additional GitHub requests.

Add the following to your workflow :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    plugin_isocalendar: yes

Use the following instead to display a full-year instead :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    plugin_isocalendar: yes
    plugin_isocalendar_duration: full-year

Select a music provider below for instructions.

<iframe allow="" frameborder="" height="" style="" sandbox="" src="https://embed.music.apple.com/**/playlist/********"></iframe>

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    plugin_music: yes
    plugin_music_provider: apple
    plugin_music_mode: playlist
    plugin_music_playlist: https://******** # Extracted source link
    plugin_music_limit: 4 # Set the number of tracks you want to display

<iframe src="https://open.spotify.com/embed/playlist/********" width="" height="" frameborder="0" allowtransparency="" allow=""></iframe>

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    plugin_music: yes
    plugin_music_provider: spotify
    plugin_music_mode: playlist
    plugin_music_playlist: https://******** # Extracted source link
    plugin_music_limit: 4

Select a music provider below for additional instructions.

https://accounts.spotify.com/authorize?client_id=********&response_type=code&scope=user-read-recently-played&redirect_uri=https%3A%2F%2Flocalhost

(async () => {
  console.log(await (await fetch("https://accounts.spotify.com/api/token", {
    method:"POST",
    headers:{"Content-Type":"application/x-www-form-urlencoded"},
    body:new URLSearchParams({
      grant_type:"authorization_code",
      redirect_uri:"https://localhost",
      client_id:"********",
      client_secret:"********",
      code:"********",
    })
  })).json())
})()

{
  "access_token":"********",
  "expires_in": 3600,
  "scope":"user-read-recently-played",
  "token_type":"Bearer",
  "refresh_token":"********"
}

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    plugin_music: yes
    plugin_music_provider: spotify
    plugin_music_token: "${{ secrets.SPOTIFY_CLIENT_ID }}, ${{ secrets.SPOTIFY_CLIENT_SECRET }}, ${{ secrets.SPOTIFY_REFRESH_TOKEN }}"
    plugin_music_mode: recent
    plugin_music_limit: 4

Add the following to your workflow :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    plugin_languages: yes
    plugin_languages_ignored: "" # List of comma separated languages to ignore
    plugin_languages_skipped: "" # List of comma separated repositories to skip

Add the following to your workflow :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    plugin_followup: yes

This uses puppeteer to navigate through your starred topics page.

You can choose to display and order topics by :

• Most stars
• Recent activity
• Recently starred by you
• randomly

Add the following to your workflow :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    plugin_topics: yes
    plugin_topics_sort: stars
    plugin_topics_limit: 15

It is possible to display starred topics as Mastered and known technologies instead :

Add the following to your workflow instead :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    plugin_topics: yes
    plugin_topics_mode: mastered
    plugin_topics_limit: 0

It will consume an additional GitHub request.

Because of GitHub REST API limitation, provided token requires public_repo scope to access projects informations.

Add the following to your workflow :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    plugin_projects: yes
    plugin_projects_limit: 4

Note that by default, profile projects have progress tracking disabled. To enable it, open the ≡ Menu and edit the project to opt-in to Track project progress (it can be a bit confusing since it's actually not in the project settings).

It is possible to display projects related to repositories along with personal projects.

To do so, open your repository project and retrieve the last url endpoint, in the format :user/:repository/projects/:project_id (for example, lowlighter/metrics/projects/1) and add it in the plugin_projects_repositories option. Enable Track project progress in the project settings to display a progress bar in generated metrics.

Add the following to your workflow :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    plugin_projects: yes
    plugin_projects_repositories: :user/:repository1/projects/:project_id, :user/:repository2/projects/:project_id, ...

It will consume an additional GitHub request per repository.

Add the following to your workflow :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    plugin_lines: yes

It will consume an additional GitHub request per repository.

Because of GitHub REST API limitation, provided token requires full repo scope to access traffic informations.

Add the following to your workflow :

- uses: lowlighter/metrics@latest
  with:
    # Token with "repo" scope
    token: ${{ secrets.METRICS_TOKEN }}
    # ... other options
    plugin_traffic: yes

Add the following to your workflow :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    plugin_tweets: yes
    plugin_tweets_token: ${{ secrets.TWITTER_TOKEN }}

It is possible to use a different twitter username from the one linked to your GitHub account by using plugin_tweets_user option.

Add the following to your workflow :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    plugin_tweets_user: ********

Supported sources are :

• dev.to

Add the following to your workflow :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    plugin_posts: yes
    plugin_posts_source: ********

It is possible to use a different username from your GitHub account by using plugin_posts_user option.

Add the following to your workflow :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    plugin_posts_user: ********

It will consume an additional GitHub request per event fetched.

Because of GitHub REST API limitation, provided token requires full repo scope to access private events. Events that cannot be fetched will be ignored so it is still possible to use this plugin with a scope-less token.

A high value must be provided for plugin_habits_from in order for this section to be accurate, although it'll increase the number of GitHub requests sent. If you're using GitHub Api in other projects, you could reach the rate limit.

These facts are generated from your recent coding activity. The indent style is deduced from the diffs of your recent commits.

Add the following to your workflow :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    plugin_habits: yes
    plugin_habits_from: 200
    plugin_habits_days: 14

You can display charts in this section :

These charts are generated from your recent coding activity. Languages metrics are computed with github/linguist from the diffs of your recent commits.

Add the following to your workflow instead :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    plugin_habits: yes
    plugin_habits_from: 200
    plugin_habits_days: 14
    plugin_habits_facts: yes
    plugin_habits_charts: yes

By default, dates are based on the Greenwich meridian (England time). In order to these metrics to be accurate, be sure to set your timezone (see here for a list of supported timezones) :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    config_timezone: Europe/Paris

It will consume an additional GitHub request per gist fetched.

Add the following to your workflow :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    plugin_gists: yes

It will consume an additional GitHub request.

Add the following to your workflow :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    plugin_stars: yes
    plugin_stars_limit: 4

It will consume additional GitHub requests per repository per set of 100 stargazers.

Add the following to your workflow :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    plugin_stargazers: yes

By default, dates are based on the Greenwich meridian (England time).

It is possible to set set your timezone (see here for a list of supported timezones) by adding the following to your workflow :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    config_timezone: Europe/Paris

Generated metrics height is computed after being rendered through an headless browser. As rendering can depends on used fonts and operating system, it may render as cropped or with additional blank space at the bottom.

It is possible to adjust the padding by adding the following to your workflow :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    config_padding: 6%

Both positive and negative values are accepted, but you must specify a percentage.

It is possible to convert output from SVG to PNG or JPEG images by adding the following to your workflow :

- uses: lowlighter/metrics@latest
  with:
    # ... other options
    config_output: png

Note that png does not support animations while jpeg does not support both animations and transparency.