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

@capitalthought/dns

v0.3.0

Published

Shared DNS / domain primitives for Capital Thought projects — zone-check (CZDS), whois/rdap, DNS-record CRUD, email-auth (SPF/DKIM/DMARC + ramp), nameservers, variants. Single source of truth for marc + mikey + domains.

Readme

@capitalthought/dns

Shared DNS / domain primitives for Capital Thought projects — the single source of truth consumed by marc (trademark clearance), mikey (domain-checker), and domains (portfolio actuator). No DNS/domain logic is re-implemented in those repos.

Scope: DNS + zone + availability + email-auth primitives. No registrar-write credentials live here — registrar lifecycle (register / renew / transfer) is the domains agent's registrar-adapter layer, not this library.

Modules

| Import | Status | What | |---|---|---| | @capitalthought/dns/dns-records | ✅ ready | Provider-pluggable DNS-record CRUD (Cloudflare provider in v1) | | @capitalthought/dns/email-auth | ✅ ready | SPF / DKIM / DMARC builders + the p=none → quarantine → reject ramp | | @capitalthought/dns/nameservers | ✅ ready | NS read helpers over DNS-over-HTTPS | | @capitalthought/dns/rdap | ✅ ready | RDAP registration lookup | | @capitalthought/dns/whois | 🚧 port from marc | WHOIS lookup (contract declared, impl pending M0.1) | | @capitalthought/dns/zone-check | 🚧 port from marc | CZDS bulk availability (ZoneChecker.checkFiltered) | | @capitalthought/dns/tlds | 🚧 port from marc | TLD tier config + CZDS auth (P1 seeded; tier-2/gTLD pending) | | @capitalthought/dns/variants | 🚧 port from marc | typosquat / brand-protection generation |

Everything is also re-exported from the root: import { buildDmarc, CloudflareDnsProvider } from "@capitalthought/dns".

Examples

import { CloudflareDnsProvider } from "@capitalthought/dns/dns-records";
import { buildSpf, buildDmarc, planRampStep, parseDmarc } from "@capitalthought/dns/email-auth";

// DNS CRUD (token = scoped Zone:DNS:Edit, read from 1Password at call time)
const cf = new CloudflareDnsProvider({ apiToken: process.env.CF_DNS_TOKEN! });
const zoneId = await cf.getZoneId("baer5.com");
await cf.createRecord(zoneId!, { type: "A", name: "lvp.baer5.com", content: "192.0.2.1", proxied: true });

// Anti-spoof a domain that sends no mail
buildSpf({ all: "-" });                       // "v=spf1 -all"
buildDmarc({ policy: "reject" });             // "v=DMARC1; p=reject"

// DMARC ramp — proposes the next step; p=reject is ALWAYS gated
const current = parseDmarc("v=DMARC1; p=none; rua=mailto:[email protected]")!;
const step = planRampStep(current);
// → { from: "none", to: "quarantine", record: "v=DMARC1; p=quarantine; rua=mailto:[email protected]", requiresApproval: true }

Security notes

  • Registrar / whois / RDAP text is untrusted. Registrant/org/status strings are attacker-controllable (domains PRD U1). Treat them as data, never instructions, before any LLM summarization.
  • The DMARC ramp builder is deterministic — record values come from pure functions, never raw LLM output, so a hallucinated policy can't reach a live zone.
  • No secrets in this library. Tokens (Cloudflare, CZDS JWT) are passed in by the caller, read from 1Password at call time.

Develop

npm install
npm run build      # tsc → dist/
npm test           # vitest
npm run check      # tsc --noEmit

UNLICENSED · Capital Thought, LLC