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-clean-code

v0.1.0

Published

DNA layer: clean code and test conventions, language neutral plus Dart and TypeScript

Readme

dna_clean_code

The DNA layer for how code is written and tested — the rules that hold in every language, plus the specifics of the languages we use.

Guides

  • dna/doc/guides/code-guide.md — layout, API shape, naming, small functions, saying it once
  • dna/doc/guides/code-guide-dart.md, dna/doc/guides/code-guide-typescript.md — what that means in each language
  • dna/doc/guides/test-guide.md — mirroring the source tree, real types over mocks, asserting on structure, 100 percent coverage
  • dna/doc/guides/test-guide-dart.md, dna/doc/guides/test-guide-typescript.md — the same, per language
  • dna/doc/guides/for-ai/ai-review-guide.md, dna/doc/guides/for-ai/review-heavy-guide.md — the review checklist an agent works through

Skills

  • /code — checks the repo against the code guide
  • /test — checks the tests against the test guide
  • /review-light — reviews the current changes
  • /review-heavy — the same, plus /simplify and /code-review

Layers

Orthogonal — it declares no parents and is inherited by the umbrella layer of each organization.

Variables

  • dnaCopyrightHolder — the name in the license header of every file

Adapting it

The language guides are ordinary DNA files, so a later layer can replace or patch them:

  • a same-path dna/doc/guides/code-guide-typescript.md replaces the file
  • a dna/doc/guides/code-guide-typescript.overrides.md patches only the sections it names

The neutral guides mark their exchangeable sections with @ tags — @layout, @imports, @api, @naming, @nesting, @coverage, @performance, @security — so an override can replace one section without restating the rest.

Usage

Declare it as a dev-dependency and initialize once:

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

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.