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

@createsomething/triad-audit

v0.1.0

Published

Subtractive Triad Audit: DRY, Rams, Heidegger analysis for codebases. Less, but better.

Readme

@create-something/triad-audit

"Creation is the discipline of removing what obscures."

A code analysis tool based on Dieter Rams' principle: Weniger, aber besser (Less, but better).

The Subtractive Triad

| Level | Question | Action | |-------|----------|--------| | DRY (Implementation) | "Have I built this before?" | Unify | | Rams (Artifact) | "Does this earn its existence?" | Remove | | Heidegger (System) | "Does this serve the whole?" | Reconnect |

Installation

npm install -g @create-something/triad-audit
# or
npx @create-something/triad-audit

Usage

CLI

# Audit current directory
triad-audit

# Audit specific path
triad-audit /path/to/project

# Output JSON to file
triad-audit -f json -o report.json

# Run specific analysis level
triad-audit -l dry    # DRY only
triad-audit -l rams   # Rams only
triad-audit -l heidegger  # Heidegger only

# Baseline comparison (CI/CD)
triad-audit --baseline     # Save current scores
triad-audit --compare      # Compare to baseline

# Generate config file
triad-audit --init

Programmatic API

import { runAudit, formatAsMarkdown } from '@create-something/triad-audit';

const result = await runAudit({ path: './src' });

console.log(`Overall score: ${result.scores.overall}/10`);
console.log(`Violations: ${result.summary.totalViolations}`);

// Generate markdown report
const report = formatAsMarkdown(result);

Output

📈 SCORES
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  ✓ DRY (Implementation)   ████████░░ 8.0/10
  ○ Rams (Artifact)        ██████░░░░ 6.0/10
  ✗ Heidegger (System)     ████░░░░░░ 4.3/10
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  ○ OVERALL                ██████░░░░ 6.1/10

⚠️ VIOLATIONS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  🟠 High:     3
  🟡 Medium:   12
  🟢 Low:      5

What It Detects

DRY Level (Implementation)

  • Duplicate code blocks - Copy-pasted code that should be unified
  • Similar patterns - Near-duplicates that indicate missing abstractions

Rams Level (Artifact)

  • Dead exports - Exports never imported anywhere
  • Unused dependencies - npm packages not used in code
  • Large files - Files that may need splitting (>500 lines)
  • Empty files - Files with no meaningful content

Heidegger Level (System)

  • Orphaned files - Files not connected to the module graph
  • Circular dependencies - Import cycles that create tight coupling
  • Package completeness - Missing package.json fields

Configuration

Create .triad-audit.json in your project root:

{
  "ignore": [
    "**/node_modules/**",
    "**/dist/**",
    "**/build/**"
  ],
  "focus": ["src/**"],
  "thresholds": {
    "dry": { "min": 6, "warn": 7 },
    "rams": { "min": 6, "warn": 7 },
    "heidegger": { "min": 5, "warn": 6 }
  },
  "skipPatterns": {
    "deadExports": ["packages/sdk/**"],
    "orphanedFiles": ["examples/**"],
    "largeFiles": ["**/*.d.ts"]
  }
}

CI/CD Integration

GitHub Actions

Copy templates/github-workflow.yml to .github/workflows/triad-audit.yml:

name: Subtractive Triad Audit

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

jobs:
  audit:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '20'

      - name: Run audit
        run: |
          npx @create-something/triad-audit --format json --output audit.json --compare

      - name: Check thresholds
        run: |
          SCORE=$(jq '.scores.overall' audit.json)
          if (( $(echo "$SCORE < 5" | bc -l) )); then
            echo "::error::Score below threshold"
            exit 1
          fi

Exit Codes

| Code | Meaning | |------|---------| | 0 | Success, no critical issues | | 1 | High severity violations found | | 2 | Critical violations found |

Baseline Tracking

Track scores over time with baseline comparison:

# After initial audit, save baseline
triad-audit --baseline

# On subsequent runs, compare
triad-audit --compare

📊 COMPARISON TO BASELINE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  🟢 DRY:       ↑ +0.5
  🟢 Rams:      ↑ +1.2
  🟡 Heidegger: → 0.0
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  🟢 OVERALL:   ↑ +0.6

  ✨ Scores have improved since baseline!

History is stored in .triad-audit/ directory.

Philosophy

This tool embodies the CREATE SOMETHING ethos:

  • Subtraction over addition - Good code is code removed
  • Intentionality - Every line should earn its existence
  • Wholeness - Parts should serve the system, not themselves

Read more: createsomething.ltd/ethos

License

MIT