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

repo-starter-kit

v0.4.0

Published

CLI to bootstrap and sync repository labels, issues, branch rulesets and config.

Readme

@zokugun/repo-starter-kit

MIT licensed NPM Version Donation Donation Donation

Command-line helper to bootstrap and sync repository settings (labels, issues, branch rulesets and basic config) from a reusable package or local files.

Why use this tool?

  • Reuse a central repo-starter-kit configuration published as an npm package or provide local files to keep repositories consistent.
  • Manage issue templates and labels programmatically.
  • Lightweight CLI with interactive prompts when needed.

Quick start

Install globally with npm:

npm install -g @zokugun/repo-starter-kit

Or run directly with npx:

npx @zokugun/repo-starter-kit --repo owner/name --package @your/package

Usage

Basic example:

repo-starter-kit --repo daiyam/temp --package @daiyam/default --keep-labels

Options

  • -r, --repo <owner/name>: Target repository (OWNER/NAME). Required.
  • -c, --create: Create the repository if it does not exist
  • -l, --labels <path>: Path to a labels YAML file to apply to the repository. Supports local files or npm URLs such as npm:@scope/config/labels.yml.
  • -i, --issue <path>: Path to a Markdown file used as an issue template. Supports local files or npm URLs such as npm:@scope/config/issue.md.
  • -b, --rulesets <path>: Path to a YAML/JSON file containing branch rulesets definitions. Supports local files or npm URLs such as npm:@scope/config/rulesets.yml.
  • -p, --package <name>: An npm package or a direct directory that includes a repo-starter-kit configuration file to apply.
  • --keep-labels: Do not delete labels missing from the provided configuration (defaults to false).
  • --keep-rulesets: Do not delete branch rulesets missing from the provided configuration (defaults to false).
  • -v, --version: Show version number.

Examples

  • Apply a published starter package to a repository:
repo-starter-kit -r myuser/myrepo -p @myorg/myconfig
  • Apply local labels file and an issue template (do not remove existing labels):
repo-starter-kit -r myuser/myrepo -l labels.yml -i issue.md -k

Configuration package

The configuration package need to be prefixed:

  • --package @daiyam/default will load the package @daiyam/repo-starter-kit-default

At its root, it needs to have one of the following file:

  • repo-starter-kit.yml
  • repo-starter-kit.yaml
  • repo-starter-kit.json

With its content as:

labels: <path to labels file>
issue: <path to issue file>
rulesets: <path to branch rulesets file>

Each <path> can be either a relative file path inside the package or an npm URL that references another published package (for example npm:@scope/reusable-kit/labels.yml).

For reference, please check https://github.com/daiyam/repo-starter-kit-default.

Branch rulesets

Each ruleset entry mirrors the payload accepted by the GitHub branch rulesets API. The file must contain an array of objects, for example:

- name: Protect main
    enforcement: active
    target: branch
    conditions:
        ref_name:
            include:
                - refs/heads/main
    rules:
        - type: pull_request
            parameters:
                required_approving_review_count: 1

Examples

The examples/ directory in this repository contains ready-to-use folders showing how to bundle labels, issues, and branch rulesets. Use them directly:

npx @zokugun/repo-starter-kit --repo <owner/name> --package ./examples/basic/

or publish one of the folders as an npm package (each folder already includes a repo-starter-kit.yml manifest) so you can pass --package @scope/name.

Donations

Support this project by becoming a financial contributor.

License

Copyright © 2025-present Baptiste Augrain

Licensed under the MIT license.