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

@render-harness/cap-github

v0.8.2

Published

GitHub monitoring capability pack for the Render agent harness.

Readme

@render-harness/cap-github

GitHub webhook and repository tools for agents in the Render harness.

Use this pack when an agent should react to GitHub events, inspect issues and pull requests, read workflow status, and optionally comment or update GitHub objects.

Configuration

Drop the pack into render-harness.yaml:

capabilities:
  - pack: "@render-harness/cap-github"
    config:
      webhookSecretEnv: "GITHUB_WEBHOOK_SECRET"
      tokenEnv: "GITHUB_TOKEN"
      accessMode: "read"

Set these environment variables on the entry that loads the agent:

  • GITHUB_WEBHOOK_SECRET: GitHub webhook secret used to verify deliveries.
  • GITHUB_TOKEN: GitHub token used for repository reads and optional write tools.

Connector

The pack mounts the github connector at /connectors/github. Configure that URL as a GitHub webhook endpoint and use the same secret as GITHUB_WEBHOOK_SECRET.

Supported webhook events:

  • issues
  • issue_comment
  • pull_request
  • pull_request_review
  • pull_request_review_comment
  • push
  • check_run
  • check_suite
  • workflow_run

Each accepted GitHub delivery enqueues one harness run.

Config Keys

| Key | Type | Default | Notes | | --- | --- | --- | --- | | agent | string | default agent | Agent name to enqueue runs for. | | userId | string | cap-github | User ID stored on enqueued runs. | | webhookSecretEnv | string | GITHUB_WEBHOOK_SECRET | Env var that contains the GitHub webhook secret. | | tokenEnv | string | GITHUB_TOKEN | Env var that contains the GitHub token. | | accessMode | read or read_write | read | Enables write tools only when set to read_write. | | allowedRepositories | string[] | all repositories | Restricts events to repositories such as owner/repo. | | events | string[] | all supported events | Restricts accepted webhook event names. | | branches | string[] | all branches | Restricts branch-scoped events. | | labels | string[] | all labels | Restricts issue and pull request events to matching labels. | | ignoredActors | string[] | none | Ignores events from matching GitHub usernames. |

Tools

Read tools are available when GITHUB_TOKEN is set:

  • github.get_issue
  • github.get_pull_request
  • github.list_pull_request_files
  • github.list_pull_request_reviews
  • github.list_pull_request_commits
  • github.list_issue_comments
  • github.get_content
  • github.list_checks
  • github.list_workflow_runs
  • github.get_workflow_run
  • github.list_workflow_run_jobs

Set accessMode: read_write to enable write tools:

  • github.create_issue_comment
  • github.create_pull_request_review_comment
  • github.update_issue
  • github.add_issue_labels
  • github.set_commit_status
  • github.rerun_workflow_run
  • github.cancel_workflow_run

Use permissions.requireApproval for write tools if the agent should ask before mutating GitHub state.

Test Commands

pnpm --filter @render-harness/cap-github build
pnpm --filter @render-harness/cap-github test