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 🙏

© 2025 – Pkg Stats / Ryan Hefner

dnsman

v0.6.2

Published

Simple dns manager, allows you to easily define your own domains handled by it.

Downloads

36

Readme

dns manager

Simple dns manager, allows you to easily define your own domains handled by it.

Overview

By default, dnsman reads /etc/dnsman/records and responds to requests by choosing the most specific entry.

# /etc/dnsman/records

# Upstream/fallback servers
nameserver 8.8.8.8
nameserver 8.8.4.4

# Proxy example.com to these, ordered by priority
ns .example.com 1.1.1.1
ns .example.com 1.0.0.1

# Route the .dev tld to localhost
a .dev 127.0.0.1
txt .domain.com "text entry"
txt .domain.com "includes""quotes"

Upstream/fallback server

Normally, dns servers will respond with an upstream server to the client and let the client make a new request to that server. This server will pretend to be all-knowing, or at least for the first hop, forwarding the request to a known upstream server if it doesn't know.

Matching

Matching records is performed by the tailing end of the request. Assume requests always have a dot prepending their least signigicant section.

| Config | Request | Matches | | ------------ | ---------------- | ------- | | .dev | mydomain.dev | yes | | .dev | example.dev | yes | | example.com | example.dev | no | | example.com | example.com | yes | | example.com | 1example.com | yes | | example.com | sub.example.com | yes | | example.com | sub.1example.com | yes | | .example.com | example.com | yes | | .example.com | 1example.com | no | | .example.com | sub.example.com | yes | | .example.com | sub.1example.com | no |