Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 17:48 UTC

connectrpc / connect-py

The Python implementation of Connect: Protobuf RPC that works.

PythonCustom license★ 148 stars⑂ 14 forkssince Sep 2025View on GitHub ↗
KindLibraryCommand-line toolPluginhow this is determined

connectrpc/connect-py holds a health index of 96 out of 100, placing it in the Exceptional band. It scores highest on Vitality (99/100) and lowest on Community & Adoption (71/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

ConnectOrganization · verified domain
688 followers26 public repossince Jan 2022

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

Metrics by category

Vitality

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

99Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
35.3/36Commit cadence — 51/52 weeks with commits
18/18Commit volume — 282 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year282
human_commit_share0.48
days_since_last_push0
active_weeks_last_year51

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 17 releases published
36/36Release recency — latest release 6 days ago
27/27Release cadence — a release every ~17.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count17
latest_release_tagv0.12.1
releases_from_tagsno
days_since_latest_release6
mean_days_between_releases17.6
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?

71Good · 17% of overall
How it's scored
35.2/60Stars — 148 stars
9.3/25Forks — 14 forks
1.7/15Watchers — 3 watchers
Inputs used
forks14
stars148
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 2,231,952 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesconnectrpc, connectrpc-otel, protoc-gen-connectrpc, connectrpc-grpcreflect
dependents—
ecosystemspypi
total_downloads—
monthly_downloads2,231,952
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?

79Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
8.7/22.5Commit distribution — top contributor authored 62% of commits
13.5/13.5Contributor breadth — 12 contributors
10/10OpenSSF Scorecard: Contributors — project has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled12
top_contributor_share0.615
How it's scored
40.6/42Issue resolution — 97% of issues closed
28.2/30PR acceptance — 281/299 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs281
open_issues1
closed_issues28
prs_merged_7d3
prs_decided_7d3
prs_merged_30d8
prs_decided_30d8
issue_closed_ratio0.966
closed_unmerged_prs18
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
30/30Ownership backing — organization-owned
20/20Verified domain
20.4/25Owner reach — 688 followers of connectrpc
19.8/25Track record — 26 public repos, account ~4 yr old
Inputs used
followers688
owner_typeOrganization
is_verifiedyes
owner_loginconnectrpc
public_repos26
account_age_days1,707

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 4 package(s) on pypi
35/35Publish recency — latest publish 6 days ago
20/20Version history — 8 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesconnectrpc, connectrpc-otel, protoc-gen-connectrpc, connectrpc-grpcreflect
ecosystemspypi
any_deprecatedno
min_days_since_publish6

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows — 8 workflow(s)
24/24Tests present
16/16Linter config — connectrpc-grpcreflect/pyproject.toml ([tool.ruff]), connectrpc-otel/pyproject.toml ([tool.ruff]), pyproject.toml ([tool.ruff])
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 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

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://connectrpc.com/docs/python/getting-started/
10/10Repository description
10/10Topics — 5 topics
0/10Wiki
Inputs used
topicsconnectrpc, grpc, protobuf, python, protocol-buffers
has_wikino
homepagehttps://connectrpc.com/docs/python/getting-started/
docs_sitehttps://connectrpc.com/docs/python/getting-started/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

86Excellent · 16% of overall

Security posture

82Excellent
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 — 30 out of 30 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
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 6 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.2/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 4 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
4.5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
6.8/7.5Vulnerabilities — 1 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.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages5
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:connectrpc@0.12.1 runtime dependency closure — what installing the published package pulls in — 5 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.

82Excellent · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 46 of 48 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.958
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes460
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — connectrpc-grpcreflect/pyproject.toml ([tool.ruff]), connectrpc-otel/pyproject.toml ([tool.ruff]), pyproject.toml ([tool.ruff])
11/11Static type checking — connectrpc-otel/connectrpc_otel/py.typed, src/connectrpc/py.typed
10/10Reproducible environment — lockfile
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 52 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configsconnectrpc-otel/connectrpc_otel/py.typed, src/connectrpc/py.typed
agent_commit_share0.01
toolchain_manifests—
dependency_bot_commit_share0.52
How it's scored
27/45Type-checkable code — Python with type-check config (connectrpc-otel/connectrpc_otel/py.typed, src/connectrpc/py.typed)
55/55Manageable file sizes — 0/125 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes46,847
source_files_sampled125
oversized_source_files0
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — example/proto/connectrpc/eliza/v1/eliza.proto, test/proto/connectrpc/example/empty.proto, test/proto/connectrpc/example/haberdasher.proto
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — example
Inputs used
example_dirsexample
has_mcp_signalno
api_schema_filesexample/proto/connectrpc/eliza/v1/eliza.proto, test/proto/connectrpc/example/empty.proto, test/proto/connectrpc/example/haberdasher.proto
interfaces_expected_of—
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

148GitHub stars
12contributors
282commits, last 12 months
0days since last push
17releases
1bus factor
1open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 14 ⇿
0Stars
14Forks
15Releases

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.

03581013151412025-092026-022026-07
Major 0Minor 7Patch 4
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-09-10 17: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-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 6 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 4 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
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
9Vulnerabilities1 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
PyPIconnectrpc>=0.11.0connectrpc-grpcreflect/pyproject.toml
PyPIopentelemetry-api>=1.39.1connectrpc-otel/pyproject.toml
PyPIopentelemetry-instrumentation>=0.60b1connectrpc-otel/pyproject.toml
PyPIprotobuf-py>=0.3.0protoc-gen-connectrpc/pyproject.toml
PyPIprotobuf-py>=0.3.0pyproject.toml
PyPIpyqwest>=0.5.1pyproject.toml
All dependencies 108

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

RegistryPackageVersionRelation
PyPIconnectrpc—direct
PyPIconnectrpc0.11.0direct
PyPIconnectrpc0.12.1direct
PyPIopentelemetry-api—direct
PyPIopentelemetry-api1.43.0direct
PyPIopentelemetry-api1.44.0direct
PyPIopentelemetry-instrumentation—direct
PyPIopentelemetry-instrumentation0.65b0direct
PyPIprotobuf-py—direct
PyPIprotobuf-py0.1.1direct
PyPIprotobuf-py0.4.0direct
PyPIpyqwest0.6.2direct
PyPIanyio4.14.1indirect
PyPIasgiref3.12.1indirect
PyPIbackports-asyncio-runner1.2.0indirect
PyPIblinker1.9.0indirect
PyPIbrotli1.2.0indirect
PyPIbuf-bin1.72.0indirect
PyPIclick8.4.2indirect
PyPIcolorama0.4.6indirect
PyPIconnect-python-example—indirect
PyPIconnectrpc-grpcreflect0.1.0indirect
PyPIconnectrpc-grpcreflect0.2.0indirect
PyPIconnectrpc-otel0.2.0indirect
PyPIcoverage7.15.0indirect
PyPIdeepmerge2.1.0indirect
PyPIenvoy-server1.39.0indirect
PyPIexample0.1.0indirect
PyPIexceptiongroup1.3.1indirect
PyPIfind-libpython0.5.1indirect
PyPIflask3.1.3indirect
PyPIghp-import2.1.0indirect
PyPIgranian2.8.2indirect
PyPIgriffelib2.1.0indirect
PyPIgrpcio1.83.1indirect
PyPIgrpcio-tools1.83.1indirect
PyPIgunicorn26.2.0indirect
PyPIh110.16.0indirect
PyPIh24.3.0indirect
PyPIhpack4.2.0indirect
PyPIhypercorn0.18.0indirect
PyPIhyperframe6.1.0indirect
PyPIidna3.18indirect
PyPIiniconfig2.3.0indirect
PyPIitsdangerous2.2.0indirect
PyPIjinja23.1.6indirect
PyPImarkdown3.10.2indirect
PyPImarkupsafe3.0.3indirect
PyPImergedeep1.3.4indirect
PyPImkdocs1.6.1indirect
PyPImkdocs-autorefs1.4.4indirect
PyPImkdocs-get-deps0.2.2indirect
PyPImkdocstrings1.0.4indirect
PyPImkdocstrings-python2.0.8indirect
PyPIopentelemetry-instrumentation-asgi0.65b0indirect
PyPIopentelemetry-instrumentation-wsgi0.65b0indirect
PyPIopentelemetry-sdk1.44.0indirect
PyPIopentelemetry-semantic-conventions0.65b0indirect
PyPIopentelemetry-util-http0.65b0indirect
PyPIpackaging26.2indirect
PyPIpastel0.2.1indirect
PyPIpathspec1.1.1indirect
PyPIplatformdirs4.10.0indirect
PyPIpluggy1.6.0indirect
PyPIpoethepoet0.48.0indirect
PyPIpriority2.0.0indirect
PyPIprotobuf—indirect
PyPIprotobuf7.35.1indirect
PyPIprotobuf-py-ext0.1.1indirect
PyPIprotobuf-py-ext0.4.0indirect
PyPIprotoc-gen-connectrpc0.11.0indirect
PyPIprotoc-gen-connectrpc0.12.1indirect
PyPIprotoc-gen-grpc-py0.4.0indirect
PyPIprotoc-gen-py0.4.0indirect
PyPIpygments2.20.0indirect
PyPIpymdown-extensions11.0.1indirect
PyPIpytest9.1.0indirect
PyPIpytest9.1.1indirect
PyPIpytest-asyncio1.4.0indirect
PyPIpytest-cov7.1.0indirect
PyPIpytest-timeout2.5.0indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpyvoy1.0.1indirect
PyPIpyyaml6.0.3indirect
PyPIpyyaml-env-tag1.1indirect
PyPIruff0.16.6indirect
PyPIsetuptools83.0.0indirect
PyPIsix1.17.0indirect
PyPIstarlette1.3.1indirect
PyPIstarlette1.6.0indirect
PyPItaskgroup0.2.2indirect
PyPItombi1.5.2indirect
PyPItomli2.4.1indirect
PyPIty0.0.78indirect
PyPItypes-grpcio1.83.0.20260730indirect
PyPItypes-protobuf7.35.1.20260906indirect
PyPItyping-extensions4.16.0indirect
PyPIuv-build—indirect
PyPIuvicorn0.52.4indirect
PyPIuvloop0.22.1indirect
PyPIwatchdog6.0.0indirect
PyPIwerkzeug3.1.8indirect
PyPIwheel0.47.0indirect
PyPIwinloop0.6.3indirect
PyPIwrapt2.2.2indirect
PyPIwsproto1.3.2indirect
PyPIzensical0.0.59indirect
PyPIzstandard0.25.0indirect
Dependency advisories 0

Installing pypi:connectrpc@0.12.1 pulls in 5 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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — PyPI.