Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-14 22:00 UTC

networknt / json-schema-validator

A fast Java JSON schema validator that supports draft V4, V6, V7, V2019-09 and V2020-12

JavaApache-2.0★ 1,080 stars⑂ 352 forkssince Sep 2016View on GitHub ↗
KindLibraryApplicationhow this is determined

networknt/json-schema-validator holds a health index of 88 out of 100, placing it in the Excellent band. It scores highest on Vitality (87/100) and lowest on AI Readiness (57/100). It was last updated today. A single contributor accounts for most of its recent work.

88
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.

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

Ownership

networkntOrganization
49 followers57 public repossince Sep 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Mavencom.networknt:json-schema-validator3.0.7-15225 days ago

Metrics by category

Vitality

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

87Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
16.6/36Commit cadence — 24/52 weeks with commits
15.5/18Commit volume — 52 commits in the last year
10/10OpenSSF Scorecard: Maintained — 20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year52
human_commit_share1
days_since_last_push0
active_weeks_last_year24

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 25 days ago
27/27Release cadence — a release every ~9.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tag2.0.7
releases_from_tagsno
days_since_latest_release25
mean_days_between_releases9.4
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?

65Good · 17% of overall
How it's scored
49.2/60Stars — 1,080 stars
21.2/25Forks — 352 forks
8.7/15Watchers — 37 watchers
Inputs used
forks352
stars1,080
watchers37
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges9
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, github.com, shields.io
has_pull_request_templateno

Sustainability & Governance

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

72Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
10.9/22.5Commit distribution — top contributor authored 52% of commits
13.5/13.5Contributor breadth — 99 contributors
10/10OpenSSF Scorecard: Contributors — project has 13 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled99
top_contributor_share0.516
How it's scored
41.6/42Issue resolution — 99% of issues closed
27.6/30PR acceptance — 512/557 decided PRs merged
13/13Newcomer PR acceptance — 6/6 first-time contributors' PRs merged in 30d
7.5/15OpenSSF Scorecard: Code-Review — Found 16/30 approved changesets -- score normalized to 5
Inputs used
merged_prs512
open_issues7
closed_issues680
prs_merged_7d1
prs_decided_7d1
prs_merged_30d6
prs_decided_30d6
issue_closed_ratio0.99
closed_unmerged_prs45
first_time_authors_30d3
first_time_prs_merged_30d6
first_time_prs_decided_30d6
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
12.2/25Owner reach — 49 followers of networknt
24.8/25Track record — 57 public repos, account ~12 yr old
Inputs used
followers49
owner_typeOrganization
is_verifiedno
owner_loginnetworknt
public_repos57
account_age_days4,386

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on maven
35/35Publish recency — latest publish 25 days ago
20/20Version history — 152 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagescom.networknt:json-schema-validator
ecosystemsmaven
any_deprecatedno
min_days_since_publish25

Engineering Quality

Are baseline engineering and documentation practices in place?

81Excellent · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — tox.ini
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
8/20OpenSSF Scorecard: CI-Tests — 9 out of 19 merged PRs checked by a CI test -- score normalized to 4
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 18 topics
10/10Wiki
Inputs used
topicsjson-schema-validator, json-schema, fast, java8, draft, v4, jackson, java, v6, v7, v2019-09, draftv4, draftv6, draftv7, json, yaml, openapi3, v2020-12
has_wikiyes
homepage—
docs_site—
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-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
1/2.5CI-Tests — 9 out of 19 merged PRs checked by a CI test -- score normalized to 4
0/2.5CII-Best-Practices — no data
3.8/7.5Code-Review — Found 16/30 approved changesets -- score normalized to 5
2.5/2.5Contributors — project has 13 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
5.2/7.5Vulnerabilities — 3 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate5.8
Excluded from scoring (no data or not applicable): Branch-Protection, CII-Best-Practices, 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_packages7
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 maven:com.networknt:json-schema-validator@3.0.7 runtime dependency closure — what installing the published package pulls in — 7 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.

57Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
32/40Legible commit history — 60 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.6
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — pom.xml (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config — tox.ini
11/11Static type checking — Java (statically typed)
0/10Reproducible environment
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
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_configs—
agent_commit_share0.01
toolchain_manifestspom.xml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Java (statically typed)
54.7/55Manageable file sizes — 2/424 source files over 60KB
Inputs used
primary_languageJava
largest_source_bytes112,822
source_files_sampled424
oversized_source_files2

Key facts

1,080GitHub stars
99contributors
52commits, last 12 months
0days since last push
100releases
1bus factor
7open issues
Mavenpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 352 ⇿
0Stars
352Forks
97Releases

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.

012525037535052016-102021-092026-08
Major 2Minor 5Patch 90

Each point covers 9 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-09-14 22:00 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
4CI-Tests9 out of 19 merged PRs checked by a CI test -- score normalized to 4
n/aCII-Best-Practicesinternal error: error during json parsing: error during json.Unmarshal: invalid character '<' looking for beginning of value
5Code-ReviewFound 16/30 approved changesets -- score normalized to 5
10Contributorsproject has 13 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
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
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7Vulnerabilities3 existing vulnerabilities detected
Direct dependencies 9
RegistryPackageVersion constraintManifest
Mavencom.ethlo.time:itu${version.itu}pom.xml
Maventools.jackson.core:jackson-databind${version.jackson}pom.xml
Maventools.jackson.dataformat:jackson-dataformat-yaml${version.jackson}pom.xml
Mavenorg.jruby.joni:joni${version.joni}pom.xml
Mavenorg.graalvm.js:js-language${version.graaljs}pom.xml
Mavenorg.graalvm.truffle:truffle-runtime${version.graaljs}pom.xml
Mavenorg.graalvm.sdk:graal-sdk${version.graaljs}pom.xml
Mavenorg.slf4j:slf4j-api${version.slf4j}pom.xml
Mavenme.fabriciorby:maven-surefire-junit5-tree-reporter${version.maven-surefire-junit5-tree-reporter}pom.xml
All dependencies 25

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

RegistryPackageVersionRelation
Mavencom.ethlo.time:itu1.14.0direct
Mavenme.fabriciorby:maven-surefire-junit5-tree-reporter1.5.1direct
Mavenorg.graalvm.js:js-language25.0.1direct
Mavenorg.graalvm.sdk:graal-sdk25.0.1direct
Mavenorg.graalvm.truffle:truffle-runtime25.0.1direct
Mavenorg.jruby.joni:joni2.2.6direct
Mavenorg.slf4j:slf4j-api2.0.17direct
Maventools.jackson.core:jackson-databind3.2.1direct
Maventools.jackson.dataformat:jackson-dataformat-yaml3.2.1direct
Mavench.qos.logback:logback-classic1.5.22indirect
Mavenorg.apache.felix:maven-bundle-plugin6.0.0indirect
Mavenorg.apache.maven.plugins:maven-compiler-plugin3.14.1indirect
Mavenorg.apache.maven.plugins:maven-gpg-plugin3.2.7indirect
Mavenorg.apache.maven.plugins:maven-javadoc-plugin3.12.0indirect
Mavenorg.apache.maven.plugins:maven-source-plugin3.4.0indirect
Mavenorg.apache.maven.plugins:maven-surefire-plugin3.5.4indirect
Mavenorg.apache.maven.plugins:maven-surefire-report-plugin3.5.4indirect
Mavenorg.hamcrest:hamcrest3.0indirect
Mavenorg.jacoco:jacoco-maven-plugin0.8.14indirect
Mavenorg.junit.jupiter:junit-jupiter-engine6.0.1indirect
Mavenorg.junit.jupiter:junit-jupiter-params6.0.1indirect
Mavenorg.moditect:moditect-maven-plugin1.2.2indirect
Mavenorg.openjdk.jmh:jmh-core1.37indirect
Mavenorg.openjdk.jmh:jmh-generator-annprocess1.37indirect
Mavenorg.sonatype.central:central-publishing-maven-plugin0.7.0indirect
Dependency advisories 0

Installing maven:com.networknt:json-schema-validator@3.0.7 pulls in 7 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 — Maven.