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

orvyen

v0.1.8

Published

ESLint for your SQL codebase — audit any dbt or SQL project in one command

Readme

Orvyen

The SQL Architect — your dbt & SQL linter

Audit any SQL/dbt project in one command. Get a beautiful report of architectural issues, unused models, missing tests, and more.

npx orvyen ./models

🔴 Critical issues detected (fails CI) 🟠 High priority findings (data quality) 🟡 Medium suggestions (refactor candidates) ⚪ Low friction items (nice to have)


Why Orvyen?

Engineers working with dbt have no fast way to audit their codebase for architectural problems. Manual review is slow. Buster is expensive cloud SaaS.

Orvyen runs locally, instantly, free.

What it detects

| Issue | What it means | Impact | |-------|--------------|--------| | Broken refs | Reference to non-existent model | 🔴 Breaks dbt run | | Circular dependencies | Models depending on each other | 🔴 Breaks dbt run | | Missing tests | Models with no dbt tests | 🟠 Data quality risk | | Unused models | Models nothing references | ⚪ Dead code | | Grain misalignment | JOINs at wrong granularity | 🟠 Silent data bugs | | Duplicate logic | Copy-paste SQL across models | 🟠 Maintenance nightmare | | God models | Single model doing too much | 🟡 Refactor candidate | | Undocumented models | Missing description | ⚪ Developer friction |


Installation

# Install globally
npm install -g orvyen

# Or run with npx (no install needed)
npx orvyen ./models

Quick Start

1. Audit your project

npx orvyen ./models

Output:

 🔍 Orvyen – SQL Architecture Auditor

ℹ️  Auditing: /Users/you/project/models

 📊 Orvyen Audit Report
🔴 CRITICAL (2)
┌─────────────────┬──────────────────────┬──────────────────┐
│ Model           │ Issue                │ Description      │
├─────────────────┼──────────────────────┼──────────────────┤
│ orders_summary  │ Broken ref: 'orders' │ Reference non... │
│ user_metrics    │ Circular dependency  │ Forms cycle...   │
└─────────────────┴──────────────────────┴──────────────────┘

Audit Summary:
  Models analyzed: 25
  Findings: 8
  Time: 0.01s

2. Generate HTML report

npx orvyen ./models --format html

Creates .orvyen/report.html — open in browser and share with your team! ✅

3. Watch mode

Automatically re-run audit when files change:

npx orvyen ./models --watch

4. Initialize config

Create a .orvyen.config.js file to customize:

npx orvyen init

Edit the file:

export default {
  include: ["models/**/*.sql"],
  exclude: ["models/**/*staging*.sql"],
  
  checks: {
    unused_model: true,
    broken_ref: true,
    missing_tests: true,
    // ... more checks
  },

  output: "all", // terminal, html, json, or all
  outputDir: ".orvyen",
};

Commands

npx orvyen ./models [options]

OPTIONS:
  --format <type>    Output: terminal | html | json | all (default: terminal)
  --watch, -w        Re-run when files change
  --help, -h         Show help

npx orvyen init      Create .orvyen.config.js

EXAMPLES:
  npx orvyen .
  npx orvyen ./models --format all
  npx orvyen ./models --watch

Configuration

.orvyen.config.js

export default {
  // Which SQL files to include (required)
  include: ["models/**/*.sql"],

  // Files to exclude
  exclude: ["models/**/*test*.sql"],

  // Enable/disable checks and set severity
  checks: {
    unused_model: true,
    missing_tests: { severity: "high" },
    duplicate_logic: true,
    broken_ref: true,
    grain_misalignment: { severity: "high" },
    circular_dependency: true,
    undocumented_model: false,
    god_model: true,
  },

  // Output formats: "terminal" | "html" | "json" | "all"
  output: "all",

  // Where to save reports
  outputDir: ".orvyen",
};

Severity Levels

| Level | Meaning | CI Fails? | |-------|---------|-----------| | critical | Breaks dbt | Yes | | high | Data quality risk | No | | medium | Refactor candidate | No | | low | Nice to have | No |


Output Formats

Terminal (default)

Colorful table in your CLI. Fast feedback.

HTML

Beautiful, shareable report. Open in browser.

npx orvyen ./models --format html
# Creates: .orvyen/report.html

JSON

Machine-readable. Use in CI/CD:

npx orvyen ./models --format json
# Creates: .orvyen/report.json

Parse in your CI:

const report = require("./.orvyen/report.json");
if (report.summary.critical > 0) {
  process.exit(1); // Fail the build
}

GitHub Actions

Add to .github/workflows/audit.yml:

name: SQL Audit

on: [push, pull_request]

jobs:
  audit:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: "20"
      - run: npx orvyen ./models --format json
      - uses: dorny/test-reporter@v1
        if: always()
        with:
          name: SQL Audit Report
          path: .orvyen/report.json
          reporter: java-junit

How It Works

  1. Parse SQL files → Extract model names, refs, sources
  2. Parse schema.yml → Add tests, descriptions
  3. Build DAG → Model dependency graph
  4. Run checks → 8 parallel audit checks
  5. Report → HTML, JSON, or terminal output

All local. No cloud calls. No data sent anywhere.


Supported Databases

Works with any SQL dialect:

  • 🔴 Snowflake
  • 🔴 BigQuery
  • 🔴 Postgres
  • 🔴 MySQL
  • 🔴 Redshift
  • 🔴 DuckDB
  • 🔴 Spark SQL
  • 🔴 Generic SQL

Performance

| Project Size | Time | CPU | |--------------|------|-----| | 5 models | <5ms | minimal | | 50 models | 10-20ms | minimal | | 500 models | 50-100ms | minimal |


Common Issues

Error: "Cannot find module 'yaml'"

npm install -g orvyen
# or
npx orvyen@latest ./models

"No findings!" but there are issues

Check your .orvyen.config.js:

checks: {
  broken_ref: true,  // Make sure checks are enabled!
  unused_model: true,
}

Want to exclude a directory?

exclude: [
  "models/**/*staging*.sql",
  "models/archive/**",
  "models/test/**",
]

Roadmap

  • [ ] Week 2: HTML reports, init command, watch mode ✅
  • [ ] Week 3: GitHub Actions integration
  • [ ] Week 4: Web dashboard (hosted, optional)
  • [ ] Week 5: Team collaboration features

Contributing

Open source! Issues and PRs welcome.

git clone https://github.com/om/orvyen
cd orvyen
npm install
npm run build
npm run test

License

MIT


Need Help?


Made with 🔴 for data engineers