Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-04 20:43 UTC

benoitc / gunicorn

gunicorn 'Green Unicorn' is a WSGI HTTP Server for UNIX, fast clients and sleepy applications.

PythonCustom license★ 10,638 stars⑂ 1,851 forkssince Nov 2009View on GitHub ↗
KindLibraryCommand-line toolPluginhow this is determined

benoitc/gunicorn holds a health index of 91 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (90/100) and lowest on AI Readiness (63/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

91
overall / 100
Excellent

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.

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

Ownership

Benoit ChesneauPersonal account
2,357 followers274 public repossince Jun 2008Enki Multimedia

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
PyPIgunicorn26.0.0-9791 days ago

Metrics by category

Vitality

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

80Excellent · 21% of overall
How it's scored
36/36Push recencylast push 2 days ago
13.8/36Commit cadence20/52 weeks with commits
18/18Commit volume428 commits in the last year
5/10OpenSSF Scorecard: Maintained4 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year428
human_commit_share0.95
days_since_last_push2
active_weeks_last_year20
How it's scored
27/27Ships releases42 releases published
27/36Release recencylatest release 91 days ago
27/27Release cadencea release every ~11.3 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count42
latest_release_tag26.0.0
releases_from_tagsno
days_since_latest_release91
mean_days_between_releases11.3
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?

82Excellent · 17% of overall
How it's scored
60/60Stars10,638 stars
25/25Forks1,851 forks
12.9/15Watchers214 watchers
Inputs used
forks1,851
stars10,638
watchers214
growth_stateorganic
growth_factor_pct100
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno

Sustainability & Governance

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

68Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
9.2/22.5Commit distributiontop contributor authored 59% of commits
13.5/13.5Contributor breadth99 contributors
10/10OpenSSF Scorecard: Contributorsproject has 106 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled99
top_contributor_share0.59
How it's scored
40.7/42Issue resolution97% of issues closed
17.5/30PR acceptance721/1,233 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 1/13 approved changesets -- score normalized to 0
Inputs used
merged_prs721
open_issues68
closed_issues2,153
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.969
closed_unmerged_prs512
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 backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
24.2/25Owner reach2,357 followers of benoitc
25/25Track record274 public repos, account ~18 yr old
Inputs used
followers2,357
owner_typeUser
is_verified
owner_loginbenoitc
public_repos274
account_age_days6,618
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 91 days ago
20/20Version history97 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgunicorn
ecosystemspypi
any_deprecatedno
min_days_since_publish91

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall
How it's scored
24/24CI workflows7 workflow(s)
24/24Tests present
16/16Linter config.pylintrc, tox.ini
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests11 out of 11 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttp://www.gunicorn.org
10/10Repository description
10/10Topics5 topics
10/10Wiki
Inputs used
topicshttp-server, http, python, wsgi-server, wsgi
has_wikiyes
homepagehttp://www.gunicorn.org
docs_sitehttp://www.gunicorn.org
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

66Good · 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-Tests11 out of 11 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 1/13 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 106 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
5/5Fuzzingproject is fuzzed
2.2/2.5Licenselicense file detected
3.8/7.5Maintained4 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 5
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
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities40 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.7
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages1
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the pypi:gunicorn@26.0.0 runtime dependency closure — what installing the published package pulls in — 1 packages. Reachability is not analyzed.

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.

63Moderate · 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 history91 of 95 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.958
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format config.pylintrc, tox.ini
0/11Static type checking
10/10Reproducible environmentDockerfile, lockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance5 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
lockfilesuv.lock
has_dockerfileyes
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.05
How it's scored
0/45Type-checkable codePython without a type-check config
54.7/55Manageable file sizes2/433 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes95,227
source_files_sampled433
oversized_source_files2
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
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

10,638GitHub stars
99contributors
428commits, last 12 months
2days since last push
42releases
1bus factor
68open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-07-19: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 10638 stars today.

More detail

Star and fork history 10,630 ★ / 1,851 ⇿
10,630Stars
1,851Forks
21Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

Star history is shown as collected on 2026-07-19. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

02,0004,0006,0008,00010,00012,00010,6301,851252018-072022-072026-07
Major 6Minor 7Patch 8

Each point covers 8 days.

OpenSSF Scorecard 5.7 / 10
5.7aggregate

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-04 20:42 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-Tests11 out of 11 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 1/13 approved changesets -- score normalized to 0
10Contributorsproject has 106 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
9Licenselicense file detected
5Maintained4 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 5
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
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities40 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
PyPIpackagingpyproject.toml
All dependencies 69

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

RegistryPackageVersionRelation
PyPIpackaging26.0direct
PyPIanyio4.13.0indirect
PyPIbackports-asyncio-runner1.2.0indirect
PyPIblacksheepindirect
PyPIcertifi2026.2.25indirect
PyPIcffi2.0.0indirect
PyPIchannelsindirect
PyPIcherrypyindirect
PyPIcolorama0.4.6indirect
PyPIcoverageindirect
PyPIcoverage7.13.1indirect
PyPIdjangoindirect
PyPIdnspython2.8.0indirect
PyPIeventlet0.40.4indirect
PyPIexceptiongroup1.3.1indirect
PyPIfastapiindirect
PyPIflaskindirect
PyPIgeventindirect
PyPIgevent25.9.1indirect
PyPIgreenlet3.3.0indirect
PyPIgunicorn-h1cindirect
PyPIgunicorn-h1c0.5.1indirect
PyPIh110.16.0indirect
PyPIh2indirect
PyPIh24.3.0indirect
PyPIhpack4.1.0indirect
PyPIhttpcore1.0.9indirect
PyPIhttptoolsindirect
PyPIhttpxindirect
PyPIhttpx0.28.1indirect
PyPIhyperframe6.1.0indirect
PyPIidna3.11indirect
PyPIiniconfig2.3.0indirect
PyPIlitestarindirect
PyPImarkdown-grid-tablesindirect
PyPImkdocsindirect
PyPImkdocs-gen-filesindirect
PyPImkdocs-macros-pluginindirect
PyPImkdocs-materialindirect
PyPInumpyindirect
PyPIpluggy1.6.0indirect
PyPIpycparser3.0indirect
PyPIpydanticindirect
PyPIpygments2.19.2indirect
PyPIpymdown-extensionsindirect
PyPIpyramidindirect
PyPIpytestindirect
PyPIpytest9.0.2indirect
PyPIpytest-asyncioindirect
PyPIpytest-asyncio1.3.0indirect
PyPIpytest-covindirect
PyPIpytest-cov7.0.0indirect
PyPIpytest-json-reportindirect
PyPIquartindirect
PyPIrequestsindirect
PyPIsentence-transformersindirect
PyPIsetproctitle1.3.7indirect
PyPIsetuptoolsindirect
PyPIstarletteindirect
PyPItomli2.4.0indirect
PyPItornadoindirect
PyPItornado6.5.5indirect
PyPItyping-extensions4.15.0indirect
PyPIuvloopindirect
PyPIuvloop0.22.1indirect
PyPIweb-pyindirect
PyPIwebsocketsindirect
PyPIzope-event6.1indirect
PyPIzope-interface8.2indirect
Dependency advisories 0

Installing pypi:gunicorn@26.0.0 pulls in 1 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

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

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