ibm/openapi-validator

Configurable and extensible validator/linter for OpenAPI documents

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 21 minutes ago
Added to GitGenius on August 16th, 2026
Created on October 15th, 2018
Open Issues & Pull Requests: 27 (+0)
GitHub issues: Enabled
Number of forks: 98
Total Stargazers: 634 (+0)
Total Subscribers: 19 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 27.2 hours
Mean response time: 9.6 days
90th percentile: 12.4 days
Tracked items: 25

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 12% of issues opened in the past year have been closed. Three people close 61% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 5
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 507 days
Stale 30+ days: 5
Stale 90+ days: 4

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • released (5)
  • bug (2)
  • pr welcome (1)
  • question (1)
  • semantic-release (1)
  • windows (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

OpenAPI Validator is a configurable and extensible linter for OpenAPI documents that validates compliance with OpenAPI 3.0.x and 3.1.x specifications.

The tool analyzes API definitions and reports problems found within them. It works by applying a set of validation rules to your OpenAPI document, with the ability to customize which rules apply and how strictly they are enforced. By default, it uses the IBM Cloud Validation Ruleset, but it can detect and use standard Spectral ruleset files if present in your project directory or parent directories. You can also explicitly specify a custom ruleset or force use of the default ruleset when alternatives exist. The validator supports both command-line and programmatic usage, with configurable output formats including text and JSON, and can generate markdown reports.

Teams should choose this tool if they need to enforce OpenAPI compliance standards across their API definitions, particularly those already using IBM Cloud practices or Spectral rulesets. It suits projects where API governance and consistency matter, whether you want to apply industry standards or custom organizational rules. The tool's support for Spectral rulesets means it integrates with existing Spectral-based workflows. Installation options include NPM, executable binaries, building from source, or running as a container image, making it flexible for different deployment scenarios.

The project maintains active development with regular updates to support evolving OpenAPI specifications. The codebase shows consistent refinement of validation rules and configuration options. Documentation is comprehensive, covering installation methods, configuration properties, output customization, and programmatic integration. The tool includes security considerations documented in the repository and supports extensibility through custom rules, allowing teams to adapt it to their specific compliance needs.