Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 21:19 UTC

h2non / jsonpath-ng

Finally, a JSONPath implementation for Python that aims to be standard compliant. That's all. Enjoy!

PythonApache-2.0★ 733 stars⑂ 124 forkssince Mar 2017forkView on GitHub ↗
KindCommand-line toolLibraryhow this is determined

h2non/jsonpath-ng holds a health index of 60 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (73/100) and lowest on Vitality (44/100). It was last updated 40 days ago. 3 contributors account for most of its recent work.

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

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

Ownership

TomPersonal account
931 followers258 public repossince Mar 2009Dissident

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 publish
PyPIjsonpath-ng1.8.061,559,31411194 days ago

Metrics by category

Vitality

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

44Weak · 21% of overall
How it's scored
18/36Push recency — last push 40 days ago
5.5/36Commit cadence — 8/52 weeks with commits
10.3/18Commit volume — 13 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year13
human_commit_share0.93
days_since_last_push40
active_weeks_last_year8
How it's scored
27/27Ships releases — 3 releases published
7.2/36Release recency — latest release 699 days ago
12.6/27Release cadence — a release every ~196.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count3
latest_release_tagv1.7.0
releases_from_tagsno
days_since_latest_release699
mean_days_between_releases196.9

Community & Adoption

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

62Moderate · 17% of overall
How it's scored
46.5/60Stars — 733 stars
17.4/25Forks — 124 forks
5.6/15Watchers — 11 watchers
Inputs used
forks124
stars733
watchers11
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/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_readmeno
has_licenseno
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 61,559,314 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesjsonpath-ng
dependents—
ecosystemspypi
total_downloads—
monthly_downloads61,559,314
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?

73Good · 23% of overall
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
15.6/22.5Commit distribution — top contributor authored 31% of commits
13.5/13.5Contributor breadth — 43 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor3
contributors_sampled43
top_contributor_share0.307
How it's scored
22.6/42Issue resolution — 54% of issues closed
22.3/30PR acceptance — 61/82 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_prs61
open_issues63
closed_issues73
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.537
closed_unmerged_prs21
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 backing — personal (user) account
0/20Verified domain — not applicable to user accounts
21.3/25Owner reach — 931 followers of h2non
25/25Track record — 258 public repos, account ~17 yr old
Inputs used
followers931
owner_typeUser
is_verified—
owner_loginh2non
public_repos258
account_age_days6,389
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
26/35Publish recency — latest publish 194 days ago
20/20Version history — 11 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesjsonpath-ng
ecosystemspypi
any_deprecatedno
min_days_since_publish194

Engineering Quality

Are baseline engineering and documentation practices in place?

61Moderate · 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
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

20At Risk
How it's scored
0/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
10/10Topics — 8 topics
10/10Wiki
Inputs used
topicsjsonpath, json, xpath, python, path, documents, query, filter
has_wikiyes
homepage—
docs_site—
has_readmeno
has_docs_dirno
has_descriptionno

Security

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

45Weak · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
25/25Dependabot config
0/25Dependency lockfiles
20/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles—
manifestspyproject.toml, requirements-dev.txt, requirements.txt, setup.py
has_codeql_workflowyes
has_security_policyno
has_dependabot_configyes

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.

47Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
4/40Legible commit history — 7 of 93 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.075
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — tox.ini
0/11Static type checking
10/10Reproducible environment — devcontainer
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 7 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
has_devcontaineryes
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.07
How it's scored
0/45Type-checkable code — Python without a type-check config
53.1/55Manageable file sizes — 1/29 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes135,305
source_files_sampled29
oversized_source_files1

Key facts

733GitHub stars
43contributors
13commits, last 12 months
40days since last push
3releases
3bus factor
63open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Community profile unavailable
  • No resolved dependencies carried a version and a supported ecosystem
  • OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

More detail

Star and fork history 0 ★ / 124 ⇿
0Stars
124Forks
3Releases

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.

025507510012512432017-062022-012026-08
Major 0Minor 2Patch 1

Each point covers 9 days.

All dependencies 5

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

RegistryPackageVersionRelation
PyPIflake8—indirect
PyPIhypothesis—indirect
PyPIpytest—indirect
PyPIsetuptools—indirect
PyPItox—indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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 — PyPI.