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

@agentic-research/depgraph-collect

v0.2.0

Published

Read what repositories declare — manifests, lockfiles, workflows — into a sources lock the portable core derives from. Node-only, no credential.

Readme

@agentic-research/depgraph-collect

Reading repositories into a sources lock, which @agentic-research/depgraph-core derives the map from. Node-only — everything that touches a filesystem, a network or a process lives here so the core does not.

No credential, deliberately

Nothing in this package reads a token or an environment variable for one. Repository visibility is established by asking GitHub unauthenticated, and it fails closed: a repository whose visibility cannot be established is treated as private, its manifests are never read, and any edge touching it carries no detail.

This is a constraint, not an oversight. A graph whose contents depend on who authenticated is not reproducible by anyone else. It is also a bug this code has already had: an earlier version used a token "if present", and a privileged run recorded three private repositories as public.

The cost is the unauthenticated rate limit — sixty requests an hour, one per repository. That is the right trade, and a token cannot buy your way out of it without reintroducing the bug.

Membership is yours to supply

The roster — which repositories the map may name — is an authored judgment, so this package does not discover it. Build a RosterEntry[] however your project already records membership and hand it over:

import {
  entryFromGithub,
  resolveCheckouts,
  parseRoots,
} from "@agentic-research/depgraph-collect";

const roster = resolveCheckouts(
  [
    entryFromGithub("agentic-research/mache"),
    entryFromGithub("agentic-research/rosary"),
  ],
  parseRoots(process.env.REPO_ROOTS),
);

There is no default search root. A package cannot know where you keep your checkouts, and guessing would silently find the wrong repository.

License

Apache-2.0