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

@damnthonyy/json-schema-validate

v1.1.3

Published

JSON Schema and OpenAPI validator using Spectral and swagger-parser

Readme

json-schema-validate

CI npm version

A lightweight OpenAPI and JSON Schema validator that combines swagger-parser and Spectral.

Why?

Problem: Neither tool alone is complete:

  • swagger-parser detects circular references but doesn't flag them as violations
  • Spectral doesn't handle circular references correctly

Solution: This package merges both:

  1. swagger-parser → Structural validation (broken refs, format errors, circular detection)
  2. Spectral → Quality rules (OAS compliance, custom rules)

Installation

npm install @damnthonyy/json-schema-validate

Usage

import { validateSchema } from '@damnthonyy/json-schema-validate';

const spec = {
  openapi: '3.0.0',
  info: { title: 'My API', version: '1.0.0' },
  paths: {
    '/users': {
      get: {
        responses: {
          '200': {
            description: 'List of users',
            content: {
              'application/json': {
                schema: { $ref: '#/components/schemas/User' }
              }
            }
          }
        }
      }
    }
  },
  components: {
    schemas: {
      User: {
        type: 'object',
        properties: {
          id: { type: 'integer' },
          name: { type: 'string' }
        }
      }
    }
  }
};

const result = await validateSchema(spec);

if (result.valid) {
  console.log('✅ Spec is valid');
} else {
  result.issues.forEach(issue => {
    console.log(`[${issue.severity}] ${issue.source}: ${issue.message}`);
    console.log(`  at: ${issue.path}`);
  });
}

Response

interface ValidationResult {
  valid: boolean;
  issues: ValidationIssue[];
}

interface ValidationIssue {
  path: string;                              // JSON Pointer path
  message: string;                           // Error message
  severity: 'error' | 'warning' | 'info';   // Severity level
  source: 'swagger-parser' | 'spectral';    // Which validator found it
}

What Gets Validated

Structural Issues (swagger-parser)

  • ✅ Broken $ref references
  • ✅ Circular references (Pet → Owner → Pet)
  • ✅ Invalid OpenAPI format
  • ✅ Missing required fields

Quality Issues (Spectral)

  • ✅ Empty descriptions
  • ✅ Missing types in schemas
  • ✅ OAS compliance rules
  • ✅ Custom rules (extensible)

Customizing Rules

Edit rules/spectral.ruleset.yaml:

extends:
  - spectral:oas

rules:
  no-empty-description:
    description: Descriptions must not be empty
    given: "$..description"
    severity: warn
    then:
      function: pattern
      functionOptions:
        match: ".+"

Testing

npm run test:run

Contributing

Found a bug or want to suggest an improvement? Open an issue

License

MIT