npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

inv2csv

v1.0.2

Published

Export your full CS2 inventory (incl. storage units) to a CSV of market_hash_name, quantity and trade-lock date

Readme

inv2csv

Export your full CS2 inventory — including storage-unit contents — to inventory.csv (market_hash_name,quantity).

Requirements

Node.js 18+ and the Steam mobile app (for QR login). CS2 must not be running on the account while this runs.

Usage

npx inv2csv

(or from a checkout: npm install && node index.js)

Scan the QR code with the Steam mobile app, approve, done — inventory.csv appears in the current directory. The item schema is fetched fresh on every run, so names are always current.

Columns: market_hash_name,quantity,tradable_after. Rows are grouped by name and trade-lock date, so the same item acquired at different times appears on separate rows. tradable_after is the date the item's trade lock expired (or expires); for items acquired by trade or market purchase that is acquisition date + 7 days, so it tells you roughly how long the item has been in the inventory. Empty = the item never had a trade lock (e.g. unboxed drops), so its age can't be derived.

Privacy

No login data is ever stored: no password is typed, and the login token lives only in process memory — every run is a fresh QR scan. Nothing is written to disk except inventory.csv.

Out of scope

Password/2FA login, prices, per-storage-unit breakdown, float/sticker details.