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

keyguard-core

v0.2.1

Published

Zero-dependency secret detection engine for Key-Guard

Readme

keyguard-core

The secret detection engine behind Key-Guard. Zero runtime dependencies.

Most people want the CLI instead:

npm install -g keyguard-cli

This package exists so the CLI, CI adapters and future editor integrations all agree on what counts as a secret.

Usage

import { scanText } from "keyguard-core";
import { readFileSync } from "node:fs";

const path = "config.js";
const findings = scanText(readFileSync(path, "utf8"), { path });

for (const finding of findings) {
  console.log(`${finding.line}:${finding.column}`, finding.ruleName, finding.preview);
}

Pass { includeWarnings: true } to also get the heuristic entropy matches, which are excluded by default.

Findings carry a redacted preview and a hash fingerprint. The raw matched value is not retained, because printing a secret in full would re-leak it into terminal history and CI logs.

API

| Export | Purpose | | ------------------------- | ----------------------------------------------- | | scanText(text, options) | Scan a string, returns findings | | scanFile(path, options) | Read and scan a file | | redact(value) | Safe preview of a sensitive value | | shannonEntropy(value) | Entropy score | | isPlaceholder(value) | Recognise obvious dummies and public defaults | | hasInlineAllow(line) | Detect a keyguard:allow pragma | | parseIgnoreFile(text) | Parse .keyguardignore | | shouldSkipPath(path) | Hard skips for lockfiles, binaries, and similar | | getServiceInfo(service) | Rotation URL and steps for a service | | RULES | The detection rules |

What it detects

Documented credential formats for AWS, GitHub, GitLab, Slack, Stripe, Google, OpenAI, Anthropic, Atlassian, npm, PyPI, SendGrid, Shopify, Twilio, Mailgun and Discord; private key blocks; JWTs (validated by decoding the header, not just pattern-matched); credentials embedded in connection strings; and generic high-entropy assignments as warnings.

Entropy matches are always warnings, never blocking. Blocking on entropy turns one noisy lockfile into a reason to uninstall the tool.

License

MIT © L-ubu