Public record
Software health reportschema 0.12.0 · metrics 2.10.0 · 2026-07-18 14:29 UTC

mvantellingen / python-zeep

A Python SOAP client

PythonCustom license★ 2,005 stars⑂ 609 forkssince Feb 2016View on GitHub ↗

mvantellingen/python-zeep holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Community & Adoption (71/100) and lowest on Sustainability & Governance (60/100). It was last updated 29 days ago. A single contributor accounts for most of its recent work.

75
overall / 100
Good

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.

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

Ownership

Michael van TellingenPersonal account
226 followers52 public repossince Apr 2010@labd

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
PyPIzeep4.3.3-6829 days ago

Metrics by category

Vitality

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

65Good · 21% of overall
How it's scored
28.8/36Push recencylast push 29 days ago
2.1/36Commit cadence3/52 weeks with commits
10.8/18Commit volume15 commits in the last year
10/10OpenSSF Scorecard: Maintained12 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year15
human_commit_share
days_since_last_push29
active_weeks_last_year3
How it's scored
27/27Ships releases7 releases published
36/36Release recencylatest release 29 days ago
12.6/27Release cadencea release every ~294.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count7
latest_release_tag4.3.3
releases_from_tagsno
days_since_latest_release29
mean_days_between_releases294.7
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
53.6/60Stars2,005 stars
23.2/25Forks609 forks
9.8/15Watchers59 watchers
Inputs used
forks609
stars2,005
watchers59
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
0/18CONTRIBUTING guide
0/13.5Code of conduct
7.2/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateyes
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

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

60Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
2.8/22.5Commit distributiontop contributor authored 88% of commits
13.5/13.5Contributor breadth100 contributors
10/10OpenSSF Scorecard: Contributorsproject has 35 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled100
top_contributor_share0.876
How it's scored
27.1/42Issue resolution65% of issues closed
18.8/30PR acceptance200/319 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 5/24 approved changesets -- score normalized to 2
Inputs used
merged_prs200
open_issues383
closed_issues699
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.646
closed_unmerged_prs119
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
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
16.9/25Owner reach226 followers of mvantellingen
24.6/25Track record52 public repos, account ~16 yr old
Inputs used
followers226
owner_typeUser
is_verified
owner_loginmvantellingen
public_repos52
account_age_days5,937
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 29 days ago
20/20Version history68 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageszeep
ecosystemspypi
any_deprecatedno
min_days_since_publish29

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
2/20OpenSSF Scorecard: CI-Tests1 out of 7 merged PRs checked by a CI test -- score normalized to 1
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttp://docs.python-zeep.org
10/10Repository description
10/10Topics4 topics
0/10Wiki
Inputs used
topicspython, soap, soap-client, wsdl
has_wikino
homepagehttp://docs.python-zeep.org
docs_sitehttp://docs.python-zeep.org
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

61Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0.2/2.5CI-Tests1 out of 7 merged PRs checked by a CI test -- score normalized to 1
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-ReviewFound 5/24 approved changesets -- score normalized to 2
2.5/2.5Contributorsproject has 35 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
7.5/7.5Maintained12 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
5/5Pinned-Dependenciesall dependencies are pinned
1.5/5SASTSAST tool is not run on all commits -- score normalized to 3
4.5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.1
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.

62Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
18/18One-command bootstrapMakefile, docs/Makefile, examples/Makefile
22/22Automated tests
0/11Lint / format config
11/11Static type checkingmypy.ini, src/zeep/py.typed
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
10/10OpenSSF Scorecard: Pinned-Dependenciesall dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_filesMakefile, docs/Makefile, examples/Makefile
has_devcontainerno
has_linter_configno
typecheck_configsmypy.ini, src/zeep/py.typed
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
27/45Type-checkable codePython with type-check config (mypy.ini, src/zeep/py.typed)
55/55Manageable file sizes0/121 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes52,491
source_files_sampled121
oversized_source_files0
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

2,005GitHub stars
100contributors
15commits, last 12 months
29days since last push
7releases
1bus factor
383open issues
PyPIpackage ecosystems

More detail

OpenSSF Scorecard 6.1 / 10
6.1aggregate

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-07-18 14:28 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
1CI-Tests1 out of 7 merged PRs checked by a CI test -- score normalized to 1
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 5/24 approved changesets -- score normalized to 2
10Contributorsproject has 35 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained12 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
3SASTSAST tool is not run on all commits -- score normalized to 3
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
PyPIattrs>=17.2.0pyproject.toml
PyPIisodate>=0.5.4pyproject.toml
PyPIlxml>=4.6.0pyproject.toml
PyPIplatformdirs>=1.4.0pyproject.toml
PyPIrequests>=2.7.0pyproject.toml
PyPIrequests-toolbelt>=0.7.1pyproject.toml
PyPIrequests-file>=1.5.1pyproject.toml
All dependencies 71

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

RegistryPackageVersionRelation
PyPIattrsdirect
PyPIattrs26.1.0direct
PyPIisodatedirect
PyPIisodate0.7.2direct
PyPIlxmldirect
PyPIlxml6.1.1direct
PyPIplatformdirsdirect
PyPIplatformdirs4.10.0direct
PyPIrequestsdirect
PyPIrequests2.34.2direct
PyPIrequests-filedirect
PyPIrequests-file3.0.1direct
PyPIrequests-toolbeltdirect
PyPIrequests-toolbelt1.0.0direct
PyPIalabaster1.0.0indirect
PyPIanyio4.14.0indirect
PyPIbabel2.18.0indirect
PyPIbackports-asyncio-runner1.2.0indirect
PyPIcertifi2026.6.17indirect
PyPIcharset-normalizer3.4.7indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.14.1indirect
PyPIdocutils0.21.2indirect
PyPIdocutils0.22.4indirect
PyPIexceptiongroup1.3.1indirect
PyPIflake87.1.1indirect
PyPIflake8-blind-except0.2.1indirect
PyPIflake8-debugger4.1.2indirect
PyPIflake8-imports0.1.1indirect
PyPIfreezegun1.5.1indirect
PyPIh110.16.0indirect
PyPIhttpcore1.0.9indirect
PyPIhttpxindirect
PyPIhttpx0.28.1indirect
PyPIidna3.18indirect
PyPIimagesize2.0.0indirect
PyPIiniconfig2.3.0indirect
PyPIisort5.13.2indirect
PyPIjinja23.1.6indirect
PyPImarkupsafe3.0.3indirect
PyPIpackaging26.2indirect
PyPIpluggy1.6.0indirect
PyPIpretend1.0.9indirect
PyPIpygments2.20.0indirect
PyPIpytest9.1.0indirect
PyPIpytest-asyncio1.4.0indirect
PyPIpytest-cov7.1.0indirect
PyPIpytest-httpx0.36.2indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIrequests-mock1.12.1indirect
PyPIroman-numerals4.1.0indirect
PyPIruff0.15.17indirect
PyPIsetuptoolsindirect
PyPIsix1.17.0indirect
PyPIsnowballstemmer3.1.1indirect
PyPIsphinxindirect
PyPIsphinx8.1.3indirect
PyPIsphinx9.0.4indirect
PyPIsphinx9.1.0indirect
PyPIsphinxcontrib-applehelp2.0.0indirect
PyPIsphinxcontrib-devhelp2.0.0indirect
PyPIsphinxcontrib-htmlhelp2.1.0indirect
PyPIsphinxcontrib-jsmath1.0.1indirect
PyPIsphinxcontrib-qthelp2.0.0indirect
PyPIsphinxcontrib-serializinghtml2.0.0indirect
PyPItomli2.4.1indirect
PyPItyping-extensions4.15.0indirect
PyPIurllib32.7.0indirect
PyPIxmlsecindirect
PyPIxmlsec1.3.17indirect
PyPIzeep4.3.3indirect
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.12.0 — full methodology · metrics wiki.

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