Public record
Software health reportschema 0.30.0 · metrics 2.10.0 · 2026-08-04 17:35 UTC

ajv-validator / ajv

The fastest JSON schema Validator. Supports JSON Schema draft-04/06/07/2019-09/2020-12 and JSON Type Definition (RFC8927)

TypeScriptMIT★ 14,793 stars⑂ 1,012 forkssince May 2015View on GitHub ↗

ajv-validator/ajv holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (98/100) and lowest on Vitality (46/100). It was last updated 84 days ago. A single contributor accounts for most of its recent work.

83
overall / 100
Excellent

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

83
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 70 is calibrated to 83 on the published index scale (record calibration 2026-08-02).

Ownership

84 followers15 public repossince Jan 2019

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmajv8.20.01,396,275,754359102 days agojsonschemavalidatorvalidationjsonschemajson-schemajson-schema-validatorjson-schema-validation

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

46Weak · 21% of overall
How it's scored
18/36Push recencylast push 84 days ago
1.4/36Commit cadence2/52 weeks with commits
8.6/18Commit volume8 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year8
human_commit_share0.86
days_since_last_push84
active_weeks_last_year2
How it's scored
27/27Ships releases100 releases published
27/36Release recencylatest release 102 days ago
12.6/27Release cadencea release every ~134.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv8.20.0
releases_from_tagsno
days_since_latest_release102
mean_days_between_releases134.1
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

98Exceptional · 17% of overall
How it's scored
60/60Stars14,793 stars
25/25Forks1,012 forks
11.3/15Watchers110 watchers
Inputs used
forks1,012
stars14,793
watchers110
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

100Exceptional
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
7.2/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges33
has_contributingyes
has_issue_templateyes
has_code_of_conductyes
readme_badge_servicescoveralls.io, github.com, opencollective.com, shields.io
has_pull_request_templateyes
How it's scored
80/80Monthly downloads1,396,275,754 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesajv
dependents
ecosystemsnpm
total_downloads
monthly_downloads1,396,275,754
unverified_packages_excluded
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

70Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
3.1/22.5Commit distributiontop contributor authored 86% of commits
13.5/13.5Contributor breadth97 contributors
10/10OpenSSF Scorecard: Contributorsproject has 26 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled97
top_contributor_share0.863
How it's scored
35.1/42Issue resolution84% of issues closed
18.1/30PR acceptance482/798 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
12/15OpenSSF Scorecard: Code-ReviewFound 25/30 approved changesets -- score normalized to 8
Inputs used
merged_prs482
open_issues285
closed_issues1,446
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.835
closed_unmerged_prs316
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
13.9/25Owner reach84 followers of ajv-validator
20.8/25Track record15 public repos, account ~7 yr old
Inputs used
followers84
owner_typeOrganization
is_verified
owner_loginajv-validator
public_repos15
account_age_days2,754
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 102 days ago
20/20Version history359 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesajv
ecosystemsnpm
any_deprecatedno
min_days_since_publish102

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter config.eslintrc.js, .eslintrc.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
2/20OpenSSF Scorecard: CI-Tests5 out of 27 merged PRs checked by a CI test -- score normalized to 1
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://ajv.js.org
10/10Repository description
10/10Topics3 topics
0/10Wiki
Inputs used
topicsjson-schema, validator, ajv
has_wikino
homepagehttps://ajv.js.org
docs_sitehttps://ajv.js.org
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

66Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0.2/2.5CI-Tests5 out of 27 merged PRs checked by a CI test -- score normalized to 1
0.5/2.5CII-Best-Practicesbadge detected: InProgress
6/7.5Code-ReviewFound 25/30 approved changesets -- score normalized to 8
2.5/2.5Contributorsproject has 26 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.8
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages4
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:ajv@8.20.0 runtime dependency closure — what installing the published package pulls in — 4 packages. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

56Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history70 of 86 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.814
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.eslintrc.js, .eslintrc.yml
11/11Static type checkingspec/tsconfig.json, tsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance14 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configsspec/tsconfig.json, tsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.14
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/205 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes39,726
source_files_sampled205
oversized_source_files0

Key facts

14,793GitHub stars
97contributors
8commits, last 12 months
84days since last push
100releases
1bus factor
285open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 1,012 ⇿
0Stars
1,012Forks
100Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

02004006008001,000992202015-072021-012026-07
Major 3Minor 39Patch 31

Each point covers 11 days.

OpenSSF Scorecard 5.8 / 10
5.8aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-08-04 17:35 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
1CI-Tests5 out of 27 merged PRs checked by a CI test -- score normalized to 1
2CII-Best-Practicesbadge detected: InProgress
8Code-ReviewFound 25/30 approved changesets -- score normalized to 8
10Contributorsproject has 26 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
npmfast-deep-equal^3.1.3package.json
npmfast-uri^3.0.1package.json
npmjson-schema-traverse^1.0.0package.json
npmrequire-from-string^2.0.2package.json
All dependencies 45

Full resolved dependency set from the GitHub dependency graph: 4 direct and 41 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
npmfast-deep-equal^3.1.3direct
npmfast-uri^3.0.1direct
npmjson-schema-traverse^1.0.0direct
npmrequire-from-string^2.0.2direct
npm@ajv-validator/config^0.5.0indirect
npm@rollup/plugin-commonjs^25.0.7indirect
npm@rollup/plugin-json^6.1.0indirect
npm@rollup/plugin-node-resolve^15.2.3indirect
npm@rollup/plugin-typescript^11.1.6indirect
npm@types/chai^4.3.11indirect
npm@types/mocha^10.0.6indirect
npm@types/node^20.11.30indirect
npm@types/require-from-string^1.2.3indirect
npm@typescript-eslint/eslint-plugin^7.3.1indirect
npm@typescript-eslint/parser^7.3.1indirect
npmajv-formats^3.0.1indirect
npmbenchmark^2.1.4indirect
npmbrowserify^17.0.0indirect
npmchai^4.4.1indirect
npmcross-env^7.0.3indirect
npmdayjs^1.11.10indirect
npmdayjs-plugin-utc^0.1.2indirect
npmeslint^8.57.0indirect
npmeslint-config-prettier^9.1.0indirect
npmglob^10.3.10indirect
npmhusky^9.0.11indirect
npmjimp^0.22.10indirect
npmjs-beautify^1.15.1indirect
npmjson-schema-test^2.0.0indirect
npmkarma^6.4.2indirect
npmkarma-chrome-launcher^3.2.0indirect
npmkarma-mocha^2.0.1indirect
npmlint-staged^15.2.2indirect
npmmocha^10.3.0indirect
npmmodule-from-string^3.3.0indirect
npmnode-fetch^3.3.2indirect
npmnyc^15.1.0indirect
npmprettier3.0.3indirect
npmre2^1.20.9indirect
npmrollup^2.79.1indirect
npmrollup-plugin-terser^7.0.2indirect
npmts-node^10.9.2indirect
npmtsify^5.0.4indirect
npmtypescript5.3.3indirect
npmuri-js^4.4.1indirect
Dependency advisories 0

Installing npm:ajv@8.20.0 pulls in 4 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.30.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.