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

@comity-dev/validate

v0.1.1

Published

Thin orchestrator over Comity shared validation tooling. Development tooling.

Readme

@comity-dev/validate

Purpose

Thin orchestrator over Comity shared validation tooling. Discovers a repository, invokes the specialized engines (schema, dependency-cruiser, ESLint, Semgrep, adapter-peers), and returns a normalized result.

This package is intentionally small. It does not implement any rule. Its only responsibilities are:

  1. Discover repository configuration (comity.config.json).
  2. Discover packages.
  3. Invoke specialized engines.
  4. Collect and normalize results.
  5. Present a unified summary.

Scope

The engines wrap shared Development-owned tooling:

| Engine | Tool | Concern | | --------------- | --------------------------------------- | ---------------------------------------------------------- | | schema | @comity-dev/schemas (Ajv) | JSON Schema for package metadata and comity.config.json. | | depcruise | dependency-cruiser | Dependency graph layering. | | eslint | ESLint + @comity-dev/eslint-plugin | Source-code lint policy. | | semgrep | semgrep + @comity-dev/semgrep-rules | Structural source patterns. | | adapter-peers | in-process | Adapter peer-dependency contract. |

Engines report one of PASS / FAIL / NOT-RUN / TOOL-UNAVAILABLE / CONFIGURATION-ERROR / EXECUTION-ERROR / NOT-APPLICABLE. PASS is only reported when the engine actually executed.

Ownership

Owned by comity-development. Consumed by Comity repositories via the comity-validate CLI.

Public API

import {
  runValidation,
  discoverRepository,
  formatSummary,
  formatViolations,
  ExitCode,
} from "@comity-dev/validate";

CLI

comity-validate --repo /path/to/repo
comity-validate --only=schema        # one engine only
comity-validate --only=eslint --verbose

Exit codes:

  • 0 — validation passed
  • 1 — validation failed (violations found)
  • 2 — configuration / discovery error
  • 3 — required tool not installed

Negative fixtures

The src/__fixtures__/third-repo/ directory contains a deliberately invalid repository used by the package's own integration tests. It is not scanned by the canonical validate run (the engine excludes __fixtures__/**); it is asserted against failure by src/__tests__/integration.test.ts.

Development

pnpm build
pnpm test

Relationship to Comity Standards

  • layering-policy.md
  • architecture-validation.md
  • ADR-008, ADR-026
  • adapters.md §13 (adapter-peer engine)