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

@retinue/tools-github

v0.3.0

Published

GitHub tools for a Retinue agent: search code, read files, manage issues and pull requests — classified, gated and idempotent.

Readme

@retinue/tools-github

npm licence

GitHub tools for a Retinue agent. Search code, read files, manage issues and pull requests — with every write classified, gated behind human approval, and carrying an idempotency key.

Install

npm i @retinue/tools-github

@retinue/agentkit is a peer dependency. This package brings no other dependency.

Use

import { createAgent } from "@retinue/agentkit/providers";
import { createStaticCredentialResolver } from "@retinue/agentkit/tools";
import { createGitHubToolkit } from "@retinue/tools-github";

const agent = createAgent({
  manifest: { id: "dev", name: "Dev", instructions: "Help with the repository.", modelPolicy: { role: "smart" } },
  tools: [
    createGitHubToolkit({
      credentialRef: "github",
      // Your resolver. This one is for a single-tenant deployment; a multi-tenant host resolves per tenant.
      resolver: createStaticCredentialResolver({ github: process.env.GITHUB_TOKEN ?? "" }),
    }),
  ],
});

const result = await agent.run({
  conversationId: "conv-1",
  message: "Find where we validate egress and open an issue if it lacks a test.",
});

The token is resolved per call, not at construction, so rotating it takes effect without a restart. Nothing in this package reads the environment — that line above is your host doing it, visibly.

Tools

| Tool | Effect | Approval | |---|---|---| | github_search_code | read | never | | github_get_file | read | never | | github_list_issues | read | never | | github_create_issue | external-write | always | | github_comment | external-write | always | | github_merge_pull_request | destructive | always |

Approval is driven by the classification, not by the name — so a gate cannot be lost by renaming a tool, and a retried write returns the first result rather than firing twice.

Configuration

| Option | Required | Notes | |---|---|---| | credentialRef | yes | An opaque handle your resolver understands. A personal access token or a GitHub App installation token both work | | resolver | yes | CredentialResolver from @retinue/agentkit/tools | | baseUrl | no | Defaults to https://api.github.com. Set for GitHub Enterprise | | fetchImpl | no | Injected for tests |

Behaviour worth knowing

Pagination reports truncation. github_list_issues walks up to five pages and returns truncated: true when it stopped early. A tool that returns page one silently teaches the model there were only thirty issues.

Rate limits are their own outcome. A 429 comes back as a retryable rate_limited error rather than a generic failure, so the model waits instead of retrying with different arguments.

Egress is the platform's. Every request goes through the runtime's egress policy, which refuses private address space — the control that matters when a URL is influenced by a model.

Licence

MIT — see LICENSE.

Copyright (c) 2026 Azeem Sarwar and Rise Experts.