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

@flowwright/provider-github

v0.1.1

Published

FlowWright GitHub App source-control provider adapter — install, repository discovery, and short-lived checkout credentials via Octokit.

Downloads

250

Readme

@flowwright/provider-github

The GitHub source-control adapter for FlowWright — a GitHub App integration (built on Octokit) that handles installation, repository discovery, webhook-driven runs, commit-status reporting, and short-lived checkout credentials. It implements the provider-neutral adapter contract so the control plane stays SDK-free.

FlowWright · Server · GitLab provider

Use it

import { buildGitHubProvider } from "@flowwright/provider-github";

const provider = buildGitHubProvider({
  appId: process.env.FW_GITHUB_APP_ID!,
  privateKey: process.env.FW_GITHUB_PRIVATE_KEY!,
  webhookSecret: process.env.FW_GITHUB_WEBHOOK_SECRET!,
});

const repos = await provider.listRepositories(installationId, null);
const cred = await provider.checkoutCredential(installationId, repositoryId);
await provider.createRunStatus(/* run → commit status */);

The control plane resolves and injects the provider through the source-control registry; you rarely construct it directly outside tests.

Public surface

| Area | Main exports | |---|---| | Provider | GitHubAppProvider, buildGitHubProvider, GitHubAppProviderConfig |

Key adapter methods: completeInstallation / refreshInstallation, listRepositories, getRepository, listBranches, listPullRequests, checkoutCredential, and createRunStatus.

Design boundary

  • Implements the source-control adapter contract from the control plane against the GitHub App API — one of the interchangeable providers registered in the SCM registry.
  • Normalizes GitHub payloads into FlowWright's provider-neutral shapes; the control plane never imports Octokit.
  • Checkout credentials are short-lived and redacted; no secrets are persisted here.

Development

$ pnpm --filter @flowwright/provider-github typecheck
$ pnpm --filter @flowwright/provider-github test
$ pnpm --filter @flowwright/provider-github build

Requires Node.js 24+. Licensed under MIT.