Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-31 11:03 UTC

StefanTerdell / zod-to-json-schema

Converts Zod schemas to Json schemas

TypeScriptISC★ 1,251 stars⑂ 93 forkssince Feb 2021archivedView on GitHub ↗

StefanTerdell/zod-to-json-schema holds a health index of 19 out of 100, placing it in the Critical band. It scores highest on Community & Adoption (78/100) and lowest on Engineering Quality (34/100). The repository is archived, so no further maintenance is expected.

19
overall / 100
Critical

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.

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

Ownership

Stefan TerdellPersonal account
39 followers59 public repossince Jan 2018

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmzod-to-json-schema3.25.2238,174,16991157 days agozodjsonschemaopenapiconversion

Metrics by category

Vitality

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

38Weak · 21% of overall
How it's scored
9.9/36Push recencylast push 157 days ago
2.8/36Commit cadence4/52 weeks with commits
10.3/18Commit volume13 commits in the last year
0/10OpenSSF Scorecard: Maintainedproject is archived
Inputs used
commits_last_year13
human_commit_share1
days_since_last_push157
active_weeks_last_year4
How it's scored
27/27Ships releases6 releases published
0/36Release recencylatest release 1,297 days ago
27/27Release cadencea release every ~33 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count6
latest_release_tag3.20.3
releases_from_tagsno
days_since_latest_release1,297
mean_days_between_releases33
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?

78Good · 17% of overall
How it's scored
50.2/60Stars1,251 stars
16.4/25Forks93 forks
3.9/15Watchers6 watchers
Inputs used
forks93
stars1,251
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (ISC)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads238,174,169 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packageszod-to-json-schema
dependents
ecosystemsnpm
total_downloads
monthly_downloads238,174,169
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?

66Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
10.9/22.5Commit distributiontop contributor authored 51% of commits
13.5/13.5Contributor breadth28 contributors
10/10OpenSSF Scorecard: Contributorsproject has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled28
top_contributor_share0.514
How it's scored
42/42Issue resolution100% of issues closed
21.5/30PR acceptance43/60 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 4/26 approved changesets -- score normalized to 1
Inputs used
merged_prs43
open_issues0
closed_issues123
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs17
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
11.5/25Owner reach39 followers of StefanTerdell
24.9/25Track record59 public repos, account ~8 yr old
Inputs used
followers39
owner_typeUser
is_verified
owner_loginStefanTerdell
public_repos59
account_age_days3,134
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 157 days ago
20/20Version history91 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageszod-to-json-schema
ecosystemsnpm
any_deprecatedno
min_days_since_publish157

Engineering Quality

Are baseline engineering and documentation practices in place?

34At Risk · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 4 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics2 topics
0/10Wiki
Inputs used
topicszod, json-schema
has_wikino
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

45Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Tests0 out of 4 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 4/26 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 5 contributing companies or organizations
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintainedproject is archived
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
0.8/7.5Vulnerabilities9 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate3.1
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories9
affected_packages2
assessed_packages55
unassessed_packages0
affected_by_severityhigh 2
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 55 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

43Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
8.5/40Legible commit history16 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.16
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checkingdist-test-v3/types/tsconfig.json, dist-test-v4/types/tsconfig.json, tsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configsdist-test-v3/types/tsconfig.json, dist-test-v4/types/tsconfig.json, tsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/85 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes24,824
source_files_sampled85
oversized_source_files0

Key facts

1,251GitHub stars
28contributors
13commits, last 12 months
157days since last push
6releases
1bus factor
0open 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 ★ / 93 ⇿
0Stars
93Forks
6Releases

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.

0204060801009232021-052023-092026-01
Major 0Minor 2Patch 4

Each point covers 5 days.

OpenSSF Scorecard 3.1 / 10
3.1aggregate

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-31 11:03 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 4 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 4/26 approved changesets -- score normalized to 1
10Contributorsproject has 5 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintainedproject is archived
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
1Vulnerabilities9 existing vulnerabilities detected
All dependencies 55

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

RegistryPackageVersionRelation
npm../..3.25.2indirect
npm@esbuild/aix-ppc640.25.0indirect
npm@esbuild/android-arm0.25.0indirect
npm@esbuild/android-arm640.25.0indirect
npm@esbuild/android-x640.25.0indirect
npm@esbuild/darwin-arm640.25.0indirect
npm@esbuild/darwin-x640.25.0indirect
npm@esbuild/freebsd-arm640.25.0indirect
npm@esbuild/freebsd-x640.25.0indirect
npm@esbuild/linux-arm0.25.0indirect
npm@esbuild/linux-arm640.25.0indirect
npm@esbuild/linux-ia320.25.0indirect
npm@esbuild/linux-loong640.25.0indirect
npm@esbuild/linux-mips64el0.25.0indirect
npm@esbuild/linux-ppc640.25.0indirect
npm@esbuild/linux-riscv640.25.0indirect
npm@esbuild/linux-s390x0.25.0indirect
npm@esbuild/linux-x640.25.0indirect
npm@esbuild/netbsd-arm640.25.0indirect
npm@esbuild/netbsd-x640.25.0indirect
npm@esbuild/openbsd-arm640.25.0indirect
npm@esbuild/openbsd-x640.25.0indirect
npm@esbuild/sunos-x640.25.0indirect
npm@esbuild/win32-arm640.25.0indirect
npm@esbuild/win32-ia320.25.0indirect
npm@esbuild/win32-x640.25.0indirect
npm@types/json-schema7.0.9indirect
npm@types/node20.9.0indirect
npmajv8.18.0indirect
npmajv-errors3.0.0indirect
npmajv-formats2.1.1indirect
npmbalanced-match4.0.4indirect
npmbrace-expansion5.0.5indirect
npmesbuild0.25.0indirect
npmfast-deep-equal3.1.3indirect
npmfast-diff1.3.0indirect
npmfast-uri3.1.0indirect
npmfsevents2.3.3indirect
npmget-tsconfig4.8.0indirect
npmglob13.0.6indirect
npmjson-schema-traverse1.0.0indirect
npmlocal-ref-resolver0.2.0indirect
npmlru-cache11.2.7indirect
npmminimatch10.2.4indirect
npmminipass7.1.3indirect
npmpackage-json-from-dist1.0.1indirect
npmpath-scurry2.0.2indirect
npmrequire-from-string2.0.2indirect
npmresolve-pkg-maps1.0.0indirect
npmrimraf6.1.3indirect
npmtsx4.19.3indirect
npmtypescript5.1.3indirect
npmundici-types5.26.5indirect
npmzod3.25.76indirect
npmzod4.1.12indirect
Dependency advisories 2

This repository publishes no package the index resolves, so its own dependency graph was assessed — 55 packages, which also include development and test pins that never ship: 2 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
brace-expansion5.0.5indirecthigh45.0.9
fast-uri3.1.0indirecthigh54.1.2

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