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

check-my-toolkit

v2.8.0

Published

Unified project health checks - code, process, and infra

Readme

check-my-toolkit

A unified CLI for enforcing code quality, workflow compliance, and infrastructure standards. One config file, multiple tools, consistent output.

npm install -g check-my-toolkit

Why?

Most projects cobble together ESLint, Prettier, Ruff, tsc, and various other tools with inconsistent configs. cm unifies them:

  • Single configcheck.toml controls all tools
  • Three domains — Code quality, process compliance, infrastructure validation
  • Consistent output — Same format whether it's ESLint, Ruff, or AWS tagging
  • Org standards — Extend from a shared registry to enforce team conventions
  • CI-ready — Exit codes and JSON output for automation

Quick Start

# Create check.toml
cat > check.toml << 'EOF'
[code.linting.eslint]
enabled = true

[code.types.tsc]
enabled = true

[process.hooks]
enabled = true
require_husky = true
EOF

# Run all checks
cm check

Domains

CODE — 14 Tools

Static analysis, formatting, type checking, and security.

| Category | Tools | | ------------- | ------------------------------- | | Linting | ESLint, Ruff | | Formatting | Prettier, Ruff Format | | Type Checking | tsc, ty | | Unused Code | Knip, Vulture | | Security | Gitleaks, npm-audit, pip-audit | | Other | Tests, Naming, Disable Comments |

PROCESS — 8 Checks

Workflow and policy enforcement.

| Check | Purpose | | -------- | ----------------------------- | | Hooks | Git hooks (Husky) validation | | CI | GitHub workflow requirements | | Branches | Branch naming patterns | | PR | Size limits (files, lines) | | Tickets | Jira/Linear references | | Coverage | Threshold enforcement | | Repo | Branch protection, CODEOWNERS | | Backups | S3 backup verification |

INFRA — 1 Check

Infrastructure validation.

| Check | Purpose | | ------- | ----------------------------- | | Tagging | AWS resource tag requirements |

Commands

# Run all checks
cm check                       # All domains (code + process + infra)
cm audit                       # Verify all configs exist

# Domain-specific
cm code check                  # Code quality checks
cm process check               # Workflow validation
cm infra check                 # Infrastructure checks

# Process utilities
cm process diff                # Show branch protection differences
cm process sync --apply        # Sync branch protection to GitHub

# Project management
cm projects detect             # Discover projects in monorepo
cm projects detect --fix       # Create missing check.toml files

# Configuration
cm validate config             # Validate check.toml
cm schema config               # Output JSON schema

Configuration

CODE Domain

[code.linting.eslint]
enabled = true
max-warnings = 0

[code.linting.ruff]
enabled = true
format = true
line-length = 88

[code.types.tsc]
enabled = true

[code.types.tsc.require]
strict = true

[code.unused.knip]
enabled = true

[code.security.secrets]
enabled = true

[code.naming]
enabled = true

[[code.naming.rules]]
extensions = ["ts", "tsx"]
file_case = "kebab-case"
folder_case = "kebab-case"

PROCESS Domain

[process.hooks]
enabled = true
require_husky = true
require_hooks = ["pre-commit", "pre-push"]

[process.ci]
enabled = true
require_workflows = ["ci.yml"]

[process.ci.jobs]
"ci.yml" = ["test", "lint", "build"]

[process.branches]
enabled = true
pattern = "^(feature|fix|hotfix)/v[0-9]+\\.[0-9]+\\.[0-9]+/.+"
exclude = ["main", "develop"]

[process.pr]
enabled = true
max_files = 20
max_lines = 500

[process.tickets]
enabled = true
pattern = "^(PROJ)-[0-9]+"
require_in_commits = true

[process.coverage]
enabled = true
min_threshold = 80

[process.repo]
enabled = true
require_branch_protection = true
require_codeowners = true

[process.repo.ruleset]
branch = "main"
required_reviews = 1

[process.backups]
enabled = true
bucket = "my-backups"
prefix = "github/myorg/myrepo"
max_age_hours = 24

INFRA Domain

[infra.tagging]
enabled = true
region = "us-east-1"
required = ["Environment", "Owner", "CostCenter"]

[infra.tagging.values]
Environment = ["dev", "stag", "prod"]

Extending from a Registry

Share standards across repos:

[extends]
registry = "github:myorg/standards"
rulesets = ["typescript", "security"]

CI Integration

GitHub Actions

- name: Install check-my-toolkit
  run: npm install -g check-my-toolkit

- name: Run checks
  run: cm check

JSON Output

cm check --format json

Exit Codes

| Code | Meaning | | ---- | ------------------- | | 0 | All checks passed | | 1 | Violations found | | 2 | Configuration error | | 3 | Runtime error |

Monorepo Usage

Works with npm workspaces, Turborepo, Nx, and pnpm workspaces.

# Detect and initialize projects
cm projects detect --fix

# Run with task runners
npm run check --workspaces --if-present  # npm
turbo check                               # Turborepo
pnpm -r run check                         # pnpm

Documentation

Development

# Prerequisites (macOS)
brew bundle

# Commands
pnpm install        # Install dependencies
pnpm run build      # Compile TypeScript
pnpm test           # Run tests

License

MIT