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

@boringsec/cli

v0.1.2

Published

BoringSec Security Scanner CLI — scan your websites and code from the terminal

Readme

@boringsec/cli

BoringSec Security Scanner CLI — scan websites and code from your terminal.

Release 0.1.2 is approved for npm distribution under proprietary licensing. Hosted scans require an eligible BoringSec account, authorized targets, and available quota.

Install

npm install -g @boringsec/[email protected]
boringsec login
boringsec help

Local development

Version 0.1.2 automatically retries safe reads only. It does not automatically replay scan submissions after an error or redirect. If a request times out or its response cannot be confirmed, it may already have been accepted; check scan history and usage before submitting again. Older installed clients must be updated to receive these corrections.

# Build from this repository
npm --prefix packages/cli run build

# Scan a URL with the local build
node packages/cli/dist/index.js scan https://myapp.com

# Scan code in the current directory
node packages/cli/dist/index.js scan-code

# Preview connected scanner engines from a manifest
node packages/cli/dist/index.js connected-scan --manifest boringsec.scan.json --dry-run

# Check usage
node packages/cli/dist/index.js usage

# Set API key
node packages/cli/dist/index.js login

Commands

| Command | Description | | ---------------------------------------------- | ----------------------------------------------- | | scan <url> | Scan a URL for 75+ security issues | | scan-code | Scan code files for secrets and unsafe patterns | | connected-scan --manifest <path> [--dry-run] | Run configured connected scanner engines | | usage | Show current usage and quota | | login | Set your API key | | help | Show help |

connected-scan --dry-run validates the manifest and prints planned engine commands without requiring an API key or uploading artifacts.

Features

  • 75+ security checks (headers, SSL, DNS, XSS, injection, secrets)
  • Colorized terminal output with severity badges
  • CI/CD friendly (exit code 1 on critical findings)
  • Works with GitHub Actions, GitLab CI, any CI system

Requirements

  • Node.js 18+
  • An eligible BoringSec API key with the required permissions and available quota

Links