Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-28 05:26 UTC

jpadilla / pyjwt

JSON Web Token implementation in Python

PythonMIT★ 5,695 stars⑂ 788 forkssince Feb 2011View on GitHub ↗

jpadilla/pyjwt holds a health index of 93 out of 100, placing it in the Exceptional band. It scores highest on Engineering Quality (92/100) and lowest on AI Readiness (65/100). It was last updated 3 days ago. 2 contributors account 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

José PadillaPersonal account
1,437 followers231 public repossince May 2009@auth0

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
PyPIPyJWT2.13.0695,639,3275598 days agojsonjwtsecuritysigningtokenweb

Metrics by category

Vitality

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

69Good · 21% of overall
How it's scored
36/36Push recencylast push 3 days ago
12.5/36Commit cadence18/52 weeks with commits
15.8/18Commit volume57 commits in the last year
1/10OpenSSF Scorecard: Maintained0 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 1
Inputs used
commits_last_year57
human_commit_share0.64
days_since_last_push3
active_weeks_last_year18
How it's scored
27/27Ships releases43 releases published
27/36Release recencylatest release 98 days ago
12.6/27Release cadencea release every ~145 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count43
latest_release_tag2.13.0
releases_from_tagsno
days_since_latest_release98
mean_days_between_releases145
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?

88Excellent · 17% of overall
How it's scored
60/60Stars5,695 stars
24.1/25Forks788 forks
9.8/15Watchers59 watchers
Inputs used
forks788
stars5,695
watchers59
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
7.2/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingno
has_issue_templateyes
has_code_of_conductyes
readme_badge_servicescodecov.io, github.com, readthedocs.org, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads695,639,327 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesPyJWT
dependents
ecosystemspypi
total_downloads
monthly_downloads695,639,327
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?

74Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
14.7/22.5Commit distributiontop contributor authored 34% of commits
13.5/13.5Contributor breadth98 contributors
10/10OpenSSF Scorecard: Contributorsproject has 51 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled98
top_contributor_share0.345
How it's scored
38.9/42Issue resolution93% of issues closed
23.9/30PR acceptance517/650 decided PRs merged
0/13Newcomer PR acceptance0/3 first-time contributors' PRs merged in 30d
4.5/15OpenSSF Scorecard: Code-ReviewFound 7/22 approved changesets -- score normalized to 3
Inputs used
merged_prs517
open_issues37
closed_issues469
prs_merged_7d0
prs_decided_7d2
prs_merged_30d0
prs_decided_30d3
issue_closed_ratio0.927
closed_unmerged_prs133
first_time_authors_30d3
first_time_prs_merged_30d0
first_time_prs_decided_30d3
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
22.7/25Owner reach1,437 followers of jpadilla
25/25Track record231 public repos, account ~17 yr old
Inputs used
followers1,437
owner_typeUser
is_verified
owner_loginjpadilla
public_repos231
account_age_days6,317
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 98 days ago
20/20Version history55 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesPyJWT
ecosystemspypi
any_deprecatedno
min_days_since_publish98

Engineering Quality

Are baseline engineering and documentation practices in place?

92Excellent · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter configruff.toml, tox.ini
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests17 out of 17 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

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://pyjwt.readthedocs.io
10/10Repository description
10/10Topics3 topics
0/10Wiki
Inputs used
topicspython, jwt, hacktoberfest
has_wikino
homepagehttps://pyjwt.readthedocs.io
docs_sitehttps://pyjwt.readthedocs.io
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

76Good · 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-Tests17 out of 17 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
2.2/7.5Code-ReviewFound 7/22 approved changesets -- score normalized to 3
2.5/2.5Contributorsproject has 51 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
5/5Fuzzingproject is fuzzed
2.5/2.5Licenselicense file detected
0.8/7.5Maintained0 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 1
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
2.5/5SASTSAST tool is not run on all commits -- score normalized to 5
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate7.6
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.

65Good · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history52 of 64 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.812
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapdocs/Makefile
22/22Automated tests
11/11Lint / format configruff.toml, tox.ini
11/11Static type checkingjwt/py.typed
0/10Reproducible environment
8/10Demonstrated agent practice4 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance9 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_filesdocs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configsjwt/py.typed
agent_commit_share0.04
toolchain_manifests
dependency_bot_commit_share0.09
How it's scored
27/45Type-checkable codePython with type-check config (jwt/py.typed)
52.9/55Manageable file sizes1/26 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes64,352
source_files_sampled26
oversized_source_files1

Key facts

5,695GitHub stars
98contributors
57commits, last 12 months
3days since last push
43releases
2bus factor
37open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 788 ⇿
0Stars
788Forks
43Releases

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.

0200400600800775162011-052019-012026-08
Major 2Minor 22Patch 17

Each point covers 14 days.

OpenSSF Scorecard 7.6 / 10
7.6aggregate

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-28 05:26 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-Tests17 out of 17 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 7/22 approved changesets -- score normalized to 3
10Contributorsproject has 51 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
1Maintained0 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 1
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
5SASTSAST tool is not run on all commits -- score normalized to 5
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
PyPItyping_extensions>= 4.0pyproject.toml
All dependencies 3

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

RegistryPackageVersionRelation
PyPItyping-extensionsdirect
PyPIsphinxindirect
PyPIsphinx-rtd-themeindirect
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 statisticsPyPI.