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

cert-lifetime-check

v0.1.1

Published

Find the TLS certificate lifetimes your repo asks for (cert-manager duration, openssl -days, cfssl expiry) and say which are already past the CA/Browser Forum maximum (200 days since 2026-03-15) and which stop being issuable later (100 days from 2027-03-1

Readme

cert-lifetime-check

Finds the TLS certificate lifetimes your repository asks for and says which of them a publicly-trusted CA may no longer issue — with the CA/Browser Forum's own table row quoted under each verdict.

$ npx cert-lifetime-check .
fail   k8s/cert.yaml:6  cert-manager duration 8760h = 365 days
       365 days is longer than the 200-day maximum, which took effect on 2026-03-15
       > 2026-03-15 | 6.3.2 | Maximum validity period of Subscriber Certificates is 200 days.
         https://cabforum.org/working-groups/server/baseline-requirements/requirements/
         last checked 2026-09-24 · CA/Browser Forum TLS Baseline Requirements 6.3.2
due    make-ca.sh:2  openssl -days 150 = 150 days
       150 days is within every cap our records show in force today, and longer
       than the 100-day maximum that takes effect on 2027-03-15 (119 days from 2026-11-16)

Exit status is 1 when a lifetime is longer than a cap that has already taken effect. A cap that takes effect later is reported and does not change the status unless you pass --strict, so putting this in CI does not start failing builds on the day a ballot passes unless you asked it to.

The schedule it knows

| Takes effect | Maximum certificate validity | BR section | | --- | --- | --- | | 2026-03-15 | 200 days | 6.3.2 | | 2027-03-15 | 100 days | 6.3.2 | | 2029-03-15 | 47 days | 6.3.2 |

It also holds the domain-control-validation reuse schedule (200 days from 2026-03-15, 100 from 2027-03-15, 10 from 2029-03-15) and the subject-identity reuse period, which fall on a different schedule from each other. cert-lifetime-check --schedule prints all of it with every quote.

What it reads

| Form | Example | | --- | --- | | cert-manager Certificate | duration: 8760h in a file whose apiVersion is cert-manager.io/… | | OpenSSL CA config | default_days = 730 in a .cnf/.conf | | OpenSSL command line | openssl req -x509 -days 365 in a script, Makefile or Dockerfile | | cfssl signing profile | "expiry": "8760h" in cfssl.json, ca-config.json |

A duration: in a YAML file that does not name cert-manager's API group is left alone, and a -days on a line that does not run openssl is not a certificate lifetime. node_modules, .git, vendor, dist and the usual build directories are skipped.

Use

npx cert-lifetime-check            # scan the current tree
npx cert-lifetime-check 365        # check one lifetime in days
npx cert-lifetime-check 8760h      # or as a Go duration
npx cert-lifetime-check --schedule # the dated schedule, with quotes
npx cert-lifetime-check --json     # the same, machine-readable
npx cert-lifetime-check --strict   # a forthcoming cap also exits 1
npx cert-lifetime-check --today 2027-04-01   # ask as at another date

As a library:

const { check, report, caps } = require('cert-lifetime-check');
check(365, { today: '2026-11-16' }).status;   // 'fail'
check(365).cap.source_quote;                  // the Forum's own row
report('.').filter((r) => r.status === 'fail');

What it does not claim

  • It is not a claim about your CA. These caps bind publicly-trusted TLS server certificates. A private CA inside your own trust store is not bound by them. We hold the CA/Browser Forum's schedule, not your issuer's policy, and some CAs tightened ahead of the dates.
  • It never prints a limit we hold no record of. The Forum's effective-date table lists only what changes, so there is no row in it for the 398-day limit that was in force before 2026-03-15. Asked about a date before then, this says "due on 2026-03-15" and not "the current limit is 398 days" — because the second sentence would be us remembering, not reading.
  • It reads what the file asks for, not what exists. A duration: 8760h is a request; it does not tell you how long your live certificate is actually valid for.
  • It writes nothing. Verdicts, file and line; the edit is yours.

Where the dates come from

Every date and quote is one record on referencesource.org/tls-certificate-requirement-effective-dates, extracted from the CA/Browser Forum's published Baseline Requirements effective-date table, re-checked against that page on a schedule, and carrying the date it was last checked. data.json ships the source URL, the verbatim row and the last-checked date for every cap, so nothing here has to be taken on trust.

The compilation is CC0-1.0. The underlying requirements are published by the CA/Browser Forum. Built and maintained by an automated pipeline.