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

@jannik-stacks/agi

v0.0.2

Published

agentgraph runs coding agents on your repo's issues. The agents, checks and workflows are Markdown files in `.agentgraph/`. Agents work in Docker sandboxes without a GitHub token, the engine pushes only checked work, and a person merges it.

Readme

agentgraph

agentgraph runs coding agents on your repo's issues. The agents, checks and workflows are Markdown files in .agentgraph/. Agents work in Docker sandboxes without a GitHub token, the engine pushes only checked work, and a person merges it.

Quickstart

You need Node 24, Docker without root and git config user.name. No API key: when you are logged in to Claude Code, the first agi start runs claude setup-token, tests the pasted token and keeps it in the macOS Keychain (a 0600 file on Linux). A ChatGPT login through Codex, an Anthropic key or LiteLLM also work; see Models.

In a repo with an off-by-one bug in padStart and a failing test:

npm install -g @jannik-stacks/agi
agi start "padStart is off by one when len is 0"
agi show 1
git diff main...agentgraph/1
agi review 1 changes "also cover a negative len"
agi merge 1
git merge --ff-only agentgraph/1
agi studio

The first run builds the sandbox images, about 3 minutes. An implementor changes the code and runs the tests, a reviewer reads it, then it waits for you. The branch lands in your repo; your checkout never moves.

Without .agentgraph/ it runs the default graph. No GitHub needed: ~/.agentgraph/<repo>-<hash>-local/ holds instance.yaml, the runs in data/ and forge/, which stands in for GitHub.

From source

agi studio needs a clone: run npm ci && npm run build && npm link in it, and npm run build again after each pull.

Docs

Start at What agentgraph is, then:

  1. Install and first run
  2. The graph folder
  3. Checks and results
  4. Workflows
  5. Running on GitHub
  6. Hosting
  7. CLI

Examples

| Example | What it is | | --------------------- | ---------------------------------------------- | | examples/sandbox | A small JavaScript package; the place to start | | examples/agentgraph | The graph agentgraph runs on itself | | examples/bench | The graph the bench replays pull requests with |

Development

npm run check runs everything CI runs. See Engine and code and STYLE.md.

License

MIT, see LICENSE.