Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-11 23:36 UTC

plaid / plaid-ruby

Ruby bindings for Plaid

RubyMIT★ 247 stars⑂ 167 forkssince Feb 2014View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

plaid/plaid-ruby holds a health index of 34 out of 100, placing it in the At Risk band. It scores highest on Sustainability & Governance (95/100) and lowest on Security (40/100). It was last updated 10 days ago. 7 contributors account for most of its recent work.

34
overall / 100
At Risk

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.

34
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 65 is calibrated to 75 on the published index scale (record calibration 2026-08-02). High-Risk Jurisdiction Policy applies a 50% multiplier to weighted overall health and gives it an At Risk ceiling of 34.

Ownership

PlaidOrganization · verified domain
1,036 followers68 public repossince Feb 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsplaid51.0.0-15910 days ago

Metrics by category

Vitality

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

49Weak · 21% of overall
How it's scored
28.8/36Push recency — last push 10 days ago
9.7/36Commit cadence — 14/52 weeks with commits
10.8/18Commit volume — 15 commits in the last year
4/10OpenSSF Scorecard: Maintained — 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
Inputs used
commits_last_year15
human_commit_share1
days_since_last_push10
active_weeks_last_year14
How it's scored
27/27Ships releases — 1 releases published
0/36Release recency — latest release 4,175 days ago
12.6/27Release cadence — cadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count1
latest_release_tagV1.4.2
releases_from_tagsno
days_since_latest_release4,175
mean_days_between_releases—
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?

75Good · 17% of overall
How it's scored
38.8/60Stars — 247 stars
18.5/25Forks — 167 forks
9.7/15Watchers — 56 watchers
Inputs used
forks167
stars247
watchers56
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_badges1
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io
has_pull_request_templateno
How it's scored
76.8/80Total downloads — 24,475,866 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesplaid
dependents—
ecosystemsrubygems
total_downloads24,475,866
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?

95Exceptional · 23% of overall
How it's scored
51.3/54Bus factor — 7 contributor(s) cover half of all commits
19.7/22.5Commit distribution — top contributor authored 12% of commits
13.5/13.5Contributor breadth — 69 contributors
10/10OpenSSF Scorecard: Contributors — project has 12 contributing companies or organizations
Inputs used
bus_factor7
contributors_sampled69
top_contributor_share0.125
How it's scored
41.7/42Issue resolution — 99% of issues closed
20.1/30PR acceptance — 265/395 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs265
open_issues1
closed_issues142
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.993
closed_unmerged_prs130
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
21.7/25Owner reach — 1,036 followers of plaid
25/25Track record — 68 public repos, account ~13 yr old
Inputs used
followers1,036
owner_typeOrganization
is_verifiedyes
owner_loginplaid
public_repos68
account_age_days4,958

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

61Moderate · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests — 17 out of 30 merged PRs checked by a CI test -- score normalized to 5
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://plaid.com/docs
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepagehttps://plaid.com/docs
docs_sitehttps://plaid.com/docs
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

40Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
1.2/2.5CI-Tests — 17 out of 30 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 12 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
3/7.5Maintained — 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
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
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
0.8/7.5Vulnerabilities — 9 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5
high_risk_jurisdiction_cap34
high_risk_jurisdiction_multiplier50
security_posture_after_multiplier25
security_posture_before_jurisdiction50
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 50% multiplier and gives Security posture an At risk ceiling of 34.

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
advisories9
affected_packages2
assessed_packages25
unassessed_packages9
affected_by_severityhigh 2
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 25 resolved dependencies against OSV. 9 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.

53Moderate · 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://plaid.com/llms.txt)
40/40Legible commit history — 94 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://plaid.com/llms.txt
legible_history_share0.94
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock
has_dockerfileyes
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 2/2,215 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes1,365,554
source_files_sampled2,215
oversized_source_files2

Key facts

247GitHub stars
69contributors
15commits, last 12 months
10days since last push
1releases
7bus factor
1open issues
RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 167 ⇿
0Stars
167Forks
1Releases

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.

0408012016020016462014-022020-052026-07
Major 0Minor 0Patch 0

Each point covers 12 days.

OpenSSF Scorecard 5.0 / 10
5.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-11 23:36 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
5CI-Tests17 out of 30 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 12 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
4Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
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
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
1Vulnerabilities9 existing vulnerabilities detected
All dependencies 34

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

RegistryPackageVersionRelation
RubyGemsast2.4.1indirect
RubyGemsbundler—indirect
RubyGemsdiff-lcs1.4.4indirect
RubyGemsdotenv—indirect
RubyGemsdotenv2.7.6indirect
RubyGemsfaraday—indirect
RubyGemsfaraday2.6.0indirect
RubyGemsfaraday-multipart—indirect
RubyGemsfaraday-multipart1.0.4indirect
RubyGemsfaraday-net_http3.0.1indirect
RubyGemsminitest—indirect
RubyGemsminitest5.25.4indirect
RubyGemsminitest-around—indirect
RubyGemsminitest-around0.5.0indirect
RubyGemsmultipart-post2.2.3indirect
RubyGemsparallel1.20.1indirect
RubyGemsparser2.7.2.0indirect
RubyGemsrainbow3.0.0indirect
RubyGemsrake—indirect
RubyGemsrake13.0.1indirect
RubyGemsregexp_parser1.8.0indirect
RubyGemsrexml3.2.5indirect
RubyGemsrspec—indirect
RubyGemsrspec3.10.0indirect
RubyGemsrspec-core3.10.0indirect
RubyGemsrspec-expectations3.10.0indirect
RubyGemsrspec-mocks3.10.0indirect
RubyGemsrspec-support3.10.0indirect
RubyGemsrubocop—indirect
RubyGemsrubocop0.91.1indirect
RubyGemsrubocop-ast0.4.2indirect
RubyGemsruby-progressbar1.10.1indirect
RubyGemsruby2_keywords0.0.5indirect
RubyGemsunicode-display_width1.7.0indirect
Dependency advisories 2

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

PackageVersionRelationSeverityAdvisoriesFixed in
faraday2.6.0indirecthigh32.14.3
rexml3.2.5indirecthigh63.3.9

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.