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

telosforge

v0.2.0

Published

Local-first engineering risk intelligence for a single repository

Readme

telos

Local-first engineering risk intelligence for a single repository.

Before you edit code, telos answers:

  1. What likely breaks if I change this?
  2. Who owns this code today?
  3. What depends on this — transitively?
  4. What changed recently here?
  5. What got riskier this week?
  6. What is fragile / weakly tested?
  7. What files tend to change together with this one?

Install

npm install -g telosforge

Two equivalent commands are exposed: telos (short) and telosforge (full). Either works — pick your preference.

You can also run it without a global install:

npx telosforge init

Quickstart — one command

cd path/to/your/repo
telos init

init is the full bootstrap pipeline. It will:

  1. create .telos/ and a default config.json
  2. open a browser to authenticate (only the first time)
  3. scan the repository — files, imports, ownership, churn, hotspots, risk
  4. sync the snapshot to your dashboard
  5. print the dashboard URL

One command, every step. Idempotent — re-running picks up where you left off.

✓ initialized .telos/
✓ authenticated as [email protected]
▸ graph analysis…
▸ git history…
▸ ownership inference…
▸ risk scoring…
▸ sync to dashboard…
✓ scanned 842 files in 1820ms
  entities  912
  edges     1147
  synced    4317 rows → dashboard

Dashboard:
  https://telosforge.com/dashboard/repos/abc/graph

Done.

Subsequent commands

For repos you've already initialized:

telos scan        # re-scan + sync
telos risk        # ranked risk per file
telos deps <p>    # forward + reverse dependencies for a file
telos hotspots    # files with high churn × complexity
telos owners      # top owner per file (or per repo)
telos sync        # advanced: re-upload the last scan without re-scanning
telos login       # advanced: re-authenticate
telos logout      # clear local credentials

Most users never need sync or login directly — init handles both.

Flags

telos [command] [options]

Options:
  --cwd <path>    repository root (defaults to the current working directory)
  --json          emit machine-readable JSON
  --quiet         suppress non-essential output
  --verbose       verbose output
  -V, --version   print the version
  -h, --help      print help

License

MIT.