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

@tyler.given/best-practices-config

v0.1.0

Published

Best-practices knowledge base — explicit CI/Docker/per-repo installer (no postinstall home-dir writes)

Readme

@tyler.given/best-practices-config

CI/Docker-safe explicit installer for the best-practices knowledge base.

Unlike @tyler.given/best-practices, this package has no postinstall script and makes no home-directory writes. Content is installed only when you explicitly run the setup command.

Use cases

  • CI pipelines (npm install without side effects)
  • Docker images (no home-dir pollution)
  • Per-repo devDependency (install content into a project-local path)
  • Environments without interactive TTY

Install

npm install --save-dev @tyler.given/best-practices-config

Usage

# Interactive — choose domains, install to ./best-practices/
npx @tyler.given/best-practices-config setup

# Specify target directory
npx @tyler.given/best-practices-config setup --target .ai/skills/best-practices

# CI mode — installs all available domains non-interactively (CI env var set automatically)
npx @tyler.given/best-practices-config setup --target .ai/skills/best-practices

What gets installed

  • SKILL.md — skill definition (agent navigation + invocation guide)
  • categories.md — full domain taxonomy reference
  • technology_and_information/ — IT, cybersecurity, data science, AI, git workflow, etc.
  • Additional domains based on your selection (or all available in CI mode)

Differences from @tyler.given/best-practices

| Feature | @tyler.given/best-practices | @tyler.given/best-practices-config | |---|---|---| | Auto-install on npm install | ✅ Yes | ❌ No | | Writes to ~/.copilot/ / ~/.claude/ | ✅ Yes | ❌ No | | CI safe | ⚠️ Warns, skips conflicts | ✅ Always safe | | Explicit --target dir | ❌ No | ✅ Yes | | Injects AI-human defaults | ✅ Yes | ❌ No |

Source

Part of the tyler555g/best-practices repository.