Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 00:39 UTC

p1c2u / jsonschema-path

Object-oriented JSONSchema

PythonApache-2.0★ 10 stars⑂ 8 forkssince Aug 2022View on GitHub ↗

p1c2u/jsonschema-path holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Vitality (87/100) and lowest on Community & Adoption (35/100). It was last updated 3 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Artur MaciagPersonal account
30 followers59 public repossince Apr 2012

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
PyPIjsonschema-path0.5.0-2258 days agojsonschemaswaggerspec

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 recencylast push 3 days ago
13.8/36Commit cadence20/52 weeks with commits
18/18Commit volume156 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year156
human_commit_share
days_since_last_push3
active_weeks_last_year20

Release discipline

100Exceptional
How it's scored
27/27Ships releases33 releases published
36/36Release recencylatest release 58 days ago
27/27Release cadencea release every ~10.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count33
latest_release_tag0.5.0
releases_from_tagsno
days_since_latest_release58
mean_days_between_releases10.2
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?

35Weak · 17% of overall
How it's scored
15.5/60Stars10 stars
7/25Forks8 forks
0/15Watchers2 watchers
Inputs used
forks8
stars10
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

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

58Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
6.7/22.5Commit distributiontop contributor authored 70% of commits
5.4/13.5Contributor breadth4 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.701
How it's scored
36.8/42Issue resolution88% of issues closed
23.9/30PR acceptance198/249 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/2 approved changesets -- score normalized to 0
Inputs used
merged_prs198
open_issues3
closed_issues21
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.875
closed_unmerged_prs51
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.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
10.7/25Owner reach30 followers of p1c2u
24.9/25Track record59 public repos, account ~14 yr old
Inputs used
followers30
owner_typeUser
is_verified
owner_loginp1c2u
public_repos59
account_age_days5,195
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 pypi
35/35Publish recencylatest publish 58 days ago
20/20Version history22 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesjsonschema-path
ecosystemspypi
any_deprecatedno
min_days_since_publish58

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter config
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests15 out of 15 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics4 topics
10/10Wiki
Inputs used
topicsjsonschema, object-oriented, path, schema
has_wikiyes
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?

55Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests15 out of 15 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/2 approved changesets -- score normalized to 0
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
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
7.5/7.5Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
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
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
6.8/7.5Vulnerabilities1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.5
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. 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.

46Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno 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.
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config
11/11Static type checkingjsonschema_path/py.typed
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespoetry.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configsjsonschema_path/py.typed
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
27/45Type-checkable codePython with type-check config (jsonschema_path/py.typed)
55/55Manageable file sizes0/32 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes18,737
source_files_sampled32
oversized_source_files0
How it's scored
40/40API schema (OpenAPI/GraphQL/proto)tests/integration/data/v3.0/parent-reference/openapi.yaml, tests/integration/data/v3.0/petstore-separate/spec/openapi.yaml
0/20MCP servernot applicable to this kind of software
0/40Runnable examples
Inputs used
example_dirs
has_mcp_signalno
api_schema_filestests/integration/data/v3.0/parent-reference/openapi.yaml, tests/integration/data/v3.0/petstore-separate/spec/openapi.yaml
interfaces_expected_of
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

10GitHub stars
4contributors
156commits, last 12 months
3days since last push
33releases
1bus factor
3open issues
PyPIpackage ecosystems

More detail

OpenSSF Scorecard 5.5 / 10
5.5aggregate

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-07-17 00:38 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
10CI-Tests15 out of 15 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/2 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow 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
9Vulnerabilities1 existing vulnerabilities detected
Direct dependencies 5
RegistryPackageVersion constraintManifest
PyPIattrs>=22.2.0pyproject.toml
PyPIpathable^0.6.0pyproject.toml
PyPIPyYAML>=5.1pyproject.toml
PyPIrequests^2.31.0pyproject.toml
PyPIreferencing<0.38.0pyproject.toml
All dependencies 71

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

RegistryPackageVersionRelation
PyPIattrs26.1.0direct
PyPIpathable0.6.0direct
PyPIpyyaml6.0.3direct
PyPIreferencing0.37.0direct
PyPIrequests2.34.2direct
PyPIast-serialize0.5.0indirect
PyPIasttokens3.0.0indirect
PyPIblack26.5.1indirect
PyPIcertifi2025.4.26indirect
PyPIcfgv3.4.0indirect
PyPIcharset-normalizer3.4.2indirect
PyPIcli-ui0.19.0indirect
PyPIclick8.1.8indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.14.0indirect
PyPIdecorator5.2.1indirect
PyPIdeptry0.25.1indirect
PyPIdistlib0.3.9indirect
PyPIdocopt0.6.2indirect
PyPIexceptiongroup1.3.0indirect
PyPIexecuting2.2.0indirect
PyPIfilelock3.21.2indirect
PyPIflake87.3.0indirect
PyPIflynt1.0.6indirect
PyPIidentify2.6.10indirect
PyPIidna3.15indirect
PyPIiniconfig2.1.0indirect
PyPIipdb0.13.13indirect
PyPIipython8.18.1indirect
PyPIisort8.0.1indirect
PyPIjedi0.19.2indirect
PyPIlibrt0.11.0indirect
PyPImatplotlib-inline0.1.7indirect
PyPImccabe0.7.0indirect
PyPImypy2.1.0indirect
PyPImypy-extensions1.1.0indirect
PyPInodeenv1.9.1indirect
PyPIpackaging25.0indirect
PyPIparso0.8.4indirect
PyPIpathspec1.0.4indirect
PyPIpexpect4.9.0indirect
PyPIplatformdirs4.3.8indirect
PyPIpluggy1.6.0indirect
PyPIpre-commit4.6.0indirect
PyPIprompt-toolkit3.0.51indirect
PyPIptyprocess0.7.0indirect
PyPIpure-eval0.2.3indirect
PyPIpycodestyle2.14.0indirect
PyPIpyflakes3.4.0indirect
PyPIpygments2.20.0indirect
PyPIpytest9.0.3indirect
PyPIpytest-cov7.1.0indirect
PyPIpytest-flake81.3.0indirect
PyPIpytokens0.4.1indirect
PyPIrequirements-parser0.13.0indirect
PyPIresponses0.26.1indirect
PyPIrpds-py0.25.1indirect
PyPIschema0.7.7indirect
PyPIstack-data0.6.3indirect
PyPItabulate0.9.0indirect
PyPItbump6.11.0indirect
PyPItomli2.2.1indirect
PyPItomlkit0.11.8indirect
PyPItraitlets5.14.3indirect
PyPItypes-pyyaml6.0.12.20260518indirect
PyPItypes-requests2.33.0.20260518indirect
PyPItyping-extensions4.15.0indirect
PyPIunidecode1.4.0indirect
PyPIurllib32.7.0indirect
PyPIvirtualenv20.36.1indirect
PyPIwcwidth0.2.13indirect
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.11.0 — full methodology · metrics wiki.

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