Source code

1. What source-available means

An extension that reads Steam profiles should be readable itself. That is the whole reason the code is published: so that anyone who is about to install it can check what it does, what it sends, and where. Pulse is not open source, and the difference is deliberate. Reading and auditing are welcome. Copying, republishing and building something else out of it are not. The full licence is at the bottom of this page.

2. Read the code that is actually running

These are the store builds themselves, not a copy prepared for show. Each file is byte for byte the archive uploaded to the store, so the SHA-256 below is something you can verify rather than take on faith.

There is nothing to build and nothing to compile. Unzip the archive and open the files in any text editor: content.js is everything that happens on a Steam profile, background.js is every network request the extension can make, and manifest.json lists the permissions it asks for. If you want to check that your installed copy matches, Chrome keeps it under chrome://extensions with Developer mode on, and its files are readable on disk.

Two things worth reading first, because they are the ones people ask about: the extension holds one permission beyond the hosts it talks to, storage, used for your own settings, and it contains no analytics, no telemetry and no identifiers. The privacy policy says the same thing in prose; the code is where you confirm it.

3. Where the repository is

The code lives in a Git repository hosted on GitHub. Since 4 August 2026 that account is under review by GitHub and its public pages return a 404 to anyone who is not signed in as the author. Nothing was deleted: the repository, its history and its releases are intact, and the review is being sorted out with GitHub support.

The cause, as far as it can be reconstructed, is a scheduled job that used to run there and refresh a price list for the inventory value badge. That job did not belong on GitHub, it now runs elsewhere, and the extension no longer fetches anything from GitHub at all. When public access is restored, the link to the repository comes back on this page.

Meanwhile the archives above are the honest answer to "let me see the code first", and they are the same bytes the stores review and ship.

4. Licence

This is the licence the code is published under, in full.

Pulse Source-Available License
Copyright (c) 2026 ahake. All rights reserved.

The source code in this repository is published publicly for transparency
and security auditing. It is NOT open source.

PERMITTED
  - Viewing and reading the source code (e.g. to audit what the extension
    does before installing it).
  - Installing and using the official Pulse extension published by the
    author (for example via the Chrome Web Store), free of charge.

NOT PERMITTED without the author's prior written permission
  - Redistributing, publishing, mirroring, or sublicensing the code or any
    part of it.
  - Modifying it or creating derivative works.
  - Using the code, in whole or in part, in any other software, product,
    or service, commercial or non-commercial.
  - Selling the code or any derivative of it.

This license applies to the code as of the date of this file and going
forward. The software is provided "AS IS", without warranty of any kind,
express or implied. The author is not liable for any claim, damages, or
other liability arising from the software or its use.

For licensing or permission requests, ask on Discord.

5. Found something

If you read the code and something looks wrong, say so on Discord. That is the fastest way to reach the person who wrote it, and while the repository is not public it is also the only way. Security issues are read first and answered first.