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

github-mock

v1.0.3

Published

Mocking GitHub APIs made easy.

Readme

github-mock

Mocking GitHub APIs made easy.

Why?

GitHub's REST and GraphQL APIs are powerful and well-documented. Writing a tool or script that works is usually a quick and enjoyable experience. Creating meaningful tests – which allow to iterate on it with confidence – is not.

Snapshots require to run the requests against live APIs and stubbing responses is error-prone and only slightly better than just proofreading the implementation. While the documentation and types are already there, the code needed to create a beneficial test environment in most cases probably dwarfs the code under test itself.

Hopefully this library can change this.

How?

import {Octokit} from '@octokit/core'
import {createAppWithGithubMock} from 'github-mock'
import {createApp} from '../src/my-app-setup.ts'

const setup = createAppWithGithubMock(
    fetch => createApp(new Octokit({request: {fetch}})),
    config => {
        // Add additional mock implementations…
    },
)

test('make REST and GraphQL requests with working API mocks', async () => {
    const [myApp, mock] = setup(store => {
        // Add initial data…
    })

    // Interact with one or more mocked APIs…
    await myApp.doSomething()

    // Assert app output and/or store state…
})

If you have written an additional mock implementation, please consider opening a PR to add it to this library.