Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 13:28 UTC

pact-foundation / pact_broker

Enables your consumer driven contracts workflow

Ruby · JavaScriptMIT★ 745 stars⑂ 191 forkssince Oct 2013View on GitHub ↗
KindCommand-line toolLibraryNetwork servicehow this is determined

pact-foundation/pact_broker holds a health index of 92 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (96/100) and lowest on AI Readiness (58/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Pact FoundationOrganization
410 followers91 public repossince Sep 2015

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemspact_broker2.121.0-2348 days ago

Metrics by category

Vitality

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

88Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
27.7/36Commit cadence — 40/52 weeks with commits
18/18Commit volume — 176 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year176
human_commit_share0.76
days_since_last_push0
active_weeks_last_year40
How it's scored
27/27Ships releases — 90 releases published
36/36Release recency — latest release 8 days ago
19.8/27Release cadence — a release every ~60.7 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count90
latest_release_tagv2.121.0
releases_from_tagsno
days_since_latest_release8
mean_days_between_releases60.7

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

83Excellent · 17% of overall
How it's scored
46.6/60Stars — 745 stars
19/25Forks — 191 forks
8.8/15Watchers — 40 watchers
Inputs used
forks191
stars745
watchers40
growth_stateorganic
growth_factor_pct100

Community health

100Exceptional
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
7.2/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateyes
has_code_of_conductyes
readme_badge_servicesbadge.fury.io, github.com, shields.io
has_pull_request_templateyes
How it's scored
59.8/80Total downloads — 572,383 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagespact_broker
dependents—
ecosystemsrubygems
total_downloads572,383
monthly_downloads—
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?

67Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
2.8/22.5Commit distribution — top contributor authored 88% of commits
13.5/13.5Contributor breadth — 76 contributors
10/10OpenSSF Scorecard: Contributors — project has 23 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled76
top_contributor_share0.875
How it's scored
32.8/42Issue resolution — 78% of issues closed
25.2/30PR acceptance — 408/486 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 5/14 approved changesets -- score normalized to 3
Inputs used
merged_prs408
open_issues100
closed_issues355
prs_merged_7d0
prs_decided_7d0
prs_merged_30d7
prs_decided_30d10
issue_closed_ratio0.78
closed_unmerged_prs78
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
0/20Verified domain
18.8/25Owner reach — 410 followers of pact-foundation
25/25Track record — 91 public repos, account ~10 yr old
Inputs used
followers410
owner_typeOrganization
is_verifiedno
owner_loginpact-foundation
public_repos91
account_age_days4,006

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on rubygems
35/35Publish recency — latest publish 8 days ago
20/20Version history — 234 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagespact_broker
ecosystemsrubygems
any_deprecatedno
min_days_since_publish8

Engineering Quality

Are baseline engineering and documentation practices in place?

96Exceptional · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
16/16Linter config — .eslintrc.yml, .rubocop.yml
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 20 out of 20 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

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — http://pactflow.io
10/10Repository description
10/10Topics — 10 topics
10/10Wiki
Inputs used
topicspact-broker, hal-browser, contract-testing, consumer, consumer-driven-contracts, verification, provider, hacktoberfest, smartbear-supported, pact
has_wikiyes
homepagehttp://pactflow.io
docs_sitehttp://pactflow.io
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

60Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 20 out of 20 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
2.2/7.5Code-Review — Found 5/14 approved changesets -- score normalized to 3
2.5/2.5Contributors — project has 23 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.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
3.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 7
4.5/5SAST — SAST tool is not run on all commits -- score normalized to 9
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate6

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.

58Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://docs.pact.io/llms.txt)
40/40Legible commit history — 76 of 76 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.pact.io/llms.txt
legible_history_share1
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .eslintrc.yml, .rubocop.yml
0/11Static type checking
10/10Reproducible environment — Dockerfile
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
7/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 7
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.06
toolchain_manifests—
dependency_bot_commit_share0.23
How it's scored
0/45Type-checkable code — Ruby without a type-check config
54.6/55Manageable file sizes — 9/1,241 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes293,228
source_files_sampled1,241
oversized_source_files9
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
0/20MCP server
40/40Runnable examples — example
Inputs used
example_dirsexample
has_mcp_signalno
api_schema_files—
interfaces_expected_ofnetwork-service

Key facts

745GitHub stars
76contributors
176commits, last 12 months
0days since last push
90releases
1bus factor
100open issues
RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-06-26: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 745 stars today.
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 743 ★ / 191 ⇿
743Stars
191Forks
89Releases

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.

Star history is shown as collected on 2026-06-26. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

0125250375500625750743185102014-052020-072026-08
Major 0Minor 62Patch 26

Each point covers 12 days.

OpenSSF Scorecard 6.0 / 10
6.0aggregate

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-12 13:28 UTC

10Binary-Artifactsno binaries found in the repo
1Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests20 out of 20 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 5/14 approved changesets -- score normalized to 3
10Contributorsproject has 23 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
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
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 20
RegistryPackageVersion constraintManifest
RubyGemsrake~> 13.3Gemfile
RubyGemssqlite3>=2.0.0Gemfile
RubyGemspadrino-core>= 0.16.0.pre3Gemfile
RubyGemsrackup~> 2.2Gemfile
RubyGemsthor~> 1.4Gemfile
RubyGemsrspec-pact-matchers~>0.1Gemfile
RubyGemsbundler-audit~>0.4Gemfile
RubyGemswebmock~>3.9Gemfile
RubyGemsrspec~>3.0Gemfile
RubyGemsrspec-its~>1.2Gemfile
RubyGemsdatabase_cleaner~>1.8Gemfile
RubyGemstimecop~> 0.9Gemfile
RubyGemsfaraday~>2.0Gemfile
RubyGemsdocker-api~>2.0Gemfile
RubyGemsapprovals>=0.0.24Gemfile
RubyGemstzinfo~>2.0Gemfile
RubyGemsfaraday-retry~>2.0Gemfile
RubyGemsopenapi_first~>2.0Gemfile
RubyGemspg~>1.6Gemfile
RubyGemspact-support—Gemfile
All dependencies 61

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

RegistryPackageVersionRelation
RubyGemsapprovals—direct
RubyGemsbundler-audit—direct
RubyGemsdatabase_cleaner—direct
RubyGemsdocker-api—direct
RubyGemsfaraday—direct
RubyGemsfaraday-retry—direct
RubyGemsopenapi_first—direct
RubyGemspact-support—direct
RubyGemspadrino-core—direct
RubyGemspg—direct
RubyGemsrackup—direct
RubyGemsrake—direct
RubyGemsrspec—direct
RubyGemsrspec-its—direct
RubyGemsrspec-pact-matchers—direct
RubyGemssqlite3—direct
RubyGemsthor—direct
RubyGemstimecop—direct
RubyGemstzinfo—direct
RubyGemswebmock—direct
RubyGemsanyway_config—indirect
RubyGemsappraisal—indirect
RubyGemscsv—indirect
RubyGemsdry-validation—indirect
RubyGemshaml—indirect
RubyGemsjson—indirect
RubyGemsjson_schemer—indirect
RubyGemsmoments—indirect
RubyGemsmutex_m—indirect
RubyGemsostruct—indirect
RubyGemspact—indirect
RubyGemspact-ffi—indirect
RubyGemspact_broker—indirect
RubyGemspry-byebug—indirect
RubyGemspstore—indirect
RubyGemspsych—indirect
RubyGemspuma—indirect
RubyGemsrack—indirect
RubyGemsrack-protection—indirect
RubyGemsrack-reverse-proxy—indirect
RubyGemsrack-test—indirect
RubyGemsredcarpet—indirect
RubyGemsreform—indirect
RubyGemsrequest_store—indirect
RubyGemsroar—indirect
RubyGemsrspec_junit_formatter—indirect
RubyGemsrubocop—indirect
RubyGemsrubocop-performance—indirect
RubyGemssanitize—indirect
RubyGemssemantic_logger—indirect
RubyGemssemver2—indirect
RubyGemssequel—indirect
RubyGemssequel-annotate—indirect
RubyGemssimplecov—indirect
RubyGemssimplecov-cobertura—indirect
RubyGemssucker_punch—indirect
RubyGemstable_print—indirect
RubyGemsthin—indirect
RubyGemswebmachine—indirect
RubyGemswisper—indirect
RubyGemsyard—indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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 — RubyGems.