Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-24 16:13 UTC

lostisland / faraday

Simple, but flexible HTTP client library, with support for multiple backends.

RubyMIT★ 5,952 stars⑂ 1,031 forkssince Dec 2009View on GitHub ↗

lostisland/faraday holds a health index of 97 out of 100, placing it in the Exceptional band. It scores highest on Community & Adoption (98/100) and lowest on AI Readiness (71/100). It was last updated 5 days ago. 3 contributors account for most of its recent work.

97
overall / 100
Exceptional

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.

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

Ownership

lostislandOrganization
34 followers22 public repossince Oct 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsfaraday2.15.0-1628 days ago

Metrics by category

Vitality

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

82Excellent · 21% of overall
How it's scored
36/36Push recency — last push 5 days ago
13.2/36Commit cadence — 19/52 weeks with commits
16.6/18Commit volume — 70 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year70
human_commit_share0.97
days_since_last_push5
active_weeks_last_year19
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 8 days ago
19.8/27Release cadence — a release every ~50.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv2.15.0
releases_from_tagsno
days_since_latest_release8
mean_days_between_releases50.1
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?

98Exceptional · 17% of overall
How it's scored
60/60Stars — 5,952 stars
25/25Forks — 1,031 forks
10.7/15Watchers — 86 watchers
Inputs used
forks1,031
stars5,952
watchers86
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
80/80Total downloads — 1,284,909,800 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesfaraday
dependents—
ecosystemsrubygems
total_downloads1,284,909,800
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?

80Excellent · 23% of overall
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
15.8/22.5Commit distribution — top contributor authored 30% of commits
13.5/13.5Contributor breadth — 98 contributors
10/10OpenSSF Scorecard: Contributors — project has 49 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled98
top_contributor_share0.296
How it's scored
39.8/42Issue resolution — 95% of issues closed
21.6/30PR acceptance — 693/961 decided PRs merged
13/13Newcomer PR acceptance — 5/5 first-time contributors' PRs merged in 30d
12/15OpenSSF Scorecard: Code-Review — Found 12/15 approved changesets -- score normalized to 8
Inputs used
merged_prs693
open_issues37
closed_issues664
prs_merged_7d10
prs_decided_7d10
prs_merged_30d20
prs_decided_30d22
issue_closed_ratio0.947
closed_unmerged_prs268
first_time_authors_30d5
first_time_prs_merged_30d5
first_time_prs_decided_30d5
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
11.1/25Owner reach — 34 followers of lostisland
21.9/25Track record — 22 public repos, account ~14 yr old
Inputs used
followers34
owner_typeOrganization
is_verifiedno
owner_loginlostisland
public_repos22
account_age_days5,116

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 — 162 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesfaraday
ecosystemsrubygems
any_deprecatedno
min_days_since_publish8

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
16/16Linter config — .rubocop.yml
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 12 out of 12 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://lostisland.github.io/faraday
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepagehttps://lostisland.github.io/faraday
docs_sitehttps://lostisland.github.io/faraday
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

82Excellent · 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 — 12 out of 12 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
6/7.5Code-Review — Found 12/15 approved changesets -- score normalized to 8
2.5/2.5Contributors — project has 49 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 14 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
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
6.8/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate7.7
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, 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
advisories0
affected_packages0
assessed_packages106
unassessed_packages19
affected_by_severitynone
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 106 resolved dependencies against OSV. 19 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

71Good · 4% of overall
How it's scored
45/45Agent instructions — .claude/CLAUDE.md, .cursorrules, .github/copilot-instructions.md
0/15Machine-readable docs (llms.txt)
31.9/40Legible commit history — 58 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.598
agent_instruction_files.claude/CLAUDE.md, .cursorrules, .github/copilot-instructions.md
agent_instruction_max_bytes2,384
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .rubocop.yml
0/11Static type checking
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 23 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 3 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
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.23
toolchain_manifests—
dependency_bot_commit_share0.03
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/79 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes30,441
source_files_sampled79
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

5,952GitHub stars
98contributors
70commits, last 12 months
5days since last push
100releases
3bus factor
37open issues
npm, RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-07-11: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 5952 stars today.
  • Could not fetch npm package 'faraday-docs' from its registry

More detail

Star and fork history 5,948 ★ / 1,031 ⇿
5,948Stars
1,031Forks
99Releases

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-07-11. 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.

01,0002,0003,0004,0005,0006,0005,9481,031212010-102018-102026-10
Major 2Minor 30Patch 61

Each point covers 15 days.

OpenSSF Scorecard 7.7 / 10
7.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-10-24 16:12 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-Tests12 out of 12 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 12/15 approved changesets -- score normalized to 8
10Contributorsproject has 49 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 14 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not 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
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
RubyGemsjruby-openssl~> 0.11.0Gemfile
npmdocsify-cli5.0.0package.json
All dependencies 125

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

RegistryPackageVersionRelation
npmdocsify-cli5.0.0direct
RubyGemsjruby-openssl—direct
npmansi-colors4.1.3indirect
npmansi-regex2.1.1indirect
npmansi-regex5.0.1indirect
npmansi-styles2.2.1indirect
npmansi-styles3.2.1indirect
npmansi-styles4.3.0indirect
npmcamelcase5.3.1indirect
npmchalk1.1.3indirect
npmchalk2.4.2indirect
npmchokidar4.0.3indirect
npmcliui6.0.0indirect
npmcolor-convert1.9.3indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.3indirect
npmcolor-name1.1.4indirect
npmcommander14.0.3indirect
npmcommon-tags1.8.2indirect
npmconnect3.7.0indirect
npmconnect-history-api-fallback1.6.0indirect
npmconnect-livereload0.6.1indirect
npmcp-file7.0.0indirect
npmdebug2.6.9indirect
npmdecamelize1.2.0indirect
npmdepd2.0.0indirect
npmdestroy1.2.0indirect
npmdexie4.4.5indirect
npmdocsify5.0.0indirect
npmee-first1.1.1indirect
npmemoji-regex8.0.0indirect
npmencodeurl1.0.2indirect
npmencodeurl2.0.0indirect
npmenquirer2.3.6indirect
npmescape-html1.0.3indirect
npmescape-string-regexp1.0.5indirect
npmetag1.8.1indirect
npmfiglet1.12.0indirect
npmfinalhandler1.1.2indirect
npmfind-up4.1.0indirect
npmfresh0.5.2indirect
npmfs-extra8.1.0indirect
npmget-caller-file2.0.5indirect
npmget-port5.1.1indirect
npmgraceful-fs4.2.11indirect
npmhas-ansi2.0.0indirect
npmhas-flag3.0.0indirect
npmhttp-errors2.0.1indirect
npminherits2.0.4indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-wsl1.1.0indirect
npmjsonfile4.0.0indirect
npmlivereload0.10.3indirect
npmlivereload-js4.0.3indirect
npmlocate-path5.0.0indirect
npmlru-cache5.1.1indirect
npmmake-dir3.1.0indirect
npmmarked18.0.11indirect
npmmedium-zoom1.1.0indirect
npmmime1.6.0indirect
npmms2.0.0indirect
npmms2.1.3indirect
npmnested-error-stacks2.1.1indirect
npmon-finished2.3.0indirect
npmon-finished2.4.1indirect
npmopen6.4.0indirect
npmopencollective-postinstall2.0.3indirect
npmopts2.0.2indirect
npmp-event4.2.0indirect
npmp-finally1.0.0indirect
npmp-limit2.3.0indirect
npmp-locate4.1.0indirect
npmp-timeout3.2.0indirect
npmp-try2.2.0indirect
npmparent-require1.0.0indirect
npmparseurl1.3.3indirect
npmpath-exists4.0.0indirect
npmprismjs1.30.0indirect
npmrange-parser1.2.1indirect
npmreaddirp4.1.2indirect
npmrequire-directory2.1.1indirect
npmrequire-main-filename2.0.0indirect
npmsemver6.3.1indirect
npmsend0.19.2indirect
npmserve-static1.16.3indirect
npmset-blocking2.0.0indirect
npmsetprototypeof1.2.0indirect
npmstatuses1.5.0indirect
npmstatuses2.0.2indirect
npmstring-width4.2.3indirect
npmstrip-ansi3.0.1indirect
npmstrip-ansi6.0.1indirect
npmsupports-color2.0.0indirect
npmsupports-color5.5.0indirect
npmtinydate1.3.0indirect
npmtoidentifier1.0.1indirect
npmuniversalify0.1.2indirect
npmunpipe1.0.0indirect
npmutils-merge1.0.1indirect
npmwhich-module2.0.1indirect
npmwrap-ansi6.2.0indirect
npmws8.22.0indirect
npmy18n4.0.3indirect
npmyallist3.1.1indirect
npmyargonaut1.1.4indirect
npmyargs15.4.1indirect
npmyargs-parser18.1.3indirect
RubyGemsbake-test-external—indirect
RubyGemscoveralls_reborn—indirect
RubyGemsfaraday-net_http—indirect
RubyGemsjson—indirect
RubyGemslogger—indirect
RubyGemspry—indirect
RubyGemsracc—indirect
RubyGemsrack—indirect
RubyGemsrake—indirect
RubyGemsrspec—indirect
RubyGemsrspec_junit_formatter—indirect
RubyGemsrubocop—indirect
RubyGemsrubocop-packaging—indirect
RubyGemsrubocop-performance—indirect
RubyGemsrubocop-rake—indirect
RubyGemssimplecov—indirect
RubyGemswebmock—indirect
RubyGemsyard-junk—indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 106 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 19 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

No known advisories affect the assessed dependencies.

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