Public record
Software health reportschema 0.12.0 · metrics 2.10.0 · 2026-07-17 19:16 UTC

Polymarket / py-sdk

Unified Python SDK for Polymarket DeFi

PythonMIT★ 71 stars⑂ 20 forkssince May 2026View on GitHub ↗

Polymarket/py-sdk holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on AI Readiness (82/100) and lowest on Community & Adoption (61/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

PolymarketOrganization
2,317 followers102 public repossince Sep 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIpolymarket-client0.1.0b2157,959210 days agoclientpolymarketprediction-marketstradingweb3

Metrics by category

Vitality

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

77Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
7.6/36Commit cadence11/52 weeks with commits
18/18Commit volume402 commits in the last year
0/10OpenSSF Scorecard: Maintainedproject was created within the last 90 days. Please review its contents carefully
Inputs used
commits_last_year402
human_commit_share
days_since_last_push0
active_weeks_last_year11

Release discipline

100Exceptional
How it's scored
27/27Ships releases21 releases published
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~1.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count21
latest_release_tagpolymarket-client-v0.1.0-b21
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases1.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?

61Moderate · 17% of overall
How it's scored
29.9/60Stars71 stars
10.7/25Forks20 forks
2.7/15Watchers4 watchers
Inputs used
forks20
stars71
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
63.5/80Monthly downloads57,959 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagespolymarket-client
dependents
ecosystemspypi
total_downloads
monthly_downloads57,959
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?

76Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
8.3/22.5Commit distributiontop contributor authored 63% of commits
12.2/13.5Contributor breadth9 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled9
top_contributor_share0.631
How it's scored
40.9/42Issue resolution97% of issues closed
27.1/30PR acceptance122/135 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-ReviewFound 3/9 approved changesets -- score normalized to 3
Inputs used
merged_prs122
open_issues1
closed_issues37
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.974
closed_unmerged_prs13
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
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
24.2/25Owner reach2,317 followers of Polymarket
25/25Track record102 public repos, account ~8 yr old
Inputs used
followers2,317
owner_typeOrganization
is_verified
owner_loginPolymarket
public_repos102
account_age_days3,236
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 0 days ago
20/20Version history21 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagespolymarket-client
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall
How it's scored
24/24CI workflows6 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests13 out of 13 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
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?

67Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
3.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests13 out of 13 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 3/9 approved changesets -- score normalized to 3
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintainedproject was created within the last 90 days. Please review its contents carefully
5/5Packagingpackaging workflow detected
3.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 7
4.5/5SASTSAST tool is not run on all commits -- score normalized to 9
2/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
6.8/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
6/7.5Vulnerabilities2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate6.7
Excluded from scoring (no data or not applicable): 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.

82Excellent · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes6,723
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
0/11Lint / format config
11/11Static type checkingsrc/polymarket/py.typed
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
7/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 7
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configno
typecheck_configssrc/polymarket/py.typed
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
27/45Type-checkable codePython with type-check config (src/polymarket/py.typed)
54.7/55Manageable file sizes2/332 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes120,139
source_files_sampled332
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

71GitHub stars
9contributors
402commits, last 12 months
0days since last push
21releases
1bus factor
1open issues
PyPIpackage ecosystems

More detail

OpenSSF Scorecard 6.7 / 10
6.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-07-17 19:15 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests13 out of 13 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 3/9 approved changesets -- score normalized to 3
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintainedproject was created within the last 90 days. Please review its contents carefully
10Packagingpackaging workflow detected
7Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 7
9SASTSAST tool is not run on all commits -- score normalized to 9
4Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
8Vulnerabilities2 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
PyPIeth-abi>=5,<6pyproject.toml
PyPIeth-account>=0.13,<1pyproject.toml
PyPIeth-utils>=4,<6pyproject.toml
PyPIhttpx>=0.27,<1pyproject.toml
PyPImsgpack>=1,<2pyproject.toml
PyPIpydantic>=2,<3pyproject.toml
PyPIwebsockets>=13,<16pyproject.toml
All dependencies 59

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

RegistryPackageVersionRelation
PyPIeth-abi5.2.0direct
PyPIeth-account0.13.7direct
PyPIeth-utils5.3.1direct
PyPIhttpx0.28.1direct
PyPImsgpack1.2.1direct
PyPIpydantic2.13.3direct
PyPIwebsockets15.0.1direct
PyPIannotated-types0.7.0indirect
PyPIanyio4.13.0indirect
PyPIbitarray3.8.1indirect
PyPIcertifi2026.4.22indirect
PyPIckzg2.1.7indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.13.5indirect
PyPIcytoolz1.1.0indirect
PyPIeth-hash0.8.0indirect
PyPIeth-keyfile0.8.1indirect
PyPIeth-keys0.7.0indirect
PyPIeth-rlp2.2.0indirect
PyPIeth-typing6.0.0indirect
PyPIh110.16.0indirect
PyPIh24.3.0indirect
PyPIhexbytes1.3.1indirect
PyPIhpack4.1.0indirect
PyPIhttpcore1.0.9indirect
PyPIhyperframe6.1.0indirect
PyPIidna3.16indirect
PyPIiniconfig2.3.0indirect
PyPInodeenv1.10.0indirect
PyPInumpy2.4.6indirect
PyPIpackaging26.2indirect
PyPIpandas2.3.3indirect
PyPIparsimonious0.10.0indirect
PyPIpluggy1.6.0indirect
PyPIpolars1.41.2indirect
PyPIpolars-runtime-321.41.2indirect
PyPIpolymarket-client0.1.0b21indirect
PyPIpyarrow21.0.0indirect
PyPIpycryptodome3.23.0indirect
PyPIpydantic-core2.46.3indirect
PyPIpygments2.20.0indirect
PyPIpyright1.1.409indirect
PyPIpytest8.4.2indirect
PyPIpytest-cov6.3.0indirect
PyPIpytest-watcher0.6.3indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpython-dotenv1.2.2indirect
PyPIpytz2026.2indirect
PyPIregex2026.4.4indirect
PyPIrespx0.23.1indirect
PyPIrlp4.1.0indirect
PyPIruff0.15.12indirect
PyPIsix1.17.0indirect
PyPItomli2.4.1indirect
PyPItoolz1.1.0indirect
PyPItyping-extensions4.15.0indirect
PyPItyping-inspection0.4.2indirect
PyPItzdata2026.2indirect
PyPIwatchdog6.0.0indirect
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.