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

yhlsec

v1.0.1

Published

CLI security checker for directories/files/zips

Readme

yhlsec

CLI security checker for directories / single files / zip archives.

Requirements

  • Node.js >= 18

Install

npm i -g yhlsec

This provides the yhlsec command.

Quick start

Scan current directory:

yhlsec

Scan a directory and write JSON report:

yhlsec ./dist --output report.json

Write HTML report:

yhlsec ./dist --output report.html

Scan a zip archive:

yhlsec ./archive.zip --output report.json

Scan a single file:

yhlsec ./src/app.js

Output formats

  • Stdout (when --output is omitted): --format text|json (default: text)
  • File output (when --output is set):
    • .html / .htm -> HTML
    • .json -> JSON
    • other extensions -> JSON

CI / exit codes

  • Exit code 0: scan completed and did not meet the fail threshold
  • Exit code 2: max severity met/exceeded the threshold

Examples:

yhlsec ./src --ci-fail-on-high
yhlsec ./src --fail-on medium

Configuration

Config file names:

  • .yhlsec.json
  • yhlsec.config.json

Resolution order:

  • --config <path> if provided
  • search upwards from the target directory
  • search upwards from current working directory

Generate a full example config:

yhlsec init-config

Write to a custom path:

yhlsec init-config -w yhlsec.config.json

What it checks

  • Built-in rules (glob / regex / string / meta)
  • External engines (configurable):
    • @ziul285/gitleaks (secret scanning)
    • npm audit (dependency vulnerabilities)
    • OSV API (dependency vulnerabilities)
    • retire (vulnerable JS libraries)
  • Risk package denylist (from lockfiles)
  • Zip Slip risk (unsafe zip entry paths)