Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 16:20 UTC

httprb / http

HTTP (The Gem! a.k.a. http.rb) - a fast Ruby HTTP client with a chainable API, streaming support, and timeouts

RubyMIT★ 3,084 stars⑂ 326 forkssince Oct 2011View on GitHub ↗

httprb/http holds a health index of 88 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (84/100) and lowest on AI Readiness (42/100). It was last updated 16 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

http.rbOrganization
6 followers5 public repossince Jan 2015

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemshttp6.0.4-11457 days ago

Metrics by category

Vitality

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

74Good · 21% of overall
How it's scored
28.8/36Push recency — last push 16 days ago
7.6/36Commit cadence — 11/52 weeks with commits
18/18Commit volume — 120 commits in the last year
10/10OpenSSF Scorecard: Maintained — 17 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year120
human_commit_share0.98
days_since_last_push16
active_weeks_last_year11
How it's scored
27/27Ships releases — 4 releases published
27/36Release recency — latest release 142 days ago
27/27Release cadence — a release every ~11.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count4
latest_release_tagv6.0.3
releases_from_tagsno
days_since_latest_release142
mean_days_between_releases11.6
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?

84Excellent · 17% of overall
How it's scored
56.6/60Stars — 3,084 stars
20.9/25Forks — 326 forks
9/15Watchers — 42 watchers
Inputs used
forks326
stars3,084
watchers42
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
80/80Total downloads — 213,306,090 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageshttp
dependents—
ecosystemsrubygems
total_downloads213,306,090
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?

72Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
14.6/22.5Commit distribution — top contributor authored 35% of commits
13.5/13.5Contributor breadth — 99 contributors
10/10OpenSSF Scorecard: Contributors — project has 54 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled99
top_contributor_share0.349
How it's scored
39.1/42Issue resolution — 93% of issues closed
22.7/30PR acceptance — 345/456 decided PRs merged
13/13Newcomer PR acceptance — 3/3 first-time contributors' PRs merged in 30d
3/15OpenSSF Scorecard: Code-Review — Found 7/27 approved changesets -- score normalized to 2
Inputs used
merged_prs345
open_issues25
closed_issues342
prs_merged_7d0
prs_decided_7d0
prs_merged_30d3
prs_decided_30d4
issue_closed_ratio0.932
closed_unmerged_prs111
first_time_authors_30d1
first_time_prs_merged_30d3
first_time_prs_decided_30d3
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
6.1/25Owner reach — 6 followers of httprb
17.7/25Track record — 5 public repos, account ~11 yr old
Inputs used
followers6
owner_typeOrganization
is_verifiedno
owner_loginhttprb
public_repos5
account_age_days4,268

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows — 6 workflow(s)
24/24Tests present
16/16Linter config — .rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 9 out of 9 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 site — https://www.rubydoc.info/gems/http/6.0.4
10/10Repository description
10/10Topics — 4 topics
10/10Wiki
Inputs used
topicsruby, http-client, http, client
has_wikiyes
homepage—
docs_sitehttps://www.rubydoc.info/gems/http/6.0.4
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-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 9 out of 9 merged PRs checked by a CI test -- score normalized to 10
0.5/2.5CII-Best-Practices — badge detected: InProgress
1.5/7.5Code-Review — Found 7/27 approved changesets -- score normalized to 2
2.5/2.5Contributors — project has 54 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 — 17 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.6
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.

42Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
36.5/40Legible commit history — 67 of 98 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.684
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
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 2 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.02
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/130 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes58,061
source_files_sampled130
oversized_source_files0

Key facts

3,084GitHub stars
99contributors
120commits, last 12 months
16days since last push
4releases
2bus factor
25open 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 ★ / 326 ⇿
0Stars
326Forks
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.

012525037532162011-102019-032026-08
Major 1Minor 0Patch 3

Each point covers 14 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-09-10 16:20 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-Tests9 out of 9 merged PRs checked by a CI test -- score normalized to 10
2CII-Best-Practicesbadge detected: InProgress
2Code-ReviewFound 7/27 approved changesets -- score normalized to 2
10Contributorsproject has 54 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained17 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 5
RegistryPackageVersion constraintManifest
RubyGemsrake—Gemfile
RubyGemsrbs>= 4.1Gemfile
RubyGemssteep>= 2Gemfile
RubyGemskramdown—Gemfile
RubyGemsyard—Gemfile
All dependencies 23

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

RegistryPackageVersionRelation
RubyGemskramdown—direct
RubyGemsrake—direct
RubyGemsrbs—direct
RubyGemssteep—direct
RubyGemsyard—direct
RubyGemsaddressable—indirect
RubyGemsdebug—indirect
RubyGemshttp-cookie—indirect
RubyGemsllhttp—indirect
RubyGemsllhttp-ffi—indirect
RubyGemslogger—indirect
RubyGemsminitest-memory—indirect
RubyGemsminitest-mock—indirect
RubyGemsminitest-strict—indirect
RubyGemsmutant-minitest—indirect
RubyGemsnokogiri—indirect
RubyGemsrubocop—indirect
RubyGemsrubocop-minitest—indirect
RubyGemsrubocop-performance—indirect
RubyGemsrubocop-rake—indirect
RubyGemssimplecov—indirect
RubyGemssimplecov-lcov—indirect
RubyGemsyardstick—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.