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

@asdsadw12312dwd2112xz/cert-check-cli

v1.0.0

Published

Check SSL/TLS certificates from the terminal

Readme

cert-check-cli

Check SSL/TLS certificates from the terminal.

Installation

npm install -g cert-check-cli

Or run directly:

npx cert-check-cli example.com

Usage

cert-check-cli [options] <domains...>

Options

| Option | Description | |--------|-------------| | --json | Output results as JSON | | --warn-days <n> | Exit with code 1 if cert expires within N days | | --port <n> | Default port (default: 443) | | --timeout <ms> | Connection timeout in ms (default: 10000) | | -V, --version | Print version | | -h, --help | Show help |

Examples

Check a single domain

cert-check-cli example.com

Output:

────────────────────────────────────────────────────────────
Domain: example.com
  Status:       ✓ VALID
  Days left:    245 days
  Valid from:   Jan 1 00:00:00 2024 GMT
  Valid to:     Dec 31 23:59:59 2024 GMT
  Subject:      CN=example.com
  Issuer:       C=US, O=Let's Encrypt, CN=R3
  SANs:         example.com, www.example.com
  TLS version:  TLSv1.3
  Cipher:       TLS_AES_256_GCM_SHA384 (TLSv1.3)
────────────────────────────────────────────────────────────

Check multiple domains

cert-check-cli github.com google.com cloudflare.com

Non-standard port

cert-check-cli myserver.com:8443
# or
cert-check-cli myserver.com --port 8443

JSON output

cert-check-cli example.com --json

Alert mode (CI/monitoring)

Exit with code 1 if any cert expires within 14 days:

cert-check-cli example.com --warn-days 14
echo $?  # 0 = ok, 1 = expiring or error

Color coding

  • Green — valid, more than 30 days remaining
  • Yellow — expiring within 30 days
  • Red — expired

Build from source

npm install
npm run build
node dist/index.js example.com