Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-11 19:59 UTC

pymodbus-dev / pymodbus

A full modbus protocol written in python

PythonCustom license★ 2,766 stars⑂ 1,063 forkssince Dec 2011View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

pymodbus-dev/pymodbus holds a health index of 95 out of 100, placing it in the Exceptional band. It scores highest on Vitality (94/100) and lowest on AI Readiness (68/100). It was last updated 2 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

pymodbusOrganization
74 followers4 public repossince Jan 2023

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIpymodbus3.15.01,411,8338129 days agomodbusasyncioscadaclientserversimulator

Metrics by category

Vitality

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

94Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
25.6/36Commit cadence — 37/52 weeks with commits
18/18Commit volume — 176 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_year176
human_commit_share1
days_since_last_push2
active_weeks_last_year37

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 99 releases published
36/36Release recency — latest release 29 days ago
27/27Release cadence — a release every ~40.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count99
latest_release_tagv3.15.0
releases_from_tagsno
days_since_latest_release29
mean_days_between_releases40.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?

92Excellent · 17% of overall
How it's scored
55.8/60Stars — 2,766 stars
25/25Forks — 1,063 forks
11.3/15Watchers — 110 watchers
Inputs used
forks1,063
stars2,766
watchers110
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

86Excellent
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
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, readthedocs.org, shields.io
has_pull_request_templateyes
How it's scored
80/80Monthly downloads — 1,411,833 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagespymodbus
dependents—
ecosystemspypi
total_downloads—
monthly_downloads1,411,833
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 factor — 2 contributor(s) cover half of all commits
12.1/22.5Commit distribution — top contributor authored 46% of commits
13.5/13.5Contributor breadth — 99 contributors
10/10OpenSSF Scorecard: Contributors — project has 22 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled99
top_contributor_share0.464
How it's scored
42/42Issue resolution — 100% of issues closed
25.3/30PR acceptance — 1,422/1,687 decided PRs merged
13/13Newcomer PR acceptance — 8/8 first-time contributors' PRs merged in 30d
7.5/15OpenSSF Scorecard: Code-Review — Found 17/30 approved changesets -- score normalized to 5
Inputs used
merged_prs1,422
open_issues1
closed_issues975
prs_merged_7d2
prs_decided_7d2
prs_merged_30d19
prs_decided_30d19
issue_closed_ratio0.999
closed_unmerged_prs265
first_time_authors_30d6
first_time_prs_merged_30d8
first_time_prs_decided_30d8
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
13.5/25Owner reach — 74 followers of pymodbus-dev
12.4/25Track record — 4 public repos, account ~3 yr old
Inputs used
followers74
owner_typeOrganization
is_verifiedno
owner_loginpymodbus-dev
public_repos4
account_age_days1,337

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 29 days ago
20/20Version history — 81 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagespymodbus
ecosystemspypi
any_deprecatedno
min_days_since_publish29

Engineering Quality

Are baseline engineering and documentation practices in place?

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

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 9 topics
10/10Wiki
Inputs used
topicspython, modbus, modbus-rtu, modbus-tcp, modbus-serial, modbus-slave, modbus-protocol, modbus-master, modbus-library
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

70Good · 16% of overall
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 — 28 out of 28 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
3.8/7.5Code-Review — Found 17/30 approved changesets -- score normalized to 5
2.5/2.5Contributors — project has 22 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 10 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
2/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.2
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, 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
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories2
affected_packages1
assessed_packages1
unassessed_packages19
affected_by_severitycritical 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 1 resolved dependencies against OSV. 19 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

68Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 90 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.9
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — doc/Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff], [tool.pylint])
11/11Static type checking — examples/py.typed, pymodbus/py.typed
10/10Reproducible environment — devcontainer
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_filesdoc/Makefile
has_devcontaineryes
has_linter_configyes
typecheck_configsexamples/py.typed, pymodbus/py.typed
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Python with type-check config (examples/py.typed, pymodbus/py.typed)
55/55Manageable file sizes — 0/128 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes40,157
source_files_sampled128
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
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

2,766GitHub stars
99contributors
176commits, last 12 months
2days since last push
99releases
2bus 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 ★ / 1,063 ⇿
0Stars
1,063Forks
99Releases

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.

02004006008001,0001,2001,06392014-072020-082026-09
Major 2Minor 22Patch 49

Each point covers 12 days.

OpenSSF Scorecard 6.2 / 10
6.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-11 19:58 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-Tests28 out of 28 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 17/30 approved changesets -- score normalized to 5
10Contributorsproject has 22 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 10 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
4Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 20

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

RegistryPackageVersionRelation
PyPIaiohttp—indirect
PyPIbottle0.12.19indirect
PyPIbuild—indirect
PyPIcodespell—indirect
PyPIcoverage—indirect
PyPIpylint—indirect
PyPIpyserial—indirect
PyPIpytest—indirect
PyPIpytest-aiohttp—indirect
PyPIpytest-asyncio—indirect
PyPIpytest-cov—indirect
PyPIpytest-timeout—indirect
PyPIpytest-xdist—indirect
PyPIrecommonmark—indirect
PyPIruff—indirect
PyPIsetuptools—indirect
PyPIsphinx—indirect
PyPIsphinx-rtd-theme—indirect
PyPItwine—indirect
PyPIzuban—indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 1 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct. 19 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
bottle0.12.19indirectcritical20.12.20

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.