Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-23 18:48 UTC

mauvilsa / jsonargparse

Minimal effort CLIs derived from type hints and parse from command line, config files and environment variables

PythonMIT★ 434 stars⑂ 66 forkssince May 2019View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

mauvilsa/jsonargparse holds a health index of 93 out of 100, placing it in the Exceptional band. It scores highest on Vitality (93/100) and lowest on AI Readiness (49/100). It was last updated today. A single contributor accounts for most of its recent work.

93
overall / 100
Exceptional

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.

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

Ownership

Mauricio VillegasPersonal account
63 followers33 public repossince Oct 2013@omni-us

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
PyPIjsonargparse4.53.01,690,2242060 days ago
PyPIjsonargparse-tests4.53.05380 days ago

Metrics by category

Vitality

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

93Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
33.2/36Commit cadence — 48/52 weeks with commits
18/18Commit volume — 203 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year203
human_commit_share1
days_since_last_push0
active_weeks_last_year48
How it's scored
16.2/27Ships releases — 93 version tags (no GitHub releases)
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~36.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count93
latest_release_tagv4.53.0
releases_from_tagsyes
days_since_latest_release0
mean_days_between_releases36.9
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?

81Excellent · 17% of overall
How it's scored
42.8/60Stars — 434 stars
15.1/25Forks — 66 forks
1.7/15Watchers — 3 watchers
Inputs used
forks66
stars434
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesbadge.fury.io, codecov.io, github.com, readthedocs.org, sonarcloud.io
has_pull_request_templateyes
How it's scored
80/80Monthly downloads — 1,690,277 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesjsonargparse, jsonargparse-tests
dependents—
ecosystemspypi
total_downloads—
monthly_downloads1,690,277
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?

64Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.9/22.5Commit distribution — top contributor authored 96% of commits
13.5/13.5Contributor breadth — 34 contributors
10/10OpenSSF Scorecard: Contributors — project has 13 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled34
top_contributor_share0.959
How it's scored
41.3/42Issue resolution — 98% of issues closed
28.4/30PR acceptance — 613/647 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs613
open_issues6
closed_issues371
prs_merged_7d7
prs_decided_7d7
prs_merged_30d35
prs_decided_30d35
issue_closed_ratio0.984
closed_unmerged_prs34
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
13/25Owner reach — 63 followers of mauvilsa
23.2/25Track record — 33 public repos, account ~13 yr old
Inputs used
followers63
owner_typeUser
is_verified—
owner_loginmauvilsa
public_repos33
account_age_days4,745
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 2 package(s) on pypi
35/35Publish recency — latest publish 0 days ago
20/20Version history — 206 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesjsonargparse, jsonargparse-tests
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

82Excellent · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 29 out of 29 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
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://jsonargparse.readthedocs.io
10/10Repository description
10/10Topics — 17 topics
0/10Wiki
Inputs used
topicspython, json, yaml, jsonnet, argparse-alternative, dataclasses, type-hints, argparse, cli, configuration-files, argument-parser, environment-variables, toml, omegaconf, pydantic, dependency-injection, jsonschema
has_wikino
homepagehttps://jsonargparse.readthedocs.io
docs_sitehttps://jsonargparse.readthedocs.io
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

83Excellent · 16% of overall

Security posture

83Excellent
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 29 out of 29 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
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 — 30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
5/5Pinned-Dependencies — all dependencies are pinned
5/5SAST — SAST tool is run on all commits
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
6.8/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate8.2
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.

49Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
26.7/40Legible commit history — 50 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.5
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
11/11Static type checking — jsonargparse/py.typed
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configsjsonargparse/py.typed
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Python with type-check config (jsonargparse/py.typed)
51/55Manageable file sizes — 5/68 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes169,565
source_files_sampled68
oversized_source_files5

Key facts

434GitHub stars
34contributors
203commits, last 12 months
0days since last push
93releases
1bus factor
6open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • deps.dev does not index pypi:jsonargparse@4.53.0; advisories assessed against the repository dependency graph instead
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 66 ⇿
0Stars
66Forks
92Releases

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.

01325385063756522019-092023-032026-09
Major 0Minor 52Patch 40

Each point covers 7 days.

OpenSSF Scorecard 8.2 / 10
8.2aggregate

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-10-23 18:48 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-Tests29 out of 29 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/30 approved changesets -- score normalized to 0
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
10Maintained30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
PyPIjsonargparse—jsonargparse_tests/pyproject.toml
All dependencies 32

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

RegistryPackageVersionRelation
PyPIjsonargparse—direct
PyPIargcomplete—indirect
PyPIattrs—indirect
PyPIautodocsumm—indirect
PyPIbuild—indirect
PyPIbump2version—indirect
PyPIdocstring-parser—indirect
PyPIfsspec—indirect
PyPIjsonnet—indirect
PyPIjsonschema—indirect
PyPIomegaconf—indirect
PyPIpre-commit—indirect
PyPIpydantic—indirect
PyPIpytest—indirect
PyPIpytest-cov—indirect
PyPIpytest-subtests—indirect
PyPIpyyaml—indirect
PyPIrequests—indirect
PyPIresponses—indirect
PyPIruamel-yaml—indirect
PyPIsetuptools—indirect
PyPIshtab—indirect
PyPIsphinx—indirect
PyPIsphinx-autodoc-typehints—indirect
PyPIsphinx-rtd-theme—indirect
PyPItomli-w—indirect
PyPItox—indirect
PyPItox-uv—indirect
PyPItwine—indirect
PyPItypes-pyyaml—indirect
PyPItypes-requests—indirect
PyPItypeshed-client—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.