Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-31 09:34 UTC

cloudamqp / amqp-client.rb

Modern AMQP 0-9-1 Ruby client

RubyMIT★ 28 stars⑂ 7 forkssince Apr 2021View on GitHub ↗

cloudamqp/amqp-client.rb holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Vitality (80/100) and lowest on AI Readiness (48/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

CloudAMQPOrganization
55 followers93 public repossince Mar 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsamqp-client2.2.0-230 days ago

Metrics by category

Vitality

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

80Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
13.8/36Commit cadence20/52 weeks with commits
18/18Commit volume186 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year186
human_commit_share0.94
days_since_last_push0
active_weeks_last_year20
How it's scored
27/27Ships releases6 releases published
36/36Release recencylatest release 0 days ago
19.8/27Release cadencea release every ~70.6 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count6
latest_release_tagv2.2.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases70.6

Community & Adoption

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

48Weak · 17% of overall
How it's scored
23.2/60Stars28 stars
6.5/25Forks7 forks
3.3/15Watchers5 watchers
Inputs used
forks7
stars28
watchers5
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
56/80Total downloads245,862 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesamqp-client
dependents
ecosystemsrubygems
total_downloads245,862
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?

71Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
11.2/22.5Commit distributiontop contributor authored 50% of commits
13.5/13.5Contributor breadth11 contributors
10/10OpenSSF Scorecard: Contributorsproject has 8 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled11
top_contributor_share0.502
How it's scored
42/42Issue resolution100% of issues closed
24.6/30PR acceptance91/111 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
7.5/15OpenSSF Scorecard: Code-ReviewFound 10/17 approved changesets -- score normalized to 5
Inputs used
merged_prs91
open_issues0
closed_issues19
prs_merged_7d4
prs_decided_7d6
prs_merged_30d6
prs_decided_30d8
issue_closed_ratio1
closed_unmerged_prs20
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 backingorganization-owned
0/20Verified domain
12.6/25Owner reach55 followers of cloudamqp
25/25Track record93 public repos, account ~14 yr old
Inputs used
followers55
owner_typeOrganization
is_verifiedno
owner_logincloudamqp
public_repos93
account_age_days5,289

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on rubygems
35/35Publish recencylatest publish 0 days ago
20/20Version history23 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesamqp-client
ecosystemsrubygems
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter config.rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests21 out of 21 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
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://cloudamqp.github.io/amqp-client.rb/
10/10Repository description
10/10Topics2 topics
0/10Wiki
Inputs used
topicsruby, amqp
has_wikino
homepagehttps://cloudamqp.github.io/amqp-client.rb/
docs_sitehttps://cloudamqp.github.io/amqp-client.rb/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

66Good · 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-Tests21 out of 21 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
3.8/7.5Code-ReviewFound 10/17 approved changesets -- score normalized to 5
2.5/2.5Contributorsproject has 8 contributing companies or organizations
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
7.5/7.5Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
5/5Pinned-Dependenciesall dependencies are pinned
4.5/5SASTSAST tool detected but not run on all commits
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate6.6

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.

48Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
32.3/40Legible commit history57 of 94 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.606
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.rubocop.yml
0/11Static type checking
0/10Reproducible environment
6/10Demonstrated agent practice3 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance6 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependenciesall dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.03
toolchain_manifests
dependency_bot_commit_share0.06
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/38 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes28,813
source_files_sampled38
oversized_source_files0

Key facts

28GitHub stars
11contributors
186commits, last 12 months
0days since last push
6releases
1bus factor
0open issues
RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 7 ⇿
0Stars
7Forks
4Releases

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.

1234567712021-062023-112026-05
Major 1Minor 1Patch 2

Each point covers 5 days.

OpenSSF Scorecard 6.6 / 10
6.6aggregate

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-08-31 09:34 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests21 out of 21 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 10/17 approved changesets -- score normalized to 5
10Contributorsproject has 8 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 1 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
9SASTSAST tool detected but not run on all commits
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 13
RegistryPackageVersion constraintManifest
RubyGemsbenchmarkGemfile
RubyGemsbunnyGemfile
RubyGemsjruby-openssl>= 0.19.0Gemfile
RubyGemsloggerGemfile
RubyGemsminitestGemfile
RubyGemsminitest-mockGemfile
RubyGemsminitest-reportersGemfile
RubyGemsrakeGemfile
RubyGemsrubocopGemfile
RubyGemsrubocop-minitestGemfile
RubyGemsrubocop-rakeGemfile
RubyGemsstackprofGemfile
RubyGemsyardGemfile
All dependencies 13

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

RegistryPackageVersionRelation
RubyGemsbenchmarkdirect
RubyGemsbunnydirect
RubyGemsjruby-openssldirect
RubyGemsloggerdirect
RubyGemsminitestdirect
RubyGemsminitest-mockdirect
RubyGemsminitest-reportersdirect
RubyGemsrakedirect
RubyGemsrubocopdirect
RubyGemsrubocop-minitestdirect
RubyGemsrubocop-rakedirect
RubyGemsstackprofdirect
RubyGemsyarddirect
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 statisticsRubyGems.