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

binance / binance-connector-ruby

A simple connector to Binance Public API

RubyMIT★ 50 stars⑂ 30 forkssince Nov 2021View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

binance/binance-connector-ruby holds a health index of 62 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (78/100) and lowest on Vitality (39/100). It was last updated 93 days ago. 2 contributors account for most of its recent work.

62
overall / 100
Moderate

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.

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

Ownership

BinanceOrganization · verified domain
3,321 followers48 public repossince Aug 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsbinance-connector-ruby1.8.0-1493 days ago

Metrics by category

Vitality

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

39Weak · 21% of overall
How it's scored
9.9/36Push recencylast push 93 days ago
0.7/36Commit cadence1/52 weeks with commits
4.3/18Commit volume2 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year2
human_commit_share1
days_since_last_push93
active_weeks_last_year1
How it's scored
27/27Ships releases9 releases published
27/36Release recencylatest release 93 days ago
12.6/27Release cadencea release every ~178.6 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count9
latest_release_tagv1.8.0
releases_from_tagsno
days_since_latest_release93
mean_days_between_releases178.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?

57Moderate · 17% of overall
How it's scored
27.4/60Stars50 stars
12.2/25Forks30 forks
2.7/15Watchers4 watchers
Inputs used
forks30
stars50
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io, shields.io
has_pull_request_templateno
How it's scored
50.3/80Total downloads68,703 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesbinance-connector-ruby
dependents
ecosystemsrubygems
total_downloads68,703
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?

78Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
12.6/22.5Commit distributiontop contributor authored 44% of commits
6.8/13.5Contributor breadth5 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor2
contributors_sampled5
top_contributor_share0.438
How it's scored
32.7/42Issue resolution78% of issues closed
25.7/30PR acceptance18/21 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
10.5/15OpenSSF Scorecard: Code-ReviewFound 8/11 approved changesets -- score normalized to 7
Inputs used
merged_prs18
open_issues2
closed_issues7
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.778
closed_unmerged_prs3
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
20/20Verified domain
25/25Owner reach3,321 followers of binance
24.3/25Track record48 public repos, account ~6 yr old
Inputs used
followers3,321
owner_typeOrganization
is_verifiedyes
owner_loginbinance
public_repos48
account_age_days2,224

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on rubygems
35/35Publish recencylatest publish 93 days ago
20/20Version history14 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesbinance-connector-ruby
ecosystemsrubygems
any_deprecatedno
min_days_since_publish93

Engineering Quality

Are baseline engineering and documentation practices in place?

68Good · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter config.rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests1 out of 11 merged PRs checked by a CI test -- score normalized to 0
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://www.rubydoc.info/gems/binance-connector-ruby/1.8.0
10/10Repository description
10/10Topics9 topics
10/10Wiki
Inputs used
topicsbinance, api, connector, crypto, library, market-data, real-time, ruby, trading
has_wikiyes
homepage
docs_sitehttps://www.rubydoc.info/gems/binance-connector-ruby/1.8.0
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

45Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0/2.5CI-Tests1 out of 11 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5.2/7.5Code-ReviewFound 8/11 approved changesets -- score normalized to 7
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
6/7.5Vulnerabilities2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories1 affected: faraday 1.10.5 (high 7.5)
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
33.7/40No advisories left outstanding1 advisory-carrying package(s) unaddressed past 90 days; oldest published 92 days ago
Inputs used
sourceosv
advisories2
affected_packages2
assessed_packages71
unassessed_packages6
affected_by_severityhigh 1, low 1
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 71 resolved dependencies against OSV. 6 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.

46Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
20/40Legible commit history18 of 48 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.375
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
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 48
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock, package-lock.json
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/484 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes36,892
source_files_sampled484
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
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

50GitHub stars
5contributors
2commits, last 12 months
93days since last push
9releases
2bus factor
2open 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 ★ / 30 ⇿
0Stars
30Forks
9Releases

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.

0510152025302722022-032024-062026-08
Major 0Minor 6Patch 3

Each point covers 5 days.

OpenSSF Scorecard 4.0 / 10
4.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-20 10: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
0CI-Tests1 out of 11 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7Code-ReviewFound 8/11 approved changesets -- score normalized to 7
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
8Vulnerabilities2 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
RubyGemsfaradayGemfile
RubyGemswebsocket-eventmachine-clientGemfile
RubyGemsrake>= 13.0.0Gemfile
RubyGemsyardGemfile
All dependencies 77

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

RegistryPackageVersionRelation
RubyGemsfaradaydirect
RubyGemsfaraday1.10.5direct
RubyGemsrakedirect
RubyGemsrake13.4.2direct
RubyGemswebsocket-eventmachine-clientdirect
RubyGemswebsocket-eventmachine-client1.3.0direct
RubyGemsyard0.9.44direct
RubyGemsabstract_type0.0.7indirect
RubyGemsadamantium0.2.0indirect
RubyGemsaddressable2.9.0indirect
RubyGemsanima0.3.2indirect
RubyGemsast2.4.3indirect
RubyGemsbigdecimal4.1.2indirect
RubyGemsbinding_of_caller2.0.0indirect
RubyGemsbundlerindirect
RubyGemsconcord0.1.6indirect
RubyGemscrack1.0.1indirect
RubyGemsdebug_inspector1.2.0indirect
RubyGemsdiff-lcs1.6.2indirect
RubyGemsdocile1.4.1indirect
RubyGemsequalizer0.0.11indirect
RubyGemseventmachine1.2.7indirect
RubyGemsfaraday-em_http1.0.0indirect
RubyGemsfaraday-em_synchrony1.0.1indirect
RubyGemsfaraday-excon1.1.0indirect
RubyGemsfaraday-httpclient1.0.1indirect
RubyGemsfaraday-multipart1.2.0indirect
RubyGemsfaraday-net_http1.0.2indirect
RubyGemsfaraday-net_http_persistent1.2.0indirect
RubyGemsfaraday-patron1.0.0indirect
RubyGemsfaraday-rack1.0.0indirect
RubyGemsfaraday-retry1.0.4indirect
RubyGemsgem-releaseindirect
RubyGemsgem-release2.2.4indirect
RubyGemshashdiff1.2.1indirect
RubyGemsice_nine0.11.2indirect
RubyGemsjson2.19.5indirect
RubyGemslanguage_server-protocol3.17.0.5indirect
RubyGemslint_roller1.1.0indirect
RubyGemsmemoizable0.4.2indirect
RubyGemsmprelude0.1.0indirect
RubyGemsmultipart-post2.4.1indirect
RubyGemsparallel2.1.0indirect
RubyGemsparser3.3.11.1indirect
RubyGemsprism1.9.0indirect
RubyGemsproc_to_ast0.2.0indirect
RubyGemsprocto0.0.3indirect
RubyGemspublic_suffix7.0.5indirect
RubyGemsracc1.8.1indirect
RubyGemsrainbow3.1.1indirect
RubyGemsregexp_parser2.12.0indirect
RubyGemsrexml3.4.4indirect
RubyGemsrouge4.7.0indirect
RubyGemsrspecindirect
RubyGemsrspec3.13.2indirect
RubyGemsrspec-core3.13.6indirect
RubyGemsrspec-expectations3.13.5indirect
RubyGemsrspec-mocks3.13.8indirect
RubyGemsrspec-parameterized2.0.1indirect
RubyGemsrspec-parameterized-core2.0.2indirect
RubyGemsrspec-parameterized-table_syntax2.1.1indirect
RubyGemsrspec-support3.13.7indirect
RubyGemsrubocop1.86.2indirect
RubyGemsrubocop-ast1.49.1indirect
RubyGemsruby-progressbar1.13.0indirect
RubyGemsruby2_keywords0.0.5indirect
RubyGemssimplecov0.22.0indirect
RubyGemssimplecov-html0.13.2indirect
RubyGemssimplecov_json_formatter0.1.4indirect
RubyGemsthread_safe0.3.6indirect
RubyGemsunicode-display_width3.2.0indirect
RubyGemsunicode-emoji4.2.0indirect
RubyGemsunparser0.5.7indirect
RubyGemswebmock3.26.2indirect
RubyGemswebsocket1.2.11indirect
RubyGemswebsocket-eventmachine-base1.2.0indirect
RubyGemswebsocket-native1.0.0indirect
Dependency advisories 2

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

PackageVersionRelationSeverityAdvisoriesFixed in
faraday1.10.5directhigh12.14.3
json2.19.5indirectlow12.19.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 statisticsRubyGems.