Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-24 03:44 UTC

hamcrest / PyHamcrest

Hamcrest matchers for Python

PythonCustom license★ 805 stars⑂ 118 forkssince Dec 2010View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

hamcrest/PyHamcrest holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (88/100) and lowest on Vitality (53/100). It was last updated 5 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

HamcrestOrganization
42 followers7 public repossince Apr 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIPyHamcrest2.1.02,556,841241097 days agohamcrestmatcherspyunittesttestingunitunittestunittesting

Metrics by category

Vitality

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

53Moderate · 21% of overall
How it's scored
36/36Push recency — last push 5 days ago
3.5/36Commit cadence — 5/52 weeks with commits
15.3/18Commit volume — 49 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year49
human_commit_share0.74
days_since_last_push5
active_weeks_last_year5
How it's scored
27/27Ships releases — 10 releases published
0/36Release recency — latest release 1,097 days ago
5.4/27Release cadence — a release every ~403.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count10
latest_release_tagV2.1.0
releases_from_tagsno
days_since_latest_release1,097
mean_days_between_releases403.4
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?

76Good · 17% of overall
How it's scored
47.1/60Stars — 805 stars
17.2/25Forks — 118 forks
7.4/15Watchers — 22 watchers
Inputs used
forks118
stars805
watchers22
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
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 2,556,841 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesPyHamcrest
dependents—
ecosystemspypi
total_downloads—
monthly_downloads2,556,841
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?

64Moderate · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12.9/22.5Commit distribution — top contributor authored 43% of commits
13.5/13.5Contributor breadth — 33 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled33
top_contributor_share0.426
How it's scored
33.8/42Issue resolution — 80% of issues closed
24.8/30PR acceptance — 175/212 decided PRs merged
0/13Newcomer PR acceptance — 0/1 first-time contributors' PRs merged in 30d
6/15OpenSSF Scorecard: Code-Review — Found 2/5 approved changesets -- score normalized to 4
Inputs used
merged_prs175
open_issues17
closed_issues70
prs_merged_7d0
prs_decided_7d0
prs_merged_30d9
prs_decided_30d10
issue_closed_ratio0.805
closed_unmerged_prs37
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
11.7/25Owner reach — 42 followers of hamcrest
18.6/25Track record — 7 public repos, account ~14 yr old
Inputs used
followers42
owner_typeOrganization
is_verifiedno
owner_loginhamcrest
public_repos7
account_age_days5,318
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
4/35Publish recency — latest publish 1,097 days ago
20/20Version history — 24 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesPyHamcrest
ecosystemspypi
any_deprecatedno
min_days_since_publish1,097

Engineering Quality

Are baseline engineering and documentation practices in place?

88Excellent · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff], [tool.black], [tool.isort]), tox.ini
9.6/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_configyes

Documentation

80Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — http://hamcrest.org/
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepagehttp://hamcrest.org/
docs_sitehttp://hamcrest.org/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

69Good · 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/7.5Code-Review — Found 2/5 approved changesets -- score normalized to 4
2.5/2.5Contributors — project has 4 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 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not 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_aggregate6.1
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
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_packages53
unassessed_packages0
affected_by_severityhigh 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 53 resolved dependencies against OSV. 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.

72Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
28.1/40Legible commit history — 39 of 74 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.527
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.black], [tool.isort]), tox.ini
11/11Static type checking — src/hamcrest/py.typed
10/10Reproducible environment — Dockerfile, lockfile
10/10Demonstrated agent practice — 6 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 23 of the last 100 commits are automated dependency updates
1/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileyes
typed_languageno
bootstrap_filesdoc/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configssrc/hamcrest/py.typed
agent_commit_share0.06
toolchain_manifests—
dependency_bot_commit_share0.23
How it's scored
27/45Type-checkable code — Python with type-check config (src/hamcrest/py.typed)
55/55Manageable file sizes — 0/112 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes7,672
source_files_sampled112
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

805GitHub stars
33contributors
49commits, last 12 months
5days since last push
10releases
2bus factor
17open 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 ★ / 118 ⇿
0Stars
118Forks
10Releases

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.

02040608010012011732011-072019-022026-10
Major 0Minor 1Patch 0

Each point covers 14 days.

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-10-24 03:43 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
4Code-ReviewFound 2/5 approved changesets -- score normalized to 4
10Contributorsproject has 4 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 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
1Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
9Vulnerabilities1 existing vulnerabilities detected
All dependencies 53

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

RegistryPackageVersionRelation
PyPIalabaster0.7.16indirect
PyPIast-serialize0.13.0indirect
PyPIattrs26.1.0indirect
PyPIbabel2.18.0indirect
PyPIcertifi2026.7.22indirect
PyPIcharset-normalizer3.3.2indirect
PyPIclick8.5.0indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.6.1indirect
PyPIdecorator5.3.1indirect
PyPIdocutils0.21.2indirect
PyPIexceptiongroup1.2.2indirect
PyPIexecnet2.1.2indirect
PyPIidna3.20indirect
PyPIimagesize1.4.1indirect
PyPIiniconfig2.0.0indirect
PyPIjinja23.1.6indirect
PyPIjsonschema4.26.0indirect
PyPIjsonschema-specifications2023.12.1indirect
PyPIlibrt0.16.0indirect
PyPImarkupsafe2.1.5indirect
PyPImypy2.4.0indirect
PyPImypy-extensions1.0.0indirect
PyPInumpy1.24.4indirect
PyPIpackaging24.1indirect
PyPIpathspec1.1.1indirect
PyPIpluggy1.5.0indirect
PyPIpygments2.21.0indirect
PyPIpytest9.0.3indirect
PyPIpytest-mypy-plugins3.1.2indirect
PyPIpytest-sugar1.1.1indirect
PyPIpytest-xdist3.6.1indirect
PyPIpyyaml6.0.2indirect
PyPIreferencing0.35.1indirect
PyPIregex2024.9.11indirect
PyPIrequests2.33.0indirect
PyPIrpds-py0.30.0indirect
PyPIrpds-py2026.6.3indirect
PyPIsnowballstemmer3.1.1indirect
PyPIsphinx7.4.7indirect
PyPIsphinxcontrib-applehelp1.0.4indirect
PyPIsphinxcontrib-devhelp1.0.2indirect
PyPIsphinxcontrib-htmlhelp2.1.0indirect
PyPIsphinxcontrib-jsmath1.0.1indirect
PyPIsphinxcontrib-qthelp2.0.0indirect
PyPIsphinxcontrib-serializinghtml2.0.0indirect
PyPItermcolor3.3.0indirect
PyPItomli2.0.1indirect
PyPItomlkit0.15.1indirect
PyPItowncrier24.8.0indirect
PyPItypes-mock5.2.0.20260518indirect
PyPItyping-extensions4.16.0indirect
PyPIurllib32.8.0indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 53 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
certifi2026.7.22indirecthigh22026.10.19

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.