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

git-third-party

v1.0.0

Published

Vendor third-party Git repositories into your own, with path filtering and local patches. CLI plus in-process Node bindings.

Readme

git-third-party (Node)

Vendor third-party Git repositories into your own, with path filtering and local patches.

This package ships two entry points:

  1. The git-third-party CLI (added to your PATH via npm install -g git-third-party or available via npx).
  2. In-process Node bindings (import { add, list, ... } from 'git-third-party') backed by the same Go core via a c-shared library.

For the full feature set, configuration format, and CLI reference, see the project README.

Install

npm install -g git-third-party
# or:
pnpm add -g git-third-party
# or scoped to a project:
npm install git-third-party

npm fetches the right platform binaries through optionalDependencies. Supported platforms: linux-x64, linux-arm64, darwin-x64, darwin-arm64, win32-x64.

CLI

git-third-party --help
git-third-party add vendor/foo https://github.com/x/y --follow main
git-third-party update

Library

import { init, add, list, version } from "git-third-party";

console.log(version());
init();
add({ dir: "vendor/foo", url: "https://github.com/x/y", follow: "main" });
for (const e of list()) {
  console.log(e.dir, e.commit);
}

Mutating calls accept dryRun?: boolean and commitMsg?: string. All calls accept repoPath?: string (default ".").

Errors

import { ConfigError, ConflictError, GitThirdPartyError } from "git-third-party";

try {
  add({ /* ... */ });
} catch (e) {
  if (e instanceof ConflictError) { /* unresolved 3-way merge */ }
  else if (e instanceof ConfigError) { /* invalid TOML */ }
  else if (e instanceof GitThirdPartyError) { /* anything else */ }
}

Concurrency

The cgo bridge serializes calls process-wide. For parallel work, use worker_threads.