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

@ggdna/dna-helix

v0.2.0

Published

DNA layer: how a DNA layer itself is built, configured and published

Readme

dna_helix

The DNA layer that tells a repo how to author a DNA layer of its own.

It carries only that one topic and is one of the layers dna_ggdna composes, so a repo gets it by taking the umbrella rather than by naming it.

Guides

  • dna/doc/guides/dna-guide.md — the dna/ layout and the dot- escape, what belongs in _dna.json and _vars.json, the three override mechanisms, and publishing one layer to both registries

Skills

  • /dna — checks a layer against the DNA guide: paths that would not instantiate, layers that are not dependencies, variables nothing declares, and manifests that drifted apart

Layers

Orthogonal, and parent-less like every topic layer of this organization.

Variables

  • dnaCopyrightHolder — the name in the license header of every file, set to ggdna here

Usage

Reach it through the umbrella:

pnpm add -D @ggdna/dna-ggdna   # TypeScript projects
dart pub add dev:dna_ggdna     # Dart projects
gg dna init

Naming this layer directly is for a repo that wants the authoring topic and nothing else:

pnpm add -D @ggdna/dna-helix
dart pub add dev:dna_helix

The placed test instantiates and verifies the DNA on every test run.

Development

The dna/ folder is hand-authored source and is never generated. The repo instantiates its own DNA — run dart test after changes; commit first, a file the DNA would overwrite must not carry uncommitted work.