sindresorhus/ow

Function argument validation for humans

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Type:Library / SDKCategory(s):Core & Utility LibrariesLanguages & Runtimes
Added to GitGenius on September 17th, 2026
Created on September 29th, 2017
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Enabled
Number of forks: 111
Total Stargazers: 3,863 (+0)
Total Subscribers: 21 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.8 days
Mean response time: 270.4 days
90th percentile: 1234.6 days
Tracked items: 37

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

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

Top labels

  • help wanted (14)
  • enhancement (9)
  • bug (3)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

ow is a function argument validation library that provides human-readable assertions for TypeScript and JavaScript.

The library solves the problem of validating function arguments with clear, expressive syntax. Rather than writing conditional checks and throwing generic errors, developers use ow's chainable API to declare what types and constraints arguments must satisfy. When validation fails, the library produces detailed error messages that pinpoint exactly what went wrong and what was expected.

The tool suits projects where argument validation errors need to be immediately understandable to developers debugging code. It works well in codebases that prioritize readable error messages over minimal dependencies, and in TypeScript projects where type information can be leveraged for validation. Teams building libraries or APIs that receive untrusted input benefit from ow's ability to fail fast with informative messages. The library is particularly valuable when validation logic would otherwise clutter function bodies with repetitive conditional statements.

The project maintains a steady stream of issue responses and pull request reviews, with maintainers actively engaging on reported problems and proposed changes. Updates arrive regularly to address edge cases, improve error messages, and expand validation capabilities. The codebase shows consistent attention to test coverage and documentation quality, ensuring that new features integrate smoothly with existing functionality.