Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-27 13:08 UTC

Redocly / ajv

The fastest JSON Schema Validator. Supports draft-04/06/07

TypeScriptMIT★ 2 stars⑂ 2 forkssince Jun 2020forkView on GitHub ↗

Redocly/ajv holds a health index of 59 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (64/100) and lowest on Community & Adoption (34/100). It was last updated 142 days ago. A single contributor accounts for most of its recent work.

59
overall / 100
Moderate

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.

59
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 56 is calibrated to 59 on the published index scale (record calibration 2026-08-02).

Ownership

RedoclyOrganization
381 followers41 public repossince Sep 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@redocly/ajv8.18.334,972,90022142 days agojsonschemavalidatorvalidationjsonschemajson-schemajson-schema-validatorjson-schema-validation

Metrics by category

Vitality

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

52Moderate · 21% of overall
How it's scored
9.9/36Push recency — last push 142 days ago
6.2/36Commit cadence — 9/52 weeks with commits
10.8/18Commit volume — 15 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year15
human_commit_share0.94
days_since_last_push142
active_weeks_last_year9
How it's scored
27/27Ships releases — 9 releases published
27/36Release recency — latest release 142 days ago
27/27Release cadence — a release every ~19.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count9
latest_release_tagv8.18.3
releases_from_tagsno
days_since_latest_release142
mean_days_between_releases19.8
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?

34At Risk · 17% of overall
How it's scored
0/60Stars — 2 stars
0/25Forks — 2 forks
0/15Watchers — 1 watchers
Inputs used
forks2
stars2
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeno
has_licenseno
readme_badges33
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescoveralls.io, github.com, opencollective.com, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 34,972,900 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@redocly/ajv
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads34,972,900
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?

64Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
3.1/22.5Commit distribution — top contributor authored 86% of commits
13.5/13.5Contributor breadth — 97 contributors
10/10OpenSSF Scorecard: Contributors — project has 29 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled97
top_contributor_share0.863
How it's scored
0/42Issue resolution — no issues or no data
17.6/30PR acceptance — 27/46 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
9/15OpenSSF Scorecard: Code-Review — Found 20/30 approved changesets -- score normalized to 6
Inputs used
merged_prs27
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs19
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
18.6/25Owner reach — 381 followers of Redocly
23.8/25Track record — 41 public repos, account ~8 yr old
Inputs used
followers381
owner_typeOrganization
is_verifiedno
owner_loginRedocly
public_repos41
account_age_days3,263

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 142 days ago
20/20Version history — 22 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@redocly/ajv
ecosystemsnpm
any_deprecatedno
min_days_since_publish142

Engineering Quality

Are baseline engineering and documentation practices in place?

64Moderate · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — .eslintrc.js, .eslintrc.yml, package.json ("prettier")
0/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests — 17 out of 20 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
0/30README
25/25Documentation directory
15/15Documentation / homepage site — https://ajv.js.org
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepagehttps://ajv.js.org
docs_sitehttps://ajv.js.org
has_readmeno
has_docs_diryes
has_descriptionno

Security

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

63Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2/2.5CI-Tests — 17 out of 20 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-Review — Found 20/30 approved changesets -- score normalized to 6
2.5/2.5Contributors — project has 29 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
4/5SAST — SAST tool is not run on all commits -- score normalized to 8
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.4
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 advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no 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:@redocly/ajv@8.18.3 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 instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
39.7/40Legible commit history — 70 of 94 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.745
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, package.json ("prettier")
11/11Static type checking — spec/tsconfig.json, tsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 6 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency 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.06
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/213 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes39,727
source_files_sampled213
oversized_source_files0

Key facts

2GitHub stars
97contributors
15commits, last 12 months
142days since last push
9releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 5.4 / 10
5.4aggregate

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-27 13:07 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
8CI-Tests17 out of 20 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 20/30 approved changesets -- score normalized to 6
10Contributorsproject has 29 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update 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
8SASTSAST tool is not run on all commits -- score normalized to 8
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
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
npmif-node-version^1.1.1indirect
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:@redocly/ajv@8.18.3 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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm.