Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-16 01:12 UTC

json-structure / sdk

Official SDKs for JSON Structure schema and instance validation

C · TypeScript · C#MIT★ 23 stars⑂ 1 forksince Nov 2025View on GitHub ↗
KindLibraryCommand-line toolhow this is determined
#data-validation#dotnet#golang#java#json-schema#json-structure#python#rust#schema-validation#sdk#typescript#validation-library

json-structure/sdk holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Vitality (79/100) and lowest on Security (33/100). It was last updated 1 day ago. 2 contributors account for most of its recent work.

69
overall / 100
Good

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.

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

Ownership

JSON Structure Working GroupOrganization
45 followers11 public repossince Mar 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistjson-structure/sdkv0.8.01102 days agojsonschemavalidationjson-structuretype-system
Gogithub.com/json-structure/sdk/gov0.8.0-72 days ago—
Mavenorg.json-structure:json-structure0.8.0-302 days ago—
PyPIjson-structure0.8.0-282 days agojsonjson-structureschematype-systemvalidation
RubyGemsjsonstructure0.8.0-82 days ago—
crates.iojson-structure0.6.0918169 days agojsontypesvalidationschemaencodingparser-implementations
npm@json-structure/sdk0.7.02133037 days agojsonschemavalidationjson-structuretypescript
npmjson-structurepoints to another repo — not scored0.2.0624051 days agocomparejsonstructure

Metrics by category

Vitality

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

79Good · 21% of overall

Development activity

65Good
How it's scored
36/36Push recency — last push 1 days ago
4.2/36Commit cadence — 6/52 weeks with commits
18/18Commit volume — 292 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year292
human_commit_share—
days_since_last_push1
active_weeks_last_year6

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 7 releases published
36/36Release recency — latest release 2 days ago
27/27Release cadence — a release every ~36 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count7
latest_release_tagjstruct-v0.8.0
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases36

Community & Adoption

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

35Weak · 17% of overall

Popularity & adoption

22At Risk
How it's scored
21.8/60Stars — 23 stars
0/25Forks — 1 forks
0/15Watchers — 0 watchers
Inputs used
forks1
stars23
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

50Moderate
How it's scored
22.5/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_readmeyes
has_licenseyes
readme_badges—
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno

Ecosystem adoption (downloads)

33At Risk
How it's scored
33.1/80Monthly downloads — 305 downloads/month across crates, go, maven, npm, packagist, pypi, rubygems
0/20Registry dependents — 0 packages depend on it
Inputs used
packagesjson-structure/sdk, github.com/json-structure/sdk/go, org.json-structure:json-structure, json-structure, jsonstructure, json-structure, @json-structure/sdk
dependents0
ecosystemscrates, go, maven, npm, packagist, pypi, rubygems
total_downloads2,625
monthly_downloads305
unverified_packages_excluded—

Sustainability & Governance

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

73Good · 23% of overall

Maintainer resilience (bus factor)

47Weak
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12.8/22.5Commit distribution — top contributor authored 43% of commits
4.1/13.5Contributor breadth — 3 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor2
contributors_sampled3
top_contributor_share0.433

Issue & PR responsiveness

79Good
How it's scored
36.2/42Issue resolution — 86% of issues closed
20.6/30PR acceptance — 81/118 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs81
open_issues5
closed_issues31
prs_merged_7d—
prs_decided_7d—
prs_merged_30d—
prs_decided_30d—
issue_closed_ratio0.861
closed_unmerged_prs37
first_time_authors_30d—
first_time_prs_merged_30d—
first_time_prs_decided_30d—
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

77Good
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain — verified-domain status not read for this organization
12/25Owner reach — 45 followers of json-structure
19.9/25Track record — 11 public repos, account ~9 yr old
Inputs used
followers45
owner_typeOrganization
is_verified—
owner_loginjson-structure
public_repos11
account_age_days3,415
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 7 package(s) on crates, go, maven, npm, packagist, pypi, rubygems
35/35Publish recency — latest publish 2 days ago
20/20Version history — 30 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesjson-structure/sdk, github.com/json-structure/sdk/go, org.json-structure:json-structure, json-structure, jsonstructure, json-structure, @json-structure/sdk
ecosystemscrates, go, maven, npm, packagist, pypi, rubygems
any_deprecatedno
min_days_since_publish2

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall

Engineering practices

80Excellent
How it's scored
24/24CI workflows — 14 workflow(s)
24/24Tests present
16/16Linter config — .eslintrc.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

75Good
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://docs.rs/json-structure
10/10Repository description
10/10Topics — 12 topics
10/10Wiki
Inputs used
topicsdata-validation, dotnet, golang, java, json-schema, json-structure, python, rust, schema-validation, sdk, typescript, validation-library
has_wikiyes
homepage—
docs_sitehttps://docs.rs/json-structure
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

33At Risk · 16% of overall

Security posture

33At Risk
How it's scored
0/30Security policy (SECURITY.md)
25/25Dependabot config
0/25Dependency lockfiles — published library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilesCargo.lock, package-lock.json
manifestscomposer.json, go/go.mod, java/pom.xml, php/composer.json, python/pyproject.toml, ruby/Gemfile, rust/Cargo.toml, typescript/package.json, vscode/package.json
has_codeql_workflowno
has_security_policyno
has_dependabot_configyes
Excluded from scoring (no data or not applicable): Dependency lockfiles. Remaining weights renormalized.

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.

59Moderate · 4% of overall

Agent context & guidance

1Critical
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no data
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share—
agent_instruction_files—
agent_instruction_max_bytes—
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.

Verify loop (build / test / typecheck)

74Good
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .eslintrc.json
11/11Static type checking — typescript/tsconfig.json, vscode/tsconfig.json
10/10Reproducible environment — devcontainer, lockfile
0/10Demonstrated agent practice — no data
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock, package-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontaineryes
has_linter_configyes
typecheck_configstypescript/tsconfig.json, vscode/tsconfig.json
agent_commit_share—
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.

Code legibility for models

95Exceptional
How it's scored
45/45Type-checkable code — C (statically typed)
50.1/55Manageable file sizes — 21/235 source files over 60KB
Inputs used
primary_languageC
largest_source_bytes158,920
source_files_sampled235
oversized_source_files21

Machine-readable interfaces

100Exceptional
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

23GitHub stars
3contributors
292commits, last 12 months
1days since last push
7releases
2bus factor
5open issues
crates.io, Go, Maven, npm, Packagist, PyPI, RubyGemspackage ecosystems

Data collection warnings

  • npm package 'json-structure' points at a different repository (https://github.com/materik/json-structure.git); excluded from ecosystem scoring
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

More detail

Direct dependencies 15
RegistryPackageVersion constraintManifest
Mavencom.fasterxml.jackson.core:jackson-core${jackson.version}java/pom.xml
Mavencom.fasterxml.jackson.core:jackson-databind${jackson.version}java/pom.xml
Mavencom.fasterxml.jackson.core:jackson-annotations${jackson.version}java/pom.xml
Mavencom.fasterxml.jackson.datatype:jackson-datatype-jsr310${jackson.version}java/pom.xml
crates.ioserde1.0rust/Cargo.toml
crates.ioserde_json1.0rust/Cargo.toml
crates.iothiserror2.0rust/Cargo.toml
crates.ioregex1.12rust/Cargo.toml
crates.iochrono0.4rust/Cargo.toml
crates.iouuid1.20rust/Cargo.toml
crates.iourl2.5rust/Cargo.toml
crates.iobase640.22rust/Cargo.toml
crates.ioindexmap2.13rust/Cargo.toml
crates.ioclap4.5rust/Cargo.toml
npm@json-structure/sdkfile:../typescriptvscode/package.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with json-structure/sdk. Read them side by side →

98valkey-io/valkey-glideAn open source Valkey client library that supports Valkey, and Redis open source 6.2, 7.0 and 7.2. Valkey GLIDE is designed for reliability, optimized performance, and high-availability, for Valkey and Redis OSS based applications. GLIDE is a multi language client library, written in Rust with programming language bindings, such as Java and PythonExceptional98microsoft/kiotaOpenAPI based HTTP Client code generatorExceptional98pulumi/pulumiPulumi - Infrastructure as Code in any programming language 🚀Exceptional98microsoft/aspireAspire is the tool for code-first, extensible, observable dev and deploy.Exceptional99taskforcesh/bullmqBullMQ - Message Queue and Batch processing for NodeJS, Python, .NET, Elixir, Rust and PHP based on Redis or PostgreSQLExceptional99Qiskit/qiskitQiskit is an open-source SDK for working with quantum computers at the level of extended quantum circuits, operators, and primitives.Exceptional

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.11.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — Packagist, Go, Maven, PyPI, RubyGems, crates.io, npm.