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

@hermannmaier/checkcli

v0.1.0

Published

Cross-ecosystem CLI environment health checker

Readme

checkcli

checkcli is a cross-ecosystem environment health checker for developer machines.

It helps you detect and fix common setup issues across PATH, package managers, versions, symlinks, and permissions.

Install

Run without installing:

npx @hermannmaier/checkcli --help

Install globally:

npm install -g @hermannmaier/checkcli
checkcli --help

Run from source:

npm install
npm run build
node dist/src/cli.js --help

Quick Start

# full report
checkcli

# machine-readable output
checkcli --json

# show available checks
checkcli --list-checks

# run a subset
checkcli --only path-health,project-versions

# skip expensive checks
checkcli --fast

# apply low-risk remediations
checkcli --apply-safe

Included Checks

  • path-health: PATH duplication, command shadowing, manager overlap hints.
  • symlink-health: broken symlink scan in common bin directories.
  • node-health: Node/npm availability, npm prefix health, npm doctor.
  • ownership-health: root-owned files in user-managed directories (common after sudo installs).
  • project-versions: project constraints vs active runtime versions (.nvmrc, .node-version, .tool-versions, package.json#engines, .python-version, pyproject.toml).

Safety Model

Default behavior is non-destructive and report-only.

--apply-safe is intentionally limited to low-risk actions:

  • create missing npm prefix directories,
  • optionally remove broken symlinks after confirmation.

For permission-protected paths, the tool prints a follow-up elevated command for the specific operation. Do not run the entire tool with elevated privileges unless you explicitly intend to.

CLI Options

  • --json: JSON output.
  • --apply-safe: apply low-risk fixes.
  • --yes: auto-confirm prompts during safe fixes.
  • --only <id>[,<id>...]: run only selected checks.
  • --skip <id>[,<id>...]: exclude selected checks.
  • --list-checks: print check ids and titles.
  • --fast: reduced-cost mode (skips npm doctor, smaller ownership/symlink scans).
  • --color / --no-color: force-enable/disable ANSI colors in human output.

Output Colors

  • Red: error findings and failed safe-fix actions.
  • Yellow: warnings and skipped safe-fix actions.
  • Green: suggested fixes and commands.

Colors auto-enable for TTY output and are disabled in JSON mode.

Exit Codes

  • 0: no error-level findings and no failed safe-fix actions.
  • 1: at least one error-level finding or a failed safe-fix action.

Development

See CONTRIBUTING.md for local workflow, adding checks, and release steps.