Repo brief: ajv-validator/ajv

Generated by RepoPilot · document generated 2026-09-17 · concise human review Evidence snapshot · analyzed 2026-09-17T03:55:54.089Z · commit f177fe323420

Verdict

Healthy — Healthy across all four use cases

• Last commit 3mo ago
• 34+ active contributors
• Distributed ownership (top contributor 28% of recent commits)
• MIT licensed
• 2 more receipts on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

What it is

Ajv is a high-performance JSON Schema validator for Node.js and browsers that compiles schemas into optimized validation functions. It supports JSON Schema drafts 04/06/07/2019-09/2020-12 and JSON Type Definition (RFC 8927), generating fast validator code through a code-generation engine rather than interpreting schemas at runtime. Monolithic TypeScript project: lib/compile/ contains the core code-generation engine with subdirectories for codegen logic (lib/compile/codegen/), validation rules (lib/compile/validate/), and JSON Type Definition support (lib/compile/jtd/). lib/refs/ holds normative JSON Schema meta-schemas for each draft. Separate entry points (lib/2019.ts,…

Start here

Open these first:

• lib/ajv.ts — Main entry point and core Ajv class definition; required to understand the public API and initialization flow.
• lib/compile/index.ts — Schema compilation orchestrator that translates JSON schemas into validator functions; central to the validation engine.
• lib/compile/codegen/index.ts — Code generation system that produces optimized validation code; load-bearing for performance claims.
• lib/vocabularies/applicator/index.ts — Applicator vocabulary implementation managing schema keywords like allOf, anyOf, oneOf; core validation logic.
• lib/compile/validate/index.ts — Validation rule orchestration that applies schema keywords to data; bridges compilation and runtime.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

git clone https://github.com/ajv-validator/ajv.git
cd ajv
npm install
npm run build
npm test

Daily commands:

npm run test
```for full test suite (runs json-tests, linting, and code coverage).
```bash
npm run test-spec
```for unit tests only.
```bash
npm run test-browser
```for browser testing via Karma.
```bash
npm run build
```to compile TypeScript to `dist/` and copy schema refs.

## Key cautions & unknowns

- Slowing — last commit 3mo ago
- Scorecard: marked unmaintained (0/10)
- **ts-node requirement for tests**: The test scripts use `TS_NODE_PROJECT=spec/tsconfig.json` pointing to a separate TypeScript config in `spec/` — running mocha directly on TypeScript specs without ts-node will fail.…
- Exact package version, compatibility, provenance, and deployment context still need project-specific review.

## Sources

- [Repository source](https://github.com/ajv-validator/ajv)
- [Open issues](https://github.com/ajv-validator/ajv/issues)
- [Recent pull requests](https://github.com/ajv-validator/ajv/pulls)
- [OpenSSF Scorecard](https://scorecard.dev/viewer/?uri=github.com/ajv-validator/ajv)

## Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

_For the complete agent context, use the CLAUDE.md or Cursor rules export._