Skip to main content

Steam Stats📶

A GitHub Action and Docker container to generate Steam user stats cards (PNG) for your README using the official Steam Web API and web scraping for Workshop stats.

Badges

Workflow Status

Steam Stats Release CodeQL & Pylint Bandit Codecov MkDocs Deploy Scorecard Security Dependabot Updates Automatic Dependency Submission Dependency Review

Code Quality & Coverage

Pylint codecov Quality Gate Status Maintainability Rating Security Rating Reliability Rating Coverage Code Smells Bugs Vulnerabilities Lines of Code Duplicated Lines (%) Technical Debt

Packaging & Deployment

Docker Image Size (tag) Docker Pulls GitHub Release Python Version from PEP 621 TOML PyPI - Version PyPI - Implementation PyPI - Downloads PyPI - Format PyPI - Status Pepy Total Downloads

Environments

GitHub deployments GitHub deployments

Documentation & Repo

Documentation GitHub repo size

License & Security

GitHub License OpenSSF Scorecard OpenSSF Best Practices

Time Tracking

wakatime

From one Passionate Gamer to Another 🍻

Full Documentation now available: nicconike.github.io/Steam-Stats/

Browse detailed guides on:

  • Getting Started (API Keys, setup, README integration)
  • Usage & Configuration: User Guide
  • Automated Examples & Feature Flags
  • API Reference (developer-level docs)
  • Developer Guide (contributing, testing, local setup)

Found missing info or want to improve these docs? Open a documentation issue or PR!


Prerequisites

  1. Steam Web API Key: API key is important to fetch your account details and for that you will require a key which you can create for your account here
  2. Markdown Comments: Update the markdown file by adding the comments where the Steam Stats will be embedded to. Refer here to learn more.
  3. Steam ID: You can get your 64-bit Steam id (SteamID64 - 17 digit number) by clicking on your profile name in the top right corner in steam desktop client, select "Account Details" and your Steam ID will be displayed directly under your account name
  4. Steam Custom ID: Open the Steam desktop application, click on your profile name in the top right corner. Select View Profile and your custom URL will be displayed in the URL bar. From this url you will know your Steam Custom ID

The Github Actions is set to run on every Monday 12 AM IST (UTC+5:30) which you can modify to your own time as per your liking by updating it in the workflow file

schedule:
        - cron: "30 18 * * 0"

[!IMPORTANT] Please don't forget any of the steps mentioned in the prerequisites else the Github Action will not work. Also, make sure that you have set the country correctly in your Steam Account.

You can refer the Steam Stats Wiki if you have any questions related to any of the steps mentioned in Prerequisites.


Samples (From my Steam Account)

Example for Steam User Stats

Steam Summary Recently Played Games

Example for Steam Workshop Stats

Steam Workshop Stats


Update README

  1. Add below comment in your markdown file for Steam User Stats
    <!-- Steam-Stats start -->
    <!-- Steam-Stats end -->
    
  2. Add below comment for Steam Workshop Stats (Optional)
    <!-- Steam-Workshop start -->
    <!-- Steam-Workshop end -->
    
  3. Don't forget to add these comments in your readme file or wherever you want to display your steam stats, because without the comments the readme will not get updated

[!CAUTION] The Steam-Stats marker should be placed before the Steam-Workshop markers if you are using both.


Features

  1. Steam Player Summary (Note: Steam Web API doesn't support Web Sockets, so the profile status cannot be updated in real time.)
  2. Recently Played Games from Steam in the Last 2 Weeks
  3. Steam Workshop Stats (If Applicable)

Feature Flags

  1. Steam User Stats (Required | Default)
    1. Steam Player Summary
    2. Steam's Recently Played Games in the last 2 weeks
      1. The Graph plot for recently played games is by default implemented in a fixed linear scale but if you want you can update it to be in a logarithmic scale by using this flag in your workflow: LOG_SCALE: True

      2. When LOG_SCALE is False

        Recently Played Games

      3. When LOG_SCALE is True

        Recently Played Games

  2. Steam Workshop Stats (Optional)
    1. Workshop Stats Module can be used by adding this flag in your workflow file in the environment variables: WORKSHOP_STATS: True
    2. This module displays the total number of Unique Visitors, Subscribers and Favorites for your Steam Workshop Items

Setup with Example

After completing the steps mentioned in the Prerequisites, you have to save all the mentioned keys(except markdown comments) like Steam API Key, Steam-ID, Custom-ID as Secrets in your Github repo's settings.

Repo Settings -> Security -> Secrets and Variables -> Actions -> Add in Repository Secrets

If you are new to Github Secrets then you can checkout this official doc here.

Sample Workflow File

steam-stats.yml

name: Steam Stats

on:
  push:
    branches: master
    schedule:
      # Runs every Monday at 12AM IST (UTC+5:30)
      - cron: "30 18 * * 0"
    workflow_dispatch:

jobs:
  steam-stats:
    name: Steam Stats
    runs-on: ubuntu-latest
    steps:
      - uses: nicconike/steam-stats@master
        with:
          STEAM_API_KEY: ${{ secrets.STEAM_API_KEY }} # Created Steam API key env var
          STEAM_ID: ${{ vars.STEAM_ID }} # Steam ID env var
          STEAM_CUSTOM_ID: ${{ vars.STEAM_CUSTOM_ID }} # Custom ID env var
          WORKSHOP_STATS: True # Optional
          LOG_SCALE: True # Optional

Checkout this real time usage example in a github repo from here and also the github actions workflow file.


Contributions

Star⭐ and Fork🍴 the Repo to start with your feature request(or bug) and experiment with the project to implement whatever Idea you might have and sent the Pull Request through 🤙

Please refer Contributing.md to get to know how to contribute to this project. And thank you for considering to contribute.


Credits


Support💙

If you are using this project and are really happy with it, then there are few ways to support me so that I can keep doing what I like doing:

  • Credit in your readme where you use this action
  • Drop a follow!😁
  • Starring and Sharing the project
  • Donations through GitHub Sponsers or whichever platform you like. So, that I can create more projects like these and play more games🎮🎧

Thanks!🫡


Created with 🐍 & ❤️ by Nicco

Metadata

Release files for Steam-Stats 1.4.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for Steam-Stats 1.4.0
File Size Uploaded
steam_stats-1.4.0.tar.gz 29.1 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for Steam-Stats 1.4.0
File Interpreter ABI Platform
steam_stats-1.4.0-py3-none-any.whl Python 3 none any Details

Total release size: 47.3 kB

Release files / steam_stats-1.4.0.tar.gz

Download URL steam_stats-1.4.0.tar.gz
Size 29.1 kB
Tags Source
SHA-256 checksum
How to use checksums
5f0d1b7061df58486dabac3e35191d08c6b0aad53316945393beefea2a67efc2
BLAKE2b-256 checksum
How to use checksums
7b27705e5775b44cf6e2eea8881c5ffb8ccf1bdedbe70fb3b1a4dfce706d8ffc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 27, 2025.

Transparency log

Release files / steam_stats-1.4.0-py3-none-any.whl

Download URL steam_stats-1.4.0-py3-none-any.whl
Size 18.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a8b36de3f290915c6d03e0db8e7fa7673715601e6a924fe5d5a85f5eb07e1d4b
BLAKE2b-256 checksum
How to use checksums
785779e69ad845140815965c32c65224a5b2b2c09e432debb3feda956f3ffed0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 27, 2025.

Transparency log

Release history Release notifications | RSS feed

This release

1.4.0 This release

2 release files

1.3.2

2 release files

1.3.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page